Hello, I just migrated to 2.0.2 and see some
xx@localhost.redirectme.net (expanded fromxx@localhost): Command died with signal 6: "/usr/local/libexec/dovecot/dovecot-lda -c /etc/dovecot2.conf". Command output: doveconf: Panic: file settings-parser.c: line 1838 (settings_copy_deflist_unique): assertion failed: (dest_count == ccount) doveconf: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0 [0x9395c0] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x45) [0x9396b5] -> /usr/local/lib/dovecot/libdovecot.so.0 [0x938c78] -> /usr/local/lib/dovecot/libdovecot.so.0 [0x9183c7] -> /usr/local/lib/dovecot/libdovecot.so.0 [0x9182de] -> /usr/local/lib/dovecot/libdovecot.so.0(settings_parser_apply_changes+0x6f) [0x91849f] -> /usr/local/bin/doveconf(config_filter_parsers_get+0x25f) [0x804e8af] -> /usr/local/bin/doveconf(config_parse_file+0x6a8) [0x80502f8] -> /usr/local/bin/doveconf(main+0x21f) [0x804c43f] -> /lib/i686/nosegneg/libc.so.6(__libc_start_main+0xdc) [0x5c8e9c] -> /usr/local/bin/doveconf [0x804b291]
This does not happen always; most mails get delivered normally through the LDA. A command line call of doveconf yields no problems.
Any hints?
Best regards, Jakob Curdes
On 17.9.2010, at 20.54, Jakob Curdes wrote:
I just migrated to 2.0.2 and see some
xx@localhost.redirectme.net (expanded fromxx@localhost): Command died with signal 6: "/usr/local/libexec/dovecot/dovecot-lda -c /etc/dovecot2.conf". Command output: doveconf: Panic: file settings-parser.c: line 1838
Can you send your dovecot2.conf?
/usr/local/lib/dovecot/libdovecot.so.0(settings_parser_apply_changes+0x6f) [0x91849f] -> /usr/local/bin/doveconf(config_filter_parsers_get+0x25f) [0x804e8af] -> /usr/local/bin/doveconf(config_parse_file+0x6a8) [0x80502f8] -> /usr/local/bin/doveconf(main+0x21f) [0x804c43f] -> /lib/i686/nosegneg/libc.so.6(__libc_start_main+0xdc) [0x5c8e9c] -> /usr/local/bin/doveconf [0x804b291]
This does not happen always; most mails get delivered normally through the LDA. A command line call of doveconf yields no problems.
Strange, because it is doveconf that is crashing. You mean doveconf -c /etc/dovecot2.conf doesn't crash?
Strange, because it is doveconf that is crashing. You mean doveconf -c /etc/dovecot2.conf doesn't crash? No, it parses the config without errrors as far as I can see (below). It seems only to crash when called in the contect of the LDA - perhaps a permission problem that is not handled properly? On the other side, all config files and the conf.d directory are readable by everyone, just checked that. jc
doveconf: /usr/local/bin/doveconf [root@xxx jc]# /usr/local/bin/doveconf -c /etc/dovecot2.conf &> doveconf.out [root@xxx jc]# more doveconf.out # 2.0.2: /etc/dovecot2.conf # OS: Linux 2.6.18-194.3.1.el5xen i686 CentOS release 5.5 (Final) auth_anonymous_username = anonymous auth_cache_negative_ttl = 0 s auth_cache_size = 10485760 auth_cache_ttl = 1800 s (..) protocol sieve { mail_debug = yes }
On Sun, 2010-09-19 at 11:54 +0200, Jakob Curdes wrote:
Strange, because it is doveconf that is crashing. You mean doveconf -c /etc/dovecot2.conf doesn't crash? No, it parses the config without errrors as far as I can see (below).
Can you run it via valgrind? (Just install valgrind and run "valgrind doveconf")
It seems only to crash when called in the contect of the LDA - perhaps a permission problem that is not handled properly?
What parameters are you giving to dovecot-lda? I doubt it has to do with permissions.
I was one of the reporters of LDA crashes in early 2.0. versions; see http://markmail.org/message/glwsn2awi4t4we2b for the original post.
I confirm that problem is solved in 2.0.6, after 2 days of running with the new version I have not observed any LDA crashes. Thank you Timo for you work!
Jakob Curdes
participants (2)
-
Jakob Curdes
-
Timo Sirainen