search for: log_io

...error 89 (Fatal failure) Segmentation Fault (core dumped) # /opt/SUNWspro/bin/dbx -f /opt/csw/sbin/dovecot core (dbx) where =>[1] hash_lookup(table = (nil), key = 0x68f6), line 159 in "hash.c" [2] child_process_lookup(pid = 26870), line 31 in "child-process.c" [3] log_it(log_io = 0x80b8598, line = 0x80b7d4a "DIGEST-MD5 mechanism can't be supported with given passdbs", continues = 0), line 129 in "log.c" [4] log_write_pending(log_io = 0x80b8598), line 52 in "log.c" [5] log_read(log_io = 0x80b8598), line 191 in "log.c" [6] l...

Hello, dovecot crashes when it receives -HUP signal. It happens always if there was some activity - for example, if I start dovecot, check any account through POP3 and then send -HUP to dovecot process, it crashes with the following log entry: segfault at 00000008 eip 0804d3fb esp bfdd3860 error 4 If there were no activity at all since starting, it does not crash. my dovecot -n output: #

...plain login gssapi digest-md5 passdb: driver: passwd args: blocking=yes userdb: driver: passwd args: blocking=yes Backtrace: #0 0x0000000000410337 in hash_lookup (table=0x0, key=0xa85) at hash.c:159 node = <value optimized out> #1 0x0000000000405dae in log_it (log_io=0x1736ee00, line=0x1736f922 "DIGEST-MD5 mechanism can't be supported with given passdbs", continues=false) at log.c:128 process = <value optimized out> log_type = LOG_TYPE_FATAL #2 0x0000000000405e48 in log_write_pending (log_io=0x1736ee00) at log.c:51...

I noticed these happen when one of my users searches his Trash folder which he doesn't empty. He uses thunderbird and it is reproducable. Feb 5 22:47:39 boomhauer dovecot: IMAP(username): file message-header-parser.c: line 350 (message_parse_header_next): assertion failed: +(IS_LWSP(line->value[0])) Feb 5 22:47:41 boomhauer dovecot: child 8022 (imap) killed with signal 6 Feb 5