Quoting Timo Sirainen tss@iki.fi:
On 21.10.2004, at 19:12, jross@wykids.org wrote:
Are you sure everything got installed correctly? The backtrace was corrupted, and the above warning message also indicates that the core file was generated by different binary.
It appears to be a new installation. Here's the output of make install.
Well, continuing my stupid questions:
Are you sure the core file was produced by the same binary? ie. you're not starting some other version of Dovecot which was installed to /usr/sbin/ or somewhere else in path?
I'm running dovecot under daemontools.
jross@junior:/home/jross/dovecot-1.0-test49 $ ps -wwwaux | grep [d]ovecot _dovecot 2060 0.0 0.1 332 1548 ?? S 8:00AM 0:00.25 imap-login _dovecot 3364 0.0 0.1 356 1560 ?? S 8:04AM 0:00.24 imap-login _dovecot 23908 0.0 0.1 384 1560 ?? S 8:19AM 0:00.24 imap-login _dovecot 2323 0.0 0.1 332 1540 ?? S 8:36AM 0:00.25 imap-login _dovecot 4022 0.0 0.1 388 1544 ?? S 10:35AM 0:00.10 imap-login _dovecot 11148 0.0 0.1 340 1560 ?? S 10:37AM 0:00.09 imap-login root 30338 0.0 0.1 232 1060 ?? S 11:43AM 0:00.01 /usr/local/sbin/dovecot -F _dovecot 20461 0.0 0.1 212 1360 ?? S 11:43AM 0:00.01 imap-login root 26687 0.0 0.0 356 712 ?? S 11:43AM 0:00.01 dovecot-auth _dovecot 27465 0.0 0.1 260 1356 ?? S 11:43AM 0:00.01 imap-login _dovecot 6723 0.0 0.1 244 1360 ?? S 11:43AM 0:00.01 imap-login root 2646 0.0 0.0 68 404 C0- S 8Oct04 0:00.06 supervise dovecot
What passdb are you using?
passwd
I just tested with OpenBSD 3.5/sparc64, worked fine.
Hmmm...test49 runs fine with the exception of the problems I reported yesterday. I tried test50 yesterday but didn't have the time to make the changes to dovecot.conf so I reverted.
test50 gives me the same error as 51, so whatever is going on happened between test49 and test50. gdb also reports that the exec file is newer than the core file.
Hope that helps!
Jeff