On 24.9.2012, at 17.55, Birta Levente wrote: > On 24/09/2012 17:32, Timo Sirainen wrote: >> On 23.9.2012, at 14.05, Joe Auty wrote: >> >>> #0 0x00007f789cd08e14 in hash_table_destroy () from >>> /usr/lib/dovecot/libdovecot.so.0 >>> (gdb) bt full >>> #0 0x00007f789cd08e14 in hash_table_destroy () from >>> /usr/lib/dovecot/libdovecot.so.0 >>> No symbol table info available. >>> #1 0x00007f789ccda054 in settings_parser_deinit () from >>> /usr/lib/dovecot/libdovecot.so.0 >>> No symbol table info available. >>> #2 0x00007f789ccff33d in master_service_settings_cache_deinit () from >>> /usr/lib/dovecot/libdovecot.so.0 >> >> Well, the good news is that it crashes only after it has already >> disconnected the client anyway. But I thought I fixed this bug in v2.1.10 >> and I'm not able to reproduce it myself.. Having debugging information >> available might show something useful. Try installing dovecot-dbg package >> and getting the bt full again? >> > > I have the same problem, but on centos 6.3 64bit. How can I give you the > debug information?
Show your doveconf -n output at least. As for debugging information, that would depend on how you installed Dovecot? From some RPM or sources?
