On Wed, Aug 16, 2006 at 05:00:33PM +0300, Timo Sirainen wrote:
On Sat, 2006-08-12 at 22:03 -0700, Scott Ellis wrote:
I tried 20060812 nightly on NetBSD-current, and it fails (rc2 works "almost" perfectly) during auth:
Aug 12 21:42:07 intrepid dovecot: Dovecot v1.0.rc6 starting up Aug 12 21:42:15 intrepid dovecot: child 3534 (auth) killed with signal 11
Could you get gdb backtrace from it? The core should be written to /var/run/dovecot directory as long as you had high enough ulimit -c and hadn't changed auth_user from root.
And what passdb and userdb are you using? checkpassword?
I'm using checkpassword as the userdb and passdb. Still getting this problem with the "2nd" -latest of today (per the kqueue on BSD thread). Backtrace is as follows:
Core was generated by `dovecot-auth'. Program terminated with signal 11, Segmentation fault. #0 0x00000000004160d6 in sigchld_handler (signo=20, context=0x0) at passdb-checkpassword.c:147 147 request = hash_lookup(module->clients, POINTER_CAST(pid)); (gdb) bt #0 0x00000000004160d6 in sigchld_handler (signo=20, context=0x0) at passdb-checkpassword.c:147 #1 0x0000000000422599 in signal_read (context=0x0) at lib-signals.c:90 #2 0x0000000000422260 in io_loop_handler_run (ioloop=0x546000) at ioloop-kqueue.c:143 #3 0x000000000042161b in io_loop_run (ioloop=0x546000) at ioloop.c:280 #4 0x0000000000410dc6 in main (argc=1, argv=0x7f7fffffec00) at main.c:322 (gdb)
This is on NetBSD/amd64 -current (as of August 8th).
Needless to say, I can't try out the "fixed" kqueue functionality yet due to this issue. :-)
ScottE