Menu
▾
▴
Re: [Fetchmail-users] The daemon runs (seen in top) but neve tries to connect
|
From: Ian B. <an...@fa...> - 2014-11-03 19:19:22
|
O Mon, Nov 03, 2014 at 06:39:28AM -0500, Jerry wrote: > On Mon, 3 Nov 2014 12:31:35 +0200, Ian Balchin stated: > > > Matthias, hello, > > > > see below > > > > On Sun, Nov 02, 2014 at 11:47:46PM +0100, Matthias Andree wrote: > > > Ian, > > > > > > can you get the logs of a run similar to: > > > > > > fetchmail --nosyslog --nodetach -vvv -d600 > > > > > > That should show something. Note that if running as root it will grab > > > /usr/local/etc/fetchmailrc, all other users will look at > > > $HOME/.fetchmailrc. We should then see where it hangs. > > > > > Starting afresh this morning and having made sure that all was as should > > be, having set for fetchmail user with fetchmailrc in /usr/local/etc As you > > can see with a system start fetchmail daemon is running from 11:27:54 But > > by the time i make a timestamp with an imap disconnect at 11:52:33 it has > > not yet made a pop3 call to receive mail. > > > > > > Nov 3 10:52:52 hestia fetchmail[907]: terminated with signal 15 > > Nov 3 11:26:57 hestia dovecot: dovecot: Killed with signal 15 (by pid=1020 > > uid=0 code=kill) Nov 3 11:26:57 hestia fetchmail[774]: terminated with > > signal 15 Nov 3 11:26:57 hestia postfix/postfix-script[1057]: stopping the > > Postfix mail system Nov 3 11:26:57 hestia postfix/master[758]: terminating > > on signal 15 Nov 3 11:27:53 hestia postfix/postfix-script[748]: starting > > the Postfix mail system Nov 3 11:27:53 hestia postfix/master[750]: daemon > > started -- version 2.11.1, configuration /usr/local/etc/postfix Nov 3 > > 11:27:54 hestia fetchmail[766]: starting fetchmail 6.3.26 daemon Nov 3 > > 11:27:54 hestia dovecot: Dovecot v1.2.17 starting up Nov 3 11:27:54 hestia > > dovecot: auth(default): passwd-file /usr/local/etc/passwd.dovecot: Read 1 > > users Nov 3 11:27:54 hestia dovecot: auth-worker(default): > > passwd-file /usr/local/etc/passwd.dovecot: Read 1 users Nov 3 11:27:55 > > hestia dovecot: auth(default): new auth connection: pid=861 Nov 3 11:27:55 > > hestia dovecot: auth(default): new auth connection: pid=860 Nov 3 11:27:55 > > hestia dovecot: auth(default): new auth connection: pid=864 Nov 3 11:27:55 > > hestia dovecot: auth(default): new auth connection: pid=863 Nov 3 11:27:55 > > hestia dovecot: auth(default): new auth connection: pid=859 Nov 3 11:27:55 > > hestia dovecot: auth(default): new auth connection: pid=862 Nov 3 11:28:53 > > hestia dovecot: auth(default): client in: AUTH 1 PLAIN > > service=imap lip=192.168.0.21 rip=192.168.0.15 > > lport=143 rport=49092 resp=<hidden> Nov 3 11:28:53 hestia > > dovecot: auth(default): passwd-file(nignog,192.168.0.15): lookup: > > user=inksi file=/usr/local/etc/passwd.dovecot Nov 3 11:28:53 hestia > > dovecot: auth(default): client out: OK 1 user=nignog Nov 3 > > 11:28:53 hestia dovecot: auth(default): master in: REQUEST 1 > > 862 1 Nov 3 11:28:53 hestia dovecot: auth-worker(default): > > passwd(nignog,192.168.0.15): lookup Nov 3 11:28:53 hestia dovecot: > > auth(default): master out: USER 1 inksi > > system_groups_user=nignog uid=1001 gid=1001 > > home=/home/nignog Nov 3 11:28:53 hestia dovecot: imap-login: Login: > > user=<nignog>, method=PLAIN, rip=192.168.0.15, lip=192.168.0.21 Nov 3 > > 11:28:54 hestia dovecot: auth(default): new auth connection: pid=866 Nov 3 > > 11:52:33 hestia dovecot: IMAP(nignog): Disconnected: Logged out > > bytes=2377/16968 > > > > If I run it as su it is woken up but that is all apart from the standard > > notice 'running as root strongly discouraged'. then: > > > > root@hestia:/usr/home/nignog # fetchmail --nosyslog --nodetach -vvv -d600 > > fetchmail: WARNING: Running as root is discouraged. > > Scratch list of UIDs: <empty> > > fetchmail: no mailservers have been specified. ****** is this line a > > clue? ***** root@hestia:/usr/home/nignog # > > > > > > so then the only option is to repeat the command as a user > > > > $ fetchmail --nosyslog --nodetach -vvv -d600 > > Old UID list from pop3.gormless.co.za: <empty> > > Old UID list from pop3.gormless.co.za: <empty> > > Old UID list from pop3.gormless.co.za: <empty> > > Old UID list from pop3.gormless.co.za: <empty> > > Scratch list of UIDs: <empty> > > fetchmail: starting fetchmail 6.3.26 daemon > > fetchmail: 6.3.26 querying pop3.gormless.co.za (protocol POP3) at Mon Nov > > 3 12:13:43 2014: poll started Trying to connect to > > 41.78.28.41/110...connected. fetchmail: POP3< +OK Dovecot ready. > > fetchmail: POP3> CAPA > > fetchmail: POP3< +OK > > fetchmail: POP3< CAPA > > fetchmail: POP3< TOP > > fetchmail: POP3< UIDL > > fetchmail: POP3< RESP-CODES > > fetchmail: POP3< PIPELINING > > fetchmail: POP3< AUTH-RESP-CODE > > fetchmail: POP3< STLS > > fetchmail: POP3< USER > > fetchmail: POP3< SASL CRAM-MD5 PLAIN LOGIN > > fetchmail: POP3< . > > fetchmail: POP3> AUTH CRAM-MD5 > > fetchmail: POP3< + PDkxNDkyMTkxNzI3NDk3NjcuMTQxNTAwOTYyNEBlbWFpbC1wcm94eXg+ > > fetchmail: decoded as <9149219172749767.1415009624@email-proxyx> > > fetchmail: POP3> > > aHlwYXRpYUBmYWJsZXMuY28uemEgOWU5YzVmZWFmNzRiY2I5MjRhYzY2NzkzOGM5YWVjMGQ= > > fetchmail: POP3< +OK Logged in. fetchmail: selecting or re-polling default > > folder fetchmail: POP3> STAT > > fetchmail: POP3< +OK 0 0 > > fetchmail: No mail for nignog@mydomain at pop3.gormless.co.za > > fetchmail: POP3> QUIT > > fetchmail: POP3< +OK Logging out. > > > > and it runs happily thereafter for multiple pops every 10 mins. > > > > Can you see anything there? > > Back only tonight. > > > > Ian > > 1) You have me confused here. Is this what your "fetchmailrc" entry looks > like: > > -rwx------ 1 fetchmail fetchmail 4.7K 2014-10-31 07:25:43 EDT fetchmailrc yes (but 1k) > > 2) cd to the /usr/local/etc directory and run as root: > > service fetchmail stop > > At that point fetchmail should be shut down. If not, post the error message. stopped. not to be seen in top. no error messages > > 3) Now still as root, enter: service fetchmail start > > If any error messages are displayed, show them here. > started. seen in top > 4) now, still as root, enter: service fetchmail awaken > > Post any error messages. root@hestia:/var/log # service fetchmail awaken Forcing fetchmail to check mailbox(es)... root@hestia:/var/log # the view from maillog: Nov 3 16:05:39 hestia fetchmail[766]: terminated with signal 15 Nov 3 16:08:50 hestia fetchmail[1342]: starting fetchmail 6.3.26 daemon Nov 3 16:10:30 hestia fetchmail[1342]: awakened by User defined signal 1 > > 5) If you want, and have not done so all ready, create a log file. cd > to /var/log and enter: touch "fetchmail.log" sans quotations and then change > the ownership and permissions. done > > chown fetchmail:fetchmail /var/log/fetchmail.log > chmod 0666 /var/log/fetchmail.log done > > In your "/usr/local/etc/fetchmailrc" file, enter the following: > > set logfile "/var/log/fetchmail.log" > set postmaster "postmaster" > set bouncemail > set no spambounce > set softbounce > set properties "" done > > You may need to change some of them; however, leave the logfile entry as is. > > Now, you will have to restart fetchmail for this to take effect. Again, as > root, service fetchmail restart done > > Post any error messages. none no apparent immediate connection either > > Good luck! didn't get any of that either first time around. from fetchmail.log fetchmail: starting fetchmail 6.3.26 daemon no timestamp :( - but after the best part of an hour that is all there is. Well, no mail to be collected, so .... I send an email to be picked up in case fetchmail was working secretly in the background root@hestia:/var/log # service fetchmail awaken Forcing fetchmail to check mailbox(es)... root@hestia:/var/log # tail -f -n 50 /var/log/fetchmail.log fetchmail: starting fetchmail 6.3.26 daemon fetchmail: 1 message for nignog@mydomain at pop3.imaginet.co.za (1261 octets). fetchmail: reading message nignog@myd...@po...:1 of 1 (1261 octets) flushed another email and another awaken fetchmail: awakened by User defined signal 1 fetchmail: 1 message for nignog@mydomain at pop3.imaginet.co.za (1284 octets). fetchmail: reading message nignog@myd...@po...:1 of 1 (1284 octets) flushed So fetchmail does check immediately after 'awaken' I suspected that fetchmail does check within the polling time but if there is nothing to fetch then it does not log this explicitly tailing fetchmail.log for a while shows no activity. So I sent another email, and within the cycle period it fetched this - repeatedly and reliably it seems. So I need to increase the verbosity, and add a time stamp, else revert to maillog. Is this possible? I see nothing in man pages or FAQ. Thank you for your patience. I will be back. Ian > > -- > Jerry > > ------------------------------------------------------------------------------ > _______________________________________________ > Fetchmail-users mailing list > Fet...@li... > https://lists.sourceforge.net/lists/listinfo/fetchmail-users |
