SIGABRT on fetching mail
Hello,
I'm running dovecot with getmail for several months already, but today it's always crashing: "getmailrc: operation error (child pid 2995 killed by signal 6)".
The deliver process aborts due to an unknown reason.
tail /var/log/dovecot-info.log May 24 12:10:28 imap-login: Info: Login: user=peter.nabbefeld@gmx.de, method=PLAIN, rip=::1, lip=::1, mpid=2970, secured, session=
May 24 12:10:49 lda(peter.nabbefeld@gmx.de)<2994><kCP3FifD51yyCwAA7IIYzw>: Info: sieve: msgid=318D121B-37FC-4E8C-B4B8-93C87E0692B8@gmx.de: stored mail into mailbox 'Gesendet' May 24 15:14:30 imap-login: Info: Login: user=peter.nabbefeld@gmx.de, method=PLAIN, rip=::1, lip=::1, mpid=6304, secured, session=<+Rae+qGJ4IUAAAAAAAAAAAAAAAAAAAAB> May 24 15:14:31 imap(peter.nabbefeld@gmx.de)<6304><+Rae+qGJ4IUAAAAAAAAAAAAAAAAAAAAB>: Info: Connection closed (append finished 0.562 secs ago) in=157758 out=520 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 May 24 15:14:37 imap-login: Info: Login: user=peter.nabbefeld@gmx.de, method=PLAIN, rip=::1, lip=::1, mpid=6307, secured, session= May 24 15:55:28 imap-login: Info: Login: user=peter.nabbefeld@gmx.de, method=PLAIN, rip=::1, lip=::1, mpid=7205, secured, session=<T9ofjaKJgIYAAAAAAAAAAAAAAAAAAAAB> May 24 15:57:00 imap-login: Info: Login: user=peter.nabbefeld@gmx.de, method=PLAIN, rip=::1, lip=::1, mpid=7254, secured, session=<nT6XkqKJhIYAAAAAAAAAAAAAAAAAAAAB> May 24 16:08:22 imap-login: Info: Login: user=peter.nabbefeld@gmx.de, method=PLAIN, rip=::1, lip=::1, mpid=7507, secured, session=<LI40u6KJJIcAAAAAAAAAAAAAAAAAAAAB> May 24 16:16:40 imap(peter.nabbefeld@gmx.de)<6307> : Info: Connection closed (IDLE running for 0.001 + waiting input for 0.001 secs, 2 B in + 10 B out, state=wait-input) in=4251 out=137885 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=661 body_count=0 body_bytes=0 May 24 16:16:54 imap-login: Info: Login: user=peter.nabbefeld@gmx.de, method=PLAIN, rip=::1, lip=::1, mpid=7662, secured, session=
tail /var/log/dovecot.log May 24 11:25:33 master: Warning: Killed with signal 15 (by pid=12275 uid=0 code=kill) May 24 11:25:35 log(660): Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) May 24 12:10:47 lda(peter.nabbefeld@gmx.de)<2994><kCP3FifD51yyCwAA7IIYzw>: Warning: Failed to parse return-path header May 24 12:10:50 lda(peter.nabbefeld@gmx.de)<2995><hco1BirD51yzCwAA7IIYzw>: Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion failed: (ret != -2) May 24 12:10:50 lda(peter.nabbefeld@gmx.de)<2995><hco1BirD51yzCwAA7IIYzw>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xeee14) [0x7fd668defe14] -> /usr/lib/dovecot/libdovecot.so.0(+0xeee51) [0x7fd668defe51] -> /usr/lib/dovecot/libdovecot.so.0(+0x46268) [0x7fd668d47268] -> /usr/lib/dovecot/libdovecot.so.0(+0x4892e) [0x7fd668d4992e] -> /usr/lib/dovecot/libdovecot.so.0(+0x1004e6) [0x7fd668e014e6] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x81) [0x7fd668dfd681] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x36) [0x7fd668dfd8a6] -> /usr/lib/dovecot/libdovecot.so.0(+0x1058f8) [0x7fd668e068f8] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x81) [0x7fd668dfd681] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x36) [0x7fd668dfd8a6] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x4c) [0x7fd668dfe33c] -> /usr/lib/dovecot/libdovecot.so.0(io_stream_copy+0x8a) [0x7fd668e18aba] -> /usr/lib/dovecot/libdovecot.so.0(+0x119ac2) [0x7fd668e1aac2] -> /usr/lib/dovecot/libdovecot.so.0(o_stream_send_istream+0x4f) [0x7fd668e1874f] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_save_continue+0x2e) [0x7fd668f981ee] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_save_continue+0x27) [0x7fd668f36887] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_continue+0x44) [0x7fd668f083f4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_copy+0xf8) [0x7fd668ef9828] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_copy+0x59) [0x7fd668f32639] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x3d5c) [0x7fd66902ad5c] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x10eec) [0x7fd668a90eec] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x58981) [0x7fd668f08981] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x4e6df) [0x7fd66676e6df] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x4e5) [0x7fd666764065] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x57259) [0x7fd666777259] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_multiscript_run+0xa2) [0x7fd6667783f2] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x3d45) [0x7fd668cecd45] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0xf9) [0x7fd66902c229]
How can I find out which message is causing the crash?
It would be very helpful, if the message's subject and receipt time could be logged in case of an abort or anything else that could help identify the corrupt message. This would also enable me to send You the message for further investigation (if appropriate).
Kind regards Peter
participants (1)
-
Peter Nabbefeld