[SOLVED] systemd not alway starts dnsmasq and minidlna service

Hi!
After I've annoyed some of you (and hopefully helped others) with my threads on systemd I got systemd working. But; I still have one problem. Systemd seems to have trouble starting dnsmasq and minidlna.
dnsmasq.service loaded failed failed A lightweight DHCP and caching DNS server
[email protected] loaded active running Getty on tty1
httpd.service loaded active running Apache Web Server
logitechmediaserver.service loaded active running Logitech Media Server Daemon
lvm.service loaded active exited LVM activation
minidlna.service loaded failed failed minidlna server
Sometimes they do load, sometimes not. Is there a way to find out why a service could not be started?
btw
systemctl start minidlna dnsmasq
does start them perfectly
Last edited by theking2 (2012-12-13 18:50:35)

Yes, there is such a command systemctl status and it says
Dec 11 20:54:44 janus systemd[1]: Starting A lightweight DHCP and caching DNS server...
Dec 11 20:54:45 janus dnsmasq[308]: dnsmasq: syntax check OK.
Dec 11 20:54:45 janus dnsmasq[335]: dnsmasq: failed to create listening socket for 172.16.0.8: Cannot assign requested address
Dec 11 20:54:45 janus systemd[1]: dnsmasq.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 11 20:54:45 janus systemd[1]: Failed to start A lightweight DHCP and caching DNS server.
Dec 11 20:54:45 janus systemd[1]: Unit dnsmasq.service entered failed state
and
minidlna.service - minidlna server
Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled)
Active: failed (Result: exit-code) since Tue, 2012-12-11 20:54:45 CET; 46s ago
Process: 303 ExecStart=/usr/sbin/minidlna -P /var/run/minidlna/minidlna.pid (code=exited, status=255)
CGroup: name=systemd:/system/minidlna.service

Similar Messages

Firefox will not start and open a website from a Thunderbird email link. It will go to a link from Thunderbird once Firefox is open, but will not initially start Firefox and proceed to open the Thunderbird email link.

Firefox will not ''start'' and open a website from a Thunderbird email link. A link from Thunderbird will open once Firefox is ''already'' started, but will not initially start Firefox and proceed to open the Thunderbird email link.

I also have this problem. I cannot open links from a discussion board I frequent nor can I open links from my email. Also after opening my email, I cannot go to any other sites except my home page. I can then go no where else.
When I close Firefox and try to reopen it, it does nothing! I have to bring up the Task Manager and end the Firefox process before I can get back in.
To the best of my knowledge, this problem started with the new update to Ver. 3.6.9. I am running Windows XP Media Center 2005

How to start CRS and other services after rebooting nodes.

Hi,
i have created two node cluster database.how to start CRS and other service after rebooting nodes?
Thanks,

use crsctl command start...
$ORA_CRS_HOME/bin/crsctl start crsOr check status about CLusterware...
$ORA_CRS_HOME/bin/crsctl check crs
CSS appears healthy
CRS appears healthy
EVM appears healthyIf not OK... check log at $ORA_CRS_HOME/log/hostname/*
and check status database , service and etc...
use crs_stat
$ORA_CRS_HOME/bin/crs_stat -t
$ORA_CRS_HOME/bin/crs_stat if you find some service or instance ... not online...
use srvctl command, help to start
Get Help...
$ORA_CRS_HOME/bin/srvctl -h

[SOLVED] Systemd stuck at "Starting File system check"

Hi all
Backstory
My hardware:
Mobo: Gigabyte X99 2011v3 with UEFI and dual bios.
GFX: MSI GTX 970 4GB Gaming OC
HDD: Samsung 850 Pro 1TB SSD
CPU: intel 5820k
I have been using arch for about 2 years now. I recently bought new hardware, Gigabyte X99 motherboard uefi dual bios. I have tried a couple of times to install arch the old way, i.e. legacy mode or normal bios mode, however after a successful install, when I reboot my bios says "Select Proper Boot Device". Then I decided to put everything in UEFI mode and install arch using the uefi install disc. At first, I was not very successful, because I followed the arch wiki to the bone but when it comes to UEFI, instructions are a bit vague. In any case, I managed to install Arch and get uefi to work 100% by using this guide http://jorisvandijk.com/2014/installing … pt-system/ .
Problem
After installing arch successfully using UEFI mode, arch starts booting up, everything shows [OK] at the side, no errors, however, it hangs after a line that reads "Starting File system check ". I am not at home right now, however I thought I could start troubleshooting and maybe get some ideas.
I have tried the following.
- Chrooted back into my arch install using the live cd and mounting my partitions.
- Updated and synced pacman.
- Removed all journal log files.
- reinstalled Systemd.
- rebuilt kernel modules.
none of the above worked. It still hangs at "Starting fiel system check"
Any ideas.
SOLUTION
Solved by using
nolapic
Still had other problems after that, however, the initial problem was solved.
Last edited by janpansa (2015-02-26 20:04:24)

jasonwryan wrote:Taking the time to read through the relevant pages and working through the Beginners' Guide methodically is the best (and only) way to both install Arch and also bed in a sound understanding of how your system is put together. It is an investment that will continue to pay you back as long as you run a Linux/UNIX box.
Hi Jason,
thx for your help so far. I have printed out the Arch beginners install and followed it to the bone and focusing on the UEFI parts. Arch installed without a single error, everything went smooth. Aftwerwards, I exited from the chroot environmount, unmount and reboot and again, it hangs on the startup. This time I took screenshots.
I present to the board, exhibit A, arch starting up after a fresh install :
http://oi61.tinypic.com/2m4x82o.jpg
I now present to the board, exhibit B, arch starting up for a second time, after restarting the pc :
http://oi59.tinypic.com/10ehvki.jpg
Afterwards, I restarted again. Went into bios setup and checked my boot priorities. This is what I saw:
I now present exhibit C, my bios boot options :
http://oi62.tinypic.com/24ys0bd.jpg
I tried all the options listed for my Samsung SSD, with and without UEFI as well as the option that was the default aka Linux boot manage". Each one did exactly the same.
I have a few ideas :
1.) Leave out swap.
2.) Disable fscheck.
3.) I have a feeling that my SSD is reading/writing too fast and that fscheck is having trouble ?
I am now trying option 1. In other words, I am reinstalling arch, again, following the beginners guide to the bone and focusing specifically on the UEFI parts. This time, I am leaving out swap. (I have 16GB of DDR4 memory). I have about a 70% feeling that the outcome will be the same. However, I will be back after that to comment on the outcome. Please leave feedback and help me through this where you can ! Thanks
Last edited by jasonwryan (2015-02-23 19:34:21)

[Solved] SystemD, how to start a service after network is up.

Hello,
I'm recently involved to set up a daemon which should be ready after boot (aria2). Then it fails, as it fails minidlna as well.
The reason is that they try to come up but there's no host to talk to. See this page.
For my purposes, it should be good when the daemons find the necessary to stay alive (even they won't have a network fully ready, that may happen in less than a minute later). For minidlna is needed a valid IP which could be 127.0.0.1 or localhost, for aria2 it may be same or just looking for a RPC binding.
This what the logs are telling me.
I was trying to set more dependencies in the service, but even to set
After=wpa_supplicant.service
it doesn't have effect.
I don't find a solution, as far as my knowledge spans. Another chance would take to set a systemD timer and when that will be gone to start the daemon. Sorry but I don't know much about that.
Looking for someone here to guide to right direction.
TIA
Last edited by TheSaint (2013-07-15 03:12:37)

WonderWoofy wrote:It depends on what network management utility you use and therefore also how you connect. If you are using an ethernet connection, you could just use dhcpcd@<interface>.service. This is a very simple service, and the network.target will not be reached until the IP address and connectivity is established.
Meanwhile some good suggestion (like yours) came up, I've tried a couple of recipes. But dhcpcd.service didn't get it right. Maybe dhcpcd@<interface>.service, would work, I'll see later.
I got this working:
[Unit]
Description=aria2 Service
Requires=network.target
After=dhcpcd.service
[Service]
Type=forking
User=aria2
Group=aria2
EnvironmentFile=/etc/conf.d/aria2.conf
WorkingDirectory=/var/aria2
ExecStart=/usr/bin/aria2c $ARIACMD
ExecReload=/usr/bin/kill -HUP $MAINPID
RestartSec=1min
Restart=on-failure
[Install]
WantedBy=multi-user.target
You may note the After=dhcpcd.service, but it doesn't work. I found RestartSec=1min ,Restart=on-failure more effective and perhaps less blocking to wait for the network to be ready. As a server this should be a small issue, very seldom compared with the running time. We (family members) can accept a little wait for the service to be on.
Exactly I don't know which of the two is the right solution, maybe the delay is the right one.
I was doing a cron scheduled job, before using systemd boot, which was kicking minidlna every 5 minutes, since it was dieing often. I didn't discover what was the reason.
I think I'll have to study another recipe which sets up a timer and keep an eye on these two services, for the long term service. But even cron would suffice, I think.
WonderWoofy wrote:if you are using wireless, the only two real solutions would be to use netctl@<profile>.service, which too won't reach the network.target until a conplete connection is made
Yes I'm on wireless network and the interface plugged on USB . My intent should go beyond any particular configuration. Maybe because I'd like to show a working setup, which may fit for all configuration (90 % )
I have to admit that the actual solution do not care much whether the network is found, so I hope to get a smarter setup that counts on the necessary tools before try something. However it's proved that they fail when no connection to the router is done. But I'm preferring that they succeed.
WonderWoofy wrote: NetworkManager gets around this by implementing an additional service called (unimaginatively) NetworkManager-wait-online.service, which is pulled in automatically when you enable NetowrkManager.service.
As I stated above I'm expecting a solution that won't pull in so much dependencies. Even NM is my connection manager, on the server.
WonderWoofy wrote:
You probably also want to use Requisite=aria2c.service on the minidlna.service as well. This too means that it will be started after aria2c, but that it will not start at all if it is not running or fails.
Additionally, you could try using the Requisite configuration on the minidnla, while setting the aria2c to restart itself on failure. So that it will keep trying, and once it does, then minidlna will start.
looks like a dog biting the tail . It's much preferable a separated failure, just in case.
WonderWoofy wrote:Edit: Also, it is not SystemD. It is systemd (like other "daemon" binaries in *nix).
I'm quite sure I saw it somewhere, none of my inventions
Last edited by TheSaint (2013-07-13 07:10:33)

Firefox 21 does not show start menu and taskbar sub-links of new tab,private window

Firefox does not show start menu icon 's submenu containing links to new tab,new window and new private window.Same happens with taskbar pinned shortcut. It does not show the above three options when I right click on it. I have installed Firefox stable,beta,aurora and nightly at the same time.All the four use different profiles.I have this setup since Firefox 12.There was no problem before v21.I tried reinstalling all the four.Resetting the stable version profile.The options do appear in othe ruser accounts.I want this option for stable version only.I think these are not available for testing versions.I tried all the suggestions in this thread:
https://support.mozilla.org/en-US/questions/943198
I am on Windows 7 64 bit.

You may be experiencing this Windows 7 bug:
* [https://bugzilla.mozilla.org/show_bug.cgi?id=870529 bug 870529] - Windows jumplist not showing anymore
<i>Please do not comment in bug reports: https://bugzilla.mozilla.org/page.cgi?id=etiquette.html</i>

Error in starting nidevldu and nipxirmu services (windows event viewer)

A computer running Windows XP SP1 and a Visual basic (V6.0) application that I've developped had crashed several times. I've seen lots of errors in the Windows event viewer saying that the nidevldu and nipxirmu services were trying to start (exact french message : Le service nidevldu est en attente de démarrage et Le service nipxirmu est en attente de démarrage). These messages are real errors (not warning or informations).
I use a 6034E PCI card, Visual basic V6.0 and NI-DAQ 7.4.
The crashes I've seen may be linked with this problem.
Is there a solution?

Hi,
I think that you are not going to be starting and stopping the devldu service in normal circumstances... due to crashes !
The firsts steps you have to focus on is to optimize your program in order to avoid crashes, which is not a normal way of work I guess. Then you will be able to avoid these messages!
Regards,
David D. - Application Engineer - NI

How do I investigate and solve Pages, Notes, Mail intermittent 'offline' and failure to synchronise problems with Mountain Lion after waking from Sleep

When I wake up my iMac after sleep, i get a variety of intermittent - but mostly FREQUENT and FRUSTRATING problems including:
Notes app is offline - as stated by a message in the window bar. If I close Notes and reopen, the app appears to be online. However, Notes does NOT update with items I know are on my iPad or in the web iCloud. Furthermore, if I create a new note on my iMac, the new Note does not upload to iCloud. This is IRRITATING!
Pages and Numbers - similar situation. I can edit a Pages or Numbers document on my iMac (stored on the iCloud). But then the Pages doc doesn't ALWAYS get uploaded to the iCloud. Then I end up with conflicted versions of the file in the cloud, my iPad, and the two iMacs I use. Then I get CONFUSED and FRUSTRATED. For example, consider these steps:
Open Pages on my iMac, edit an iCloud file, then save and close file
Pages/File/Open/iCloud - I note in the iCloud file list the edited file has a little 'cloud' icon against its name. From experience this warns me of TROUBLE - namely that the file has NOT yet been uploaded to the iCloud. However, I just checked the new Beta iCloud on the web, and to my surprise, the file edited on my iMac is apparently in the icloud. But now, I edit the iCloud version, and the changes DO NOT appear on my iMac pages version. OK I realise its in Beta version...
So now, I open my iPad, open Pages. I note the iCloud version of my edited document updates to my iPad, as indicated by a blue download line. 'It just works' as Steve Jobs claimed at Apple Developers Conference a couple of years back. Again, the edited version form my iPad is now 'up in the cloud' correctly....
Oh - and now mysteriously the Pages version on my Imac has become synchronised with my iPad/iCloud version! Luck ... but that's about all I can say. It doesn't always happen. I'm LUCKY today.
Meanwhile, the Note I created on my iMac (Item 1 above) has still not yet appeared on my iPad or iCloud... even though I HOPE it would be given that Pages on my iMac, iPad and iCloud are chatting nicely now! The Note says it's in my iCloud - but NOT. Similarly, notes updated or added on my iPad, which appear in iCloud, are NOT on my iMac.
Mail - last but NOT LEAST! and MOST INFURIATING!!! My Gmail, Vodafone NZ and Orcon accounts (in Mail) are all active and receiving after the night's sleep. However, my iCloud mail account has the dreaded offline.
The message on Mail is "There may be a problem with the mail server or network. Verify the settings for account “ICloud - [email protected]” or try again. The server returned the error: The server “p03-imap.mail.me.com” cannot be contacted on port 993." Despite the message, mail was received this morning at 8:59 am ... some time before I woke-up my computer (a late start this morning).
If I sent an email FROM my .me iCloud account TO my Vodafone account, the message whooshes away, it's in my SENT box. But it doesn't get delivered to my Vodafone account on my iMac Mail, or anywhere else, Despite the message being listed in my 'Sent' mailbox!!!
In contrast, a message sent from my Gmail account to my Vodafone account (in Mail) gets sent and received almost instantly on my iMac and iPad.
All of the above mishaps are extremely frustrating, as I rush off from working on my iMac at home, get to my iMac at work and find documents I have been updating on my home iMac not available correctly on my work iMac ... or even my iPad. I expect these things from Apple to 'just work'. Furthermore, emails I THINK I have sent (as indicated by them appearing in the Sent folder on my home iMac) ... have not actually been despatched.
Frankly, I can no longer rely or recommend the Apple iCloud stuff, so I am converting more and more to relying on DropBox and Google.
These problems only became apparent since I updated to one of the Mountain Lion versions... I can't say when.
Oh - if I shutdown and restart the computer my Mail works OK. Guess what, I don't want to do that each time I want to use Mail!
Technicals:
My iMac is connected by Ethernet cable to my Apple TimeCapsule. The TimeCapsule is connected by Ethernet cable to my Orcon Genius Modem.
Obviously, my internet connection is A-OK, as I am able to use Firefox to make this posting!
Mountain Lion 10.8.4
iMac 27 inch, mid 2010, Intel Core i5 16 Gb

I've returned to my sleeping iMac after a few days away. Tis time, ALL MAIL accoiunts are offline. I will follow you next set of instructions. In the meantime, here is the DETAIL from MAIL CONNECTION DOCTOR:
LevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
19.10827 STATUS [Gmail]/Trash (UIDNEXT UNSEEN HIGHESTMODSEQ)
WROTE Sep 30 08:35:11.179 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
20.10827 STATUS INBOX (UIDNEXT UNSEEN HIGHESTMODSEQ)
WROTE Sep 30 08:35:11.202 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
21.10827 STATUS "Sent Messages" (UIDNEXT UNSEEN HIGHESTMODSEQ)
WROTE Sep 30 08:35:11.226 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
22.10827 STATUS "Deleted Messages" (UIDNEXT UNSEEN HIGHESTMODSEQ)
READ Sep 30 08:35:11.254 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
* STATUS "[Gmail]/All Mail" (HIGHESTMODSEQ 561701 UIDNEXT 1666 UNSEEN 105)
13.10827 OK Success
READ Sep 30 08:35:11.494 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
* STATUS "[Gmail]/Drafts" (HIGHESTMODSEQ 561701 UIDNEXT 1 UNSEEN 0)
14.10827 OK Success
READ Sep 30 08:35:11.514 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
* STATUS "[Gmail]/Important" (HIGHESTMODSEQ 561701 UIDNEXT 731 UNSEEN 8)
15.10827 OK Success
* STATUS "[Gmail]/Sent Mail" (HIGHESTMODSEQ 561701 UIDNEXT 532 UNSEEN 2)
16.10827 OK Success
* STATUS "[Gmail]/Spam" (HIGHESTMODSEQ 561701 UIDNEXT 16 UNSEEN 2)
17.10827 OK Success
* STATUS "[Gmail]/Starred" (HIGHESTMODSEQ 561701 UIDNEXT 19 UNSEEN 0)
18.10827 OK Success
* STATUS "[Gmail]/Trash" (HIGHESTMODSEQ 561701 UIDNEXT 546 UNSEEN 0)
19.10827 OK Success
* STATUS "INBOX" (HIGHESTMODSEQ 561701 UIDNEXT 603 UNSEEN 64)
20.10827 OK Success
* STATUS "Sent Messages" (HIGHESTMODSEQ 561701 UIDNEXT 138 UNSEEN 0)
21.10827 OK Success
* STATUS "Deleted Messages" (HIGHESTMODSEQ 561701 UIDNEXT 89 UNSEEN 0)
22.10827 OK Success
WROTE Sep 30 08:35:11.537 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc3186cf640
23.10827 IDLE
READ Sep 30 08:35:11.927 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc3186cf640
+ idling
READ Sep 30 08:35:15.472 [kCFStreamSocketSecurityLevelNone] -- host:smtp.mail.me.com -- port:587 -- socket:0x7fc31855c470 -- thread:0x7fc31858ada0
220 st11p00mm-asmtp002.mac.com -- Server ESMTP (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013))
WROTE Sep 30 08:35:24.784 [kCFStreamSocketSecurityLevelNone] -- host:mail.orcon.net.nz -- port:25 -- socket:0x7fc3161a1b00 -- thread:0x7fc315d05050
EHLO [10.1.1.4]
WROTE Sep 30 08:35:24.822 [kCFStreamSocketSecurityLevelNone] -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x7fc316e72a70 -- thread:0x7fc31850bec0
EHLO [10.1.1.4]
WROTE Sep 30 08:35:34.080 [kCFStreamSocketSecurityLevelNone] -- host:smtp.mail.me.com -- port:587 -- socket:0x7fc31855c470 -- thread:0x7fc31858ada0
EHLO [10.1.1.4]
INITIATING CONNECTION Sep 30 08:35:47.175 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc316fc30e0
INITIATING CONNECTION Sep 30 08:35:47.175 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc31a6fa8a0
INITIATING CONNECTION Sep 30 08:35:47.175 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316197890
INITIATING CONNECTION Sep 30 08:35:47.175 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc316e813d0
INITIATING CONNECTION Sep 30 08:35:47.175 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0350
INITIATING CONNECTION Sep 30 08:35:47.175 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3185c0410
INITIATING CONNECTION Sep 30 08:35:47.175 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315ded870
INITIATING CONNECTION Sep 30 08:35:47.193 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e729b0
INITIATING CONNECTION Sep 30 08:35:47.198 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3167d2380
INITIATING CONNECTION Sep 30 08:35:47.377 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3167d2380
INITIATING CONNECTION Sep 30 08:36:40.352 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc318203720
INITIATING CONNECTION Sep 30 08:36:40.352 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc312c8dbc0
INITIATING CONNECTION Sep 30 08:36:40.353 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31617f290
INITIATING CONNECTION Sep 30 08:36:40.353 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc316e729b0
INITIATING CONNECTION Sep 30 08:36:40.353 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31615a390
INITIATING CONNECTION Sep 30 08:36:40.353 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316e3bbc0
INITIATING CONNECTION Sep 30 08:36:40.353 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316e0cfa0
INITIATING CONNECTION Sep 30 08:36:40.368 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31829f120
INITIATING CONNECTION Sep 30 08:36:40.403 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc312c8dbc0
INITIATING CONNECTION Sep 30 08:36:40.412 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
INITIATING CONNECTION Sep 30 08:36:40.565 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc312c8dbc0
INITIATING CONNECTION Sep 30 08:36:40.595 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
INITIATING CONNECTION Sep 30 08:36:40.633 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
INITIATING CONNECTION Sep 30 08:36:40.687 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
INITIATING CONNECTION Sep 30 08:36:40.708 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
INITIATING CONNECTION Sep 30 08:36:40.729 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
INITIATING CONNECTION Sep 30 08:37:33.322 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3183339e0
INITIATING CONNECTION Sep 30 08:37:33.322 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3186f07e0
INITIATING CONNECTION Sep 30 08:37:33.322 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315a9b630
INITIATING CONNECTION Sep 30 08:37:33.322 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3163e7dd0
INITIATING CONNECTION Sep 30 08:37:33.322 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3172f6e70
INITIATING CONNECTION Sep 30 08:37:33.322 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31616b9d0
INITIATING CONNECTION Sep 30 08:37:33.323 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315d14150
INITIATING CONNECTION Sep 30 08:37:33.336 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e03950
INITIATING CONNECTION Sep 30 08:37:33.462 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
INITIATING CONNECTION Sep 30 08:37:33.463 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3163e7dd0
INITIATING CONNECTION Sep 30 08:37:33.509 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
INITIATING CONNECTION Sep 30 08:37:33.528 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3163e7dd0
INITIATING CONNECTION Sep 30 08:37:33.557 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
INITIATING CONNECTION Sep 30 08:37:33.598 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
INITIATING CONNECTION Sep 30 08:37:33.624 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
INITIATING CONNECTION Sep 30 08:37:33.646 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
INITIATING CONNECTION Sep 30 08:38:26.315 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc31686fa30
INITIATING CONNECTION Sep 30 08:38:26.316 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316fcc7d0
INITIATING CONNECTION Sep 30 08:38:26.316 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3170d8a90
INITIATING CONNECTION Sep 30 08:38:26.317 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc318521490
INITIATING CONNECTION Sep 30 08:38:26.317 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316e81b30
INITIATING CONNECTION Sep 30 08:38:26.317 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc316fdf410
INITIATING CONNECTION Sep 30 08:38:26.318 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315d3a890
INITIATING CONNECTION Sep 30 08:38:26.320 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316774270
INITIATING CONNECTION Sep 30 08:38:26.350 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316728a90
INITIATING CONNECTION Sep 30 08:38:26.350 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
INITIATING CONNECTION Sep 30 08:38:26.495 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316774270
INITIATING CONNECTION Sep 30 08:38:26.538 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
INITIATING CONNECTION Sep 30 08:38:26.591 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
INITIATING CONNECTION Sep 30 08:38:26.619 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
INITIATING CONNECTION Sep 30 08:38:26.642 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
INITIATING CONNECTION Sep 30 08:38:26.666 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
INITIATING CONNECTION Sep 30 08:39:19.257 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc31662a980
INITIATING CONNECTION Sep 30 08:39:19.258 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3182e6150
INITIATING CONNECTION Sep 30 08:39:19.258 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31605c330
INITIATING CONNECTION Sep 30 08:39:19.258 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3184b79c0
INITIATING CONNECTION Sep 30 08:39:19.258 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31658f5b0
INITIATING CONNECTION Sep 30 08:39:19.259 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc316e03950
INITIATING CONNECTION Sep 30 08:39:19.259 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3160d8c80
INITIATING CONNECTION Sep 30 08:39:19.265 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31662b000
INITIATING CONNECTION Sep 30 08:39:19.287 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316073530
INITIATING CONNECTION Sep 30 08:39:19.287 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
INITIATING CONNECTION Sep 30 08:39:19.420 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31662b000
INITIATING CONNECTION Sep 30 08:39:19.457 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
INITIATING CONNECTION Sep 30 08:39:19.505 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
INITIATING CONNECTION Sep 30 08:39:19.531 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
INITIATING CONNECTION Sep 30 08:39:19.552 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
INITIATING CONNECTION Sep 30 08:39:19.573 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
INITIATING CONNECTION Sep 30 08:40:11.346 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3161c6e50
INITIATING CONNECTION Sep 30 08:40:11.347 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc316becee0
INITIATING CONNECTION Sep 30 08:40:11.348 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31679c620
INITIATING CONNECTION Sep 30 08:40:11.349 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3144ad030
INITIATING CONNECTION Sep 30 08:40:11.349 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31b8d0250
INITIATING CONNECTION Sep 30 08:40:11.349 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc3158e5b50
INITIATING CONNECTION Sep 30 08:40:11.349 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc316728a90
INITIATING CONNECTION Sep 30 08:40:11.363 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315c576d0
INITIATING CONNECTION Sep 30 08:40:11.518 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
INITIATING CONNECTION Sep 30 08:40:11.518 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3168cf630
INITIATING CONNECTION Sep 30 08:40:11.548 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
INITIATING CONNECTION Sep 30 08:40:11.568 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3168cf630
INITIATING CONNECTION Sep 30 08:40:11.597 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
INITIATING CONNECTION Sep 30 08:40:11.638 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
INITIATING CONNECTION Sep 30 08:40:11.660 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
INITIATING CONNECTION Sep 30 08:40:11.683 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
INITIATING CONNECTION Sep 30 08:41:06.173 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318297540
INITIATING CONNECTION Sep 30 08:41:06.175 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31b9c7b90
INITIATING CONNECTION Sep 30 08:41:06.175 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc314144080
INITIATING CONNECTION Sep 30 08:41:06.175 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315d435e0
INITIATING CONNECTION Sep 30 08:41:06.175 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3167306a0
INITIATING CONNECTION Sep 30 08:41:06.175 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31680f3e0
INITIATING CONNECTION Sep 30 08:41:06.175 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3170d8a90
INITIATING CONNECTION Sep 30 08:41:06.197 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31671e630
INITIATING CONNECTION Sep 30 08:41:06.223 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
INITIATING CONNECTION Sep 30 08:41:06.223 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318569a40
INITIATING CONNECTION Sep 30 08:41:06.376 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
INITIATING CONNECTION Sep 30 08:41:06.396 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318569a40
INITIATING CONNECTION Sep 30 08:41:06.431 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
INITIATING CONNECTION Sep 30 08:41:06.475 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
INITIATING CONNECTION Sep 30 08:41:06.503 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
INITIATING CONNECTION Sep 30 08:41:06.527 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
INITIATING CONNECTION Sep 30 08:41:59.159 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3160bc120
INITIATING CONNECTION Sep 30 08:41:59.160 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316e16c90
INITIATING CONNECTION Sep 30 08:41:59.160 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3161e71f0
INITIATING CONNECTION Sep 30 08:41:59.161 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc315f45120
INITIATING CONNECTION Sep 30 08:41:59.161 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3170d94c0
INITIATING CONNECTION Sep 30 08:41:59.161 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3174bc990
INITIATING CONNECTION Sep 30 08:41:59.161 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31820b7d0
INITIATING CONNECTION Sep 30 08:41:59.174 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3162884e0
INITIATING CONNECTION Sep 30 08:41:59.189 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
INITIATING CONNECTION Sep 30 08:41:59.189 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
INITIATING CONNECTION Sep 30 08:41:59.344 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
INITIATING CONNECTION Sep 30 08:41:59.363 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
INITIATING CONNECTION Sep 30 08:41:59.409 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
INITIATING CONNECTION Sep 30 08:41:59.430 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
INITIATING CONNECTION Sep 30 08:41:59.450 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
INITIATING CONNECTION Sep 30 08:41:59.471 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
INITIATING CONNECTION Sep 30 08:42:51.209 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31a613830
INITIATING CONNECTION Sep 30 08:42:51.210 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3168ae8d0
INITIATING CONNECTION Sep 30 08:42:51.210 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3161d6110
INITIATING CONNECTION Sep 30 08:42:51.211 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315de6190
INITIATING CONNECTION Sep 30 08:42:51.211 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc316482400
INITIATING CONNECTION Sep 30 08:42:51.211 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3167069e0
INITIATING CONNECTION Sep 30 08:42:51.211 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31829f120
INITIATING CONNECTION Sep 30 08:42:51.224 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3159e76e0
INITIATING CONNECTION Sep 30 08:42:51.372 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
INITIATING CONNECTION Sep 30 08:42:51.372 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
INITIATING CONNECTION Sep 30 08:42:51.402 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
INITIATING CONNECTION Sep 30 08:42:51.421 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
INITIATING CONNECTION Sep 30 08:42:51.466 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
INITIATING CONNECTION Sep 30 08:42:51.492 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
INITIATING CONNECTION Sep 30 08:42:51.514 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
INITIATING CONNECTION Sep 30 08:42:51.536 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
INITIATING CONNECTION Sep 30 09:43:23.246 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc315d40d90
INITIATING CONNECTION Sep 30 09:43:23.246 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc315ad1930
INITIATING CONNECTION Sep 30 09:43:23.246 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc316c27e30
INITIATING CONNECTION Sep 30 09:43:23.246 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315adf230
INITIATING CONNECTION Sep 30 09:43:23.246 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315d49010
INITIATING CONNECTION Sep 30 09:43:23.246 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159a1ea0
INITIATING CONNECTION Sep 30 09:43:23.246 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc318691eb0
INITIATING CONNECTION Sep 30 09:43:23.250 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315f45120
INITIATING CONNECTION Sep 30 09:43:23.311 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e1b2d0
INITIATING CONNECTION Sep 30 09:43:23.311 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
INITIATING CONNECTION Sep 30 09:43:23.427 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315f45120
INITIATING CONNECTION Sep 30 09:43:23.471 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
INITIATING CONNECTION Sep 30 09:43:23.524 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
INITIATING CONNECTION Sep 30 09:43:23.547 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
INITIATING CONNECTION Sep 30 09:43:23.574 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
INITIATING CONNECTION Sep 30 09:43:23.598 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
INITIATING CONNECTION Sep 30 10:06:17.592 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159227c0
INITIATING CONNECTION Sep 30 10:06:17.596 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3174e7bd0
INITIATING CONNECTION Sep 30 10:06:17.598 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315e08640
INITIATING CONNECTION Sep 30 10:06:18.674 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
INITIATING CONNECTION Sep 30 10:06:19.483 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318462600
INITIATING CONNECTION Sep 30 10:06:19.539 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3162d4270
INITIATING CONNECTION Sep 30 10:06:19.564 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159227c0
INITIATING CONNECTION Sep 30 10:06:19.582 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
INITIATING CONNECTION Sep 30 10:06:19.653 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
INITIATING CONNECTION Sep 30 10:06:19.674 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
INITIATING CONNECTION Sep 30 10:06:19.725 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
INITIATING CONNECTION Sep 30 10:06:19.747 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
INITIATING CONNECTION Sep 30 10:07:19.496 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316491d10
INITIATING CONNECTION Sep 30 10:07:19.523 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3144bad30
INITIATING CONNECTION Sep 30 10:07:19.531 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
INITIATING CONNECTION Sep 30 10:07:19.534 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3172b7640
INITIATING CONNECTION Sep 30 10:07:19.550 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315cbb960
INITIATING CONNECTION Sep 30 10:07:19.626 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315842910
INITIATING CONNECTION Sep 30 10:07:19.665 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316491d10
INITIATING CONNECTION Sep 30 10:07:19.715 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
INITIATING CONNECTION Sep 30 10:07:19.805 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
INITIATING CONNECTION Sep 30 10:07:19.854 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
INITIATING CONNECTION Sep 30 10:07:19.892 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
INITIATING CONNECTION Sep 30 10:07:19.915 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
INITIATING CONNECTION Sep 30 10:08:19.527 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3162aa260
INITIATING CONNECTION Sep 30 10:08:19.553 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3162e8510
INITIATING CONNECTION Sep 30 10:08:19.555 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315ac9950
INITIATING CONNECTION Sep 30 10:08:19.564 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
INITIATING CONNECTION Sep 30 10:08:19.582 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3146b1020
INITIATING CONNECTION Sep 30 10:08:19.685 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3163d82c0
INITIATING CONNECTION Sep 30 10:08:19.705 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3162aa260
INITIATING CONNECTION Sep 30 10:08:19.756 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
INITIATING CONNECTION Sep 30 10:08:19.800 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
INITIATING CONNECTION Sep 30 10:08:19.852 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
INITIATING CONNECTION Sep 30 10:08:19.876 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
INITIATING CONNECTION Sep 30 10:08:19.898 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0

Shared Variable Engine not always started

I'm experiencing an intermittent problem with the LabVIEW variable engine. The National Instruments Variable Engine service is configured to start automatically with Windows but that doesn't seem to always be the case. Every now and then I'll load my application only to find red LED indicators on all of the controls accessing my shared variables. I'll bring up the variable manager and stop/start the service, restart my application and then they're all green LEDs and everything works. Any idea what might be causing this?
Thanks,
- Kevin Handy

Hi Kevin. I don't know what causes the problem, but I have seen it on our systems as well.
Our solution was to have our application stop and then start the variable engine every time
it launches. Stopping might not be ok for you depending on how your applications are
architected, but for us it is fine.
We use two System Exec.vi calls, with the following strings:
net stop "national instruments variable engine"
net start "national instruments variable engine"
Haven't had any instances of the application coming up w/o the variable engine since
we added this initialization step.
Matt

[SOLVED]systemd won't start my /etc/rc.local

I was trying to emulate rc.local behaviour with this:
/usr/lib/systemd/system/rc-local.service
[Unit]
Description=/etc/rc.local Compatibility
ConditionPathExists=/etc/rc.local
[Service]
Type=forking
ExecStart=/etc/rc.local start
TimeoutSec=0
StandardOutput=tty
RemainAfterExit=yes
SysVStartPriority=99
[Install]
WantedBy=multi-user.target
and my
/etc/rc-local
looks like this
modprobe -r samsung_laptop
But it's not working. When I execute sudo systemctl status rc-local.service I get
rc-local.service - /etc/rc.local Compatibility
Loaded: loaded (/usr/lib/systemd/system/rc-local.service; enabled)
Active: failed (Result: exit-code) since Fri 2013-03-29 17:54:16 CET; 5min ago
Process: 745 ExecStart=/etc/rc.local start (code=exited, status=203/EXEC)
Last edited by Neky (2013-03-29 18:31:39)

Why do you have "start" as an argument to /etc/rc.local?
Also, for what you are trying to achieve, why not simply blacklist the module in /etc/modrpobe.d? Then it would not be loaded under any circumstances. Also if this is out of fear of the UEFI bug, I believe that for this particular module, there has been a patch included in the latest kernels that protects this from happening by not allowing writes to the NVRAM if it is 50% full or more.

[solved] gdm not showing user list and not recognizing gconf

I installed gdm2setup from aur and ran it as root, and since then gdm will no longer display a user browser to select my user from, I have to manually type in the user name and password to login.
I uninstalled gdm2setup, and then did a force reinstall for gdm (pacman -S --force gdm)
Then I rebooted, and as I mentioned, the user browser does not display.
I edited /etc/gdm/custom.conf so that it shows:
[greeter]
Browser=1
...but still no luck.
I made sure that gconf says that disable_user_list is not true, and it isn't.
gconftool-2 --get /apps/gdm/simple-greeter/disable_user_list
false
So I don't know what else to do, or why this is happening.
If anyone can help it would be greatly appreciated.
EDIT: Here is the most recent :0-greeter.log after a fresh reboot
No idea if any of this is related to my problem.
# cat /var/log/gdm/\:0-greeter.log
** (<unknown>:2058): DEBUG: Client registered with session manager: /org/gnome/SessionManager/Client1
gnome-session[2050]: WARNING: Could not launch application 'gnome-power-manager.desktop': Unable to start application: Failed to execute child process "gnome-power-manager" (No such file or directory)
** (process:2077): DEBUG: Greeter session pid=2077 display=:0.0 xauthority=/var/run/gdm/auth-for-gdm-JngQ5L/database
gdm-simple-greeter[2077]: Gtk-WARNING: gtkwidget.c:5676: widget not within a GtkWindow
gdm-simple-greeter[2077]: WARNING: Unable to read from file /etc/arch-release
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x160002b (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x160002b (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x160002b (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
Window manager warning: Log level 16: Failed to send buffer
gdm-simple-greeter[2077]: WARNING: Failed to send buffer
Window manager warning: Log level 16: Failed to send buffer
(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(gnome-settings-daemon:2059): atk-bridge-WARNING **: IOR not set.
(polkit-gnome-authentication-agent-1:2076): polkit-gnome-1-WARNING **: Error enumerating temporary authorizations: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine session the caller is in
(polkit-gnome-authentication-agent-1:2076): polkit-gnome-1-WARNING **: Error enumerating temporary authorizations: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine session the caller is in
(polkit-gnome-authentication-agent-1:2076): polkit-gnome-1-WARNING **: Error enumerating temporary authorizations: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine session the caller is in
(polkit-gnome-authentication-agent-1:2076): polkit-gnome-1-WARNING **: Error enumerating temporary authorizations: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine session the caller is in
(polkit-gnome-authentication-agent-1:2076): polkit-gnome-1-WARNING **: Error enumerating temporary authorizations: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine session the caller is in
EDIT#2
Solved!
sudo -u gdm gconftool-2 --set --type boolean /apps/gdm/simple-greeter/disable_user_list false
Last edited by goplexian (2010-10-13 10:56:29)

I want to set disable_user_list to true, but If I execute this
sudo -u gdm gconftool-2 --set --type boolean /apps/gdm/simple-greeter/disable_user_list true
I'm asked for a password ...
EDIT:
this line was commented in my sudoers file
%wheel ALL=(ALL) SETENV: ALL
Last edited by SiD (2010-12-02 19:34:46)

.xintirc not always starting openbox

Hi,
till now I managed to fix all problems with arch by investigating and reading but this one drives me crazy.
After I launch the "Your .xsession" from Qingy, Openbox starts if I am lucky but never if I use Qingy to start this session at startup.
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
setxkbmap -option terminate:ctrl_alt_bksp &
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && echo "$f" >> ~/.xinitrc.log && . "$f"
done
unset f
fi
exec /usr/bin/openbox-session
But if I change my .xsession so this:
#!/bin/sh
# ~/.xsession
# Executed by xdm/gdm/kdm at login
exec openbox-session
#/bin/bash --login -i ~/.xinitrc
Openbox starts always for me.
Does anyone has a clue for me, why I see this behavior from my netbook?
Regards,
Dominik

Inxsible wrote:Maybe something under your /etc/X11/xinit/xinitrc.d is holding it up. Everything that you run from the .xinitrc should have a & at the end to background it sorta. If something gets held up, your
exec /usr/bin/openbox-session will not be executed.
Sorry, I didn't mention that I commented out the part of .xinitrc that calls the files in xinitrc.d. The only thing in there is dbus. So the only thing that I suspect is /bin/bash --login -i ~/.xinitrc not working but I have no clou about how to debug that.
Thank you for your input, it helped me think things over an I now go and check if I missed some thing.
Regards,
Dominik
edit:
I did some more testing and it didn't gave me more info but I think qingy and bash --login in combination are my problem because if i login first to a shell and startx all is well.
Last edited by slalomsk8er (2011-04-15 20:52:55)

MSI 270x Gaming tf - one fan not always start

Hi,
i bought recently MSI 270x gaming and mine problem was high temperatures. I discovered that one of the fan doesnt work (it look like he had too less voltage to start). I touch him gently and he start work fine for few days (shut down pc for night). Sadly yesterday he wont start again on turn pc (it look like turn power up -> both fans start rotate few times, they stop and next they go on little higher rpm - this is moment when one of fans have troubles).
Fan look really fine, doesnt have any resistance to rotate when you touch him, its look more like problem with control from voltage system.
Its possible to change video card bios in way to give more power to fans on start (i think this will solve problem with not starting fan).
Here is mine vbios h.ttp://www.filedropper.com/pitcairn

There have been several issues reported about fans on this card model. Seems a batch of this are simply bad. Contact MSI about it or contact reseller for rma. >>How to contact MSI.<<

[SOLVED] systemd-udevd using 100% CPU and monitors go to sleep on boot

Hi,
Turned my PC on this morning to find an issue with the monitors going to sleep immediately after booting. The boot process is usually slim autologin to a cinnamon session. I can see as far as entering my LUKS passphrase, followed by a few additional lines, followed by blank monitors and monitors entering power saving mode.
Booting with nomodeset on the kernel command line allows me to boot to a terminal and I can login etc, but obviously X doesn't start. I'm using xf86-video-ati drivers.
When booting with KMS enabled I also have a runaway systemd-udevd process which is thrashing my processor and I'm unable to kill it (I've tried kill -9 and still it persists).
The PC was working fine when I shut it down last night. No updates have been performed since, and no configuration changes have been made. I did notice that the power management dialog in the settings failed to open though.
Any suggestions would be welcome please, as I've now lost half a day trying to get this resolved.
TIA
X.
Edit: I've also tried downgrading xserver to 1.15, xf86-video-ati and the associated dependencies with no change.
Edit2: I've also disabled slim and rebooted and the same thing happens - so I don't believe it's an issue with X but with KMS.
Edit3: Booting with acpi=off on the kernel command line also fails with the same result.
Last edited by xanthi (2014-07-30 13:55:58)

Turned out to be an issue with libdrm. Apparently I had run some updates yesterday before shutting down, but they didn't appear in pacman.log; instead I found them by looking in the pacman package cache and found:
-rw-r--r-- 1 root root 110072 Jul 29 22:59 lib32-libdrm-2.4.56-1-x86_64.pkg.tar.xz
-rw-r--r-- 1 root root 160996 Jul 29 22:55 libdrm-2.4.56-1-x86_64.pkg.tar.xz
Downgraded [lib32-]libdrm packages to 2.4.54-1, rebooted, and success.

MacBook Air does not finish start up and has a white screen, any suggestions?

It seems like the start up disk is full, but I can only restart or shut down

Reinstalling Lion/Mountain Lion Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
Freeing Up Space on The Hard Drive
1. See Lion's Storage Display.
2. You can remove data from your Home folder except for the /Home/Library/ folder.
3. Visit The XLab FAQs and read the FAQ on freeing up space on your hard drive.
4. Also see Freeing space on your Mac OS X startup disk.
5. See Where did my Disk Space go?.
6. See The Storage Display.
You must Empty the Trash in order to recover the space they occupied on the hard drive.
You should consider replacing the drive with a larger one. Check out OWC for drives, tutorials, and toolkits.
Try using OmniDiskSweeper 1.8 or GrandPerspective to search your drive for large files and where they are located.

[SOLVED] systemd not alway starts dnsmasq and minidlna service

Similar Messages

Maybe you are looking for