Please disregard the below reported bug report. I experienced the
same problem today and this time "sleep" was not involved.
I rotate mail.log weekly. This morning I noticed that dovecot was no
longer logging to mail.log although, again, it was running fine.
Is it possible that dovecot has a problem after midnight and will not
log with the new day? Something is stopping dovecot from logging and
it appears that it might have to do with change of the day?
This is a new (two day old) dovecot installation. Coming from uw-
imap. It never exhibited this problem.
Thank you,
B. Bodger
Ronkonkoma, NY
On May 10, 2007, at 7:34 AM, Bruce Bodger wrote:
Version: dovecot --version: 1.0.0
OS: OS X - 10.4.9
Architecture: G5 Dual/1.8Ghz
Had a fairly normal time correction last night:
May 9 20:56:56 G518X2 ntpd[219]: time set -1.212733 s
Which dovecot duly noted:
May 9 20:56:56 G518X2 dovecot: auth(default): Time just moved
backwards by 1 seconds. I'll sleep now until we're back in present.
This morning all of the dovecot processes are running fine but
dovecot has stopped logging. (I have modified nothing in
dovecot.conf relative to logging: dovecot logs to syslog using the
"mail" syslog_facility.)
ps -aux | grep dovecot
root 53 0.0 -0.0 27772 544 ?? Ss 4:23PM
0:04.69 /usr/local/sbin/dovecot -F
root 79 0.0 -0.0 28176 556 ?? S 4:23PM
0:03.21 dovecot-auth
dovecot 9548 0.0 -0.0 27780 496 ?? S 7:12AM
0:00.05 imap-login
dovecot 9631 0.0 -0.0 27780 500 ?? S 7:17AM
0:00.03 imap-login
dovecot 9632 0.0 -0.0 27780 500 ?? S 7:17AM
0:00.03 imap-login
I am starting dovecot via OS X's launchdaemon facility thus the "-
F" command line switch requirement.
Sending a "kill -HUP" to the process did not get it to start logging.
Sending a "Kill -9" to the process forced a restart and logging
began again.
ps -aux | grep dovecot
root 9738 0.0 -0.0 27772 540 ?? Ss 7:26AM
0:00.03 /usr/local/sbin/dovecot -F
root 9739 0.0 -0.0 28176 544 ?? S 7:26AM
0:00.02 dovecot-auth
dovecot 9740 0.0 -0.0 27780 500 ?? S 7:26AM
0:00.02 imap-login
dovecot 9751 0.0 -0.0 27780 500 ?? S 7:27AM
0:00.01 imap-login
dovecot 9762 0.0 -0.0 27780 500 ?? S 7:27AM
0:00.01 imap-login
Before posting this bug I compared v1.0.0's /src/lib/ioloop.c to
that in the nightly snapshot and saw no adjustments in, what I
presumed to be, the relevant portion of the code.
Output of "dovecot -n"
protocols: imap
ssl_disable: yes
disable_plaintext_auth: no
login_dir: /usr/local/var/run/dovecot/login
login_executable: /usr/local/libexec/dovecot/imap-login
first_valid_uid: 490
mail_extra_groups: mail
mail_location: mbox:~/Library/Mail/IMAP:INBOX=/var/mail/%u:INDEX=%h/
Library/Mail/DOVECOT.indexes
dotlock_use_excl: yes
auth default:
mechanisms: plain login
passdb:
driver: pam
userdb:
driver: passwd
Thank you.
