[Dovecot] locking problem
I have one user who can't read his e-mail. The /var/log/mail.log file
has this statement.
dovecot: IMAP(<user>): Timeout while waiting for lock for transaction
log file /users/<user>/mail/.imap/INBOX/dovecot.index.log
I tried killing the imap daemons and removing the lock file, but it keeps coming back. Any idea what else to do?
This is the dovecot file:
dovecot -n
1.2.9: /etc/dovecot/dovecot.conf
OS: Linux 2.6.32-28-server x86_64 Ubuntu 10.04.3 LTS
log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/certs/ssl-cert-snakeoil.pem ssl_key_file: /etc/ssl/private/ssl-cert-snakeoil.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth-client mode: 432 user: postfix group: postfix
--myron
Myron Kowalski MoCoSIN Network/Systems Administrator Moravian College myron@moravian.edu (610) 861-1441
On 1.2.2012, at 16.09, myron wrote:
I have one user who can't read his e-mail. The /var/log/mail.log file has this statement.
dovecot: IMAP(<user>): Timeout while waiting for lock for transaction log file /users/<user>/mail/.imap/INBOX/dovecot.index.log
I tried killing the imap daemons and removing the lock file, but it keeps coming back. Any idea what else to do? .. mail_location: mbox:~/mail:INBOX=/var/mail/%u
How large is the /var/mail/<user> mbox file?
On Feb 1, 2012, at 3:24 PM, Timo Sirainen wrote:
On 1.2.2012, at 16.09, myron wrote:
I have one user who can't read his e-mail. The /var/log/mail.log
file has this statement.dovecot: IMAP(<user>): Timeout while waiting for lock for
transaction log file /users/<user>/mail/.imap/INBOX/dovecot.index.logI tried killing the imap daemons and removing the lock file, but it keeps coming back. Any idea what else to do? .. mail_location: mbox:~/mail:INBOX=/var/mail/%u
How large is the /var/mail/<user> mbox file?
-rw------- 1 <user> mail 15M 2012-02-01 14:46 /var/mail/<user>
Can I just zero out the 3 files in that directory.
6240 Jan 31 13:26 dovecot.index 165888 Jan 31 14:39 dovecot.index.cache 25100 Jan 31 14:42 dovecot.index.log
On 1.2.2012, at 22.43, myron wrote:
dovecot: IMAP(<user>): Timeout while waiting for lock for transaction log file /users/<user>/mail/.imap/INBOX/dovecot.index.log How large is the /var/mail/<user> mbox file?
-rw------- 1 <user> mail 15M 2012-02-01 14:46 /var/mail/<user>
OK, so not very big.
Can I just zero out the 3 files in that directory.
6240 Jan 31 13:26 dovecot.index 165888 Jan 31 14:39 dovecot.index.cache 25100 Jan 31 14:42 dovecot.index.log
You can delete them, but somehow I doubt that helps.. That error message anyway happens when a session has opened the mbox and is "syncing" it. This normally is a pretty fast operation, but the error message indicates that another session saw the first session doing it for over 3 minutes until it aborted.
Do you have hanging imap processes eating 100% CPU? That could explain it if Dovecot doesn't like something in the mbox file. Also there may have been some other reasons for this that are already fixed in newer versions.
On Feb 1, 2012, at 4:11 PM, Timo Sirainen wrote:
On 1.2.2012, at 22.43, myron wrote:
dovecot: IMAP(<user>): Timeout while waiting for lock for
transaction log file /users/<user>/mail/.imap/INBOX/ dovecot.index.log How large is the /var/mail/<user> mbox file?-rw------- 1 <user> mail 15M 2012-02-01 14:46 /var/mail/<user>
OK, so not very big.
His isn't, but I have users with 500MB to a GB mailbox. Could they be
the cause of the problem?
Can I just zero out the 3 files in that directory.
6240 Jan 31 13:26 dovecot.index 165888 Jan 31 14:39 dovecot.index.cache 25100 Jan 31 14:42 dovecot.index.log
You can delete them, but somehow I doubt that helps.. That error
message anyway happens when a session has opened the mbox and is
"syncing" it. This normally is a pretty fast operation, but the
error message indicates that another session saw the first session
doing it for over 3 minutes until it aborted.Do you have hanging imap processes eating 100% CPU?
Hardly anything: ps -eo pcpu,pid,user,args | sort -k 1 -r | head -20 %CPU PID USER COMMAND 0.0 9 root [events/0] 0.0 993 root /usr/sbin/sshd -D 0.0 984 root /usr/sbin/cupsd -C /etc/cups/cupsd.conf 0.0 9677 <different user> imap 0.0 9659 dovecot imap-login 0.0 959 root [ext4-dio-unwrit] 0.0 958 root [ext4-dio-unwrit] 0.0 957 root [jbd2/dm-1-8] 0.0 9442 root [lockd] 0.0 939 root [ext4-dio-unwrit] 0.0 938 root [ext4-dio-unwrit] 0.0 937 root [jbd2/dm-3-8] 0.0 930 root [ext4-dio-unwrit] 0.0 929 root [ext4-dio-unwrit] 0.0 928 root [jbd2/dm-2-8] 0.0 9192 root /usr/sbin/apache2 -k start 0.0 911 root [ext4-dio-unwrit] 0.0 910 root [ext4-dio-unwrit] 0.0 90 root [kconservative/1]
That could explain it if Dovecot doesn't like something in the mbox
file. Also there may have been some other reasons for this that are
already fixed in newer versions.
I looked at the upgrade list on the server and dovecot isn't showing
any upgrades via atp-get
participants (2)
-
myron
-
Timo Sirainen