[Dovecot] Worse now: Cores
Worse now: I get stuff such as
in my log. What is dovecot trying to do and why?
Kris
-- Kristian =?iso-8859-15?q?K=F6hntopp?= kris@xn--khntopp-90a.de
Kristian Koehntopp, on 12/5/2007 1:38 PM, said the following:
Worse now: I get stuff such as
in my log. What is dovecot trying to do and why?
You need to provide more info...
dovecot -n output for starters... All anyone knows so far is you're EITHER on 1.0rc14, or 1.0.8, MAYBE...
--
Best regards,
Charles
On Wednesday, 5. December 2007 19:49:28 Charles Marcus wrote:
Kristian Koehntopp, on 12/5/2007 1:38 PM, said the following:
Worse now: I get stuff such as
in my log. What is dovecot trying to do and why?
You need to provide more info...
dovecot -n output for starters... All anyone knows so far is you're EITHER on 1.0rc14, or 1.0.8, MAYBE...
I am in the process of moving my mailboxes from an overloaded cyrus-box to a new dovecot installation. The suse-supplied 1.0.rc14 did break down with signal 6 asserts "seq 1 < seq2 ...", so I compiled a download of 1.0.8 instead. This did not change a thing.
Downgraded from self-compiled 1.0.8 back to 1.0.rc14 as supplied by suse, deleted all dovecot files in Maildir to have them regenerated.
Here is dovecot -n of the current install:
h743107:~ # /usr/sbin/dovecot -n # /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ syslog_facility: local6 listen: 85.214.35.184 ssl_cert_file: /etc/dovecot/imap.pem ssl_key_file: /etc/dovecot/imap.pem ssl_cipher_list: ALL:!LOW login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_greeting: server ready. verbose_proctitle: yes first_valid_uid: 1000 last_valid_uid: 60000 mail_location: maildir:~/Maildir mail_debug: yes maildir_copy_with_hardlinks: yes imap_client_workarounds: delay-newmail outlook-idle tb-extra-mailbox-sep auth default: mechanisms: plain login passdb: driver: pam args: dovecot userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 432 group: mail
-- Kristian =?iso-8859-15?q?K=F6hntopp?= kris@xn--khntopp-90a.de
On Wed, 2007-12-05 at 19:57 +0100, Kristian Koehntopp wrote:
On Wednesday, 5. December 2007 19:49:28 Charles Marcus wrote:
Kristian Koehntopp, on 12/5/2007 1:38 PM, said the following:
Worse now: I get stuff such as
in my log. What is dovecot trying to do and why?
You need to provide more info...
dovecot -n output for starters... All anyone knows so far is you're EITHER on 1.0rc14, or 1.0.8, MAYBE...
I am in the process of moving my mailboxes from an overloaded cyrus-box to a new dovecot installation. The suse-supplied 1.0.rc14 did break down with signal 6 asserts "seq 1 < seq2 ...", so I compiled a download of 1.0.8 instead. This did not change a thing.
How easily can you crash it? What do you use as filesystem?
On Wednesday, 5. December 2007 20:21:32 Timo Sirainen wrote:
I am in the process of moving my mailboxes from an overloaded cyrus-box to a new dovecot installation. The suse-supplied 1.0.rc14 did break down with signal 6 asserts "seq 1 < seq2 ...", so I compiled a download of 1.0.8 instead. This did not change a thing.
How easily can you crash it? What do you use as filesystem?
h743107:/var/log # grep signal dovecot.log | perl -n -e '($m = $_ ) =~ /(dovecot: .*signal.*)/ and ( $m = $1 ) =~ s/child \d+/child PID/ and print "$m\n";'| sort | uniq -c 17 dovecot: child PID (imap) killed with signal 11 607 dovecot: child PID (imap) killed with signal 6
h743107:/var/log # head -1 dovecot.log Dec 1 23:31:10 h743107 dovecot: Dovecot v1.0.rc14 starting up h743107:/var/log # tail -1 dovecot.log Dec 5 20:41:18 h743107 dovecot: IMAP(azundris): Disconnected: Logged out
h743107:/var/log # df -Th Filesystem Type Size Used Avail Use% Mounted on /dev/sda3 ext3 149G 6.8G 135G 5% / udev tmpfs 506M 88K 506M 1% /dev /dev/sda1 ext2 54M 7.2M 44M 15% /boot /dev/sdb2 reiserfs 153G 38G 115G 25% /home
h743107:/var/log # cat /etc/SuSE-release openSUSE 10.2 (i586) VERSION = 10.2
I am using INBOX as $HOME/Maildir/, this is on reiserfs. The / is ext3 with dir_index.
Kris
-- Kristian =?iso-8859-15?q?K=F6hntopp?= kris@xn--khntopp-90a.de
On Wed, 2007-12-05 at 20:43 +0100, Kristian Koehntopp wrote:
On Wednesday, 5. December 2007 20:21:32 Timo Sirainen wrote:
I am in the process of moving my mailboxes from an overloaded cyrus-box to a new dovecot installation. The suse-supplied 1.0.rc14 did break down with signal 6 asserts "seq 1 < seq2 ...", so I compiled a download of 1.0.8 instead. This did not change a thing.
How easily can you crash it? What do you use as filesystem?
h743107:/var/log # grep signal dovecot.log | perl -n -e '($m = $_ ) =~ /(dovecot: .*signal.*)/ and ( $m = $1 ) =~ s/child \d+/child PID/ and print "$m\n";'| sort | uniq -c 17 dovecot: child PID (imap) killed with signal 11 607 dovecot: child PID (imap) killed with signal 6
h743107:/var/log # head -1 dovecot.log Dec 1 23:31:10 h743107 dovecot: Dovecot v1.0.rc14 starting up h743107:/var/log # tail -1 dovecot.log Dec 5 20:41:18 h743107 dovecot: IMAP(azundris): Disconnected: Logged out
Either your users are doing something really strange, or there's something wrong with the server. v1.0.x has worked pretty well for a lot of people, so I have trouble believing that the real problem here is with Dovecot.
The assert you first mentioned happens if there's broken data in dovecot.index.log file. v1.1 handles this by logging an error instead of crashing. But broken data should never be written to dovecot.index.log in the first place.
The glibc free() error then is a pretty serious problem. It just should never happen no matter what you do. The backtrace shows that it's happening on commit path when changing message flags. There's no way there's a bug in there, so either the heap was corrupted earlier by another code path, or there's something wrong with the server's memory.
If it's heap corruption it's probably in some rarely run error handling path, in which case it would help to see what errors were logged by the same process before that.
Could you send more (or all) of those asserts, backtraces and other errors you see in logs to me privately?
On Wed, 2007-12-05 at 22:02 +0200, Timo Sirainen wrote:
The glibc free() error then is a pretty serious problem. It just should never happen no matter what you do. The backtrace shows that it's happening on commit path when changing message flags. There's no way there's a bug in there, so either the heap was corrupted earlier by another code path, or there's something wrong with the server's memory.
If it's heap corruption it's probably in some rarely run error handling path, in which case it would help to see what errors were logged by the same process before that.
And even better would be if you could get "bt full" gdb backtraces from them. The core files should get written to users' home directories, see http://dovecot.org/bugreport.html
On Wed, Dec 05, 2007 at 10:02:01PM +0200, Timo Sirainen wrote: [snip]
The glibc free() error then is a pretty serious problem. It just should never happen no matter what you do. The backtrace shows that it's [snap] I recently had similar (not dovecot related) troubles on a box with corrupt/defective memory. Do a memtest if you can; this could probably be a hardware defect.
best regards, Adi Kriegisch
participants (4)
-
Adi Kriegisch
-
Charles Marcus
-
Kristian Koehntopp
-
Timo Sirainen