I think they fixed it in git, but probably didn't apply it to 2.2.25. I would recommend trying the latest from git.
Sent from my iPhone > On Jul 27, 2016, at 10:46 AM, Michael Chen <michael.c...@rivetlogic.com> > wrote: > > I built from dovecot-2.2.25.tar.gz on Mac OSX 10.11.15 (El Capitan) the > usual way: > > CFLAGS=-I/usr/local/ssl/include LDFLAGS=-L/usr/local/ssl/lib ./configure > make > sudo make install > sudo /usr/local/sbin/dovecot > > It consistently crash on startup with the following entries in > /var/log/mail.log (edited backtrace): > > Jul 27 07:39:26 macbook-pro dovecot[70234]: master: Dovecot v2.2.25 > (7be1766) starting up for imap, pop3, lmtp > Jul 27 07:39:26 macbook-pro dovecot[70234]: master: Panic: kevent(EV_ADD, > READ, 60) failed: Bad file descriptor > Jul 27 07:39:26 macbook-pro dovecot[70234]: master: Error: Raw backtrace: > 2 libdovecot.0.dylib 0x00000001000dc3fb > default_fatal_finish + 43 > -> 3 libdovecot.0.dylib 0x00000001000dd4e0 > syslog_handler + 0 > -> 4 dovecot 0x0000000100026f8d > master_fatal_callback + 429 > -> 5 libdovecot.0.dylib 0x00000001000dca9f i_panic + 415 > -> 6 libdovecot.0.dylib 0x00000001000ff022 > io_loop_handle_add + 194 > -> 7 libdovecot.0.dylib 0x00000001000fb5f1 io_add_file > + 385 > -> 8 libdovecot.0.dylib 0x00000001000fb456 io_add + 118 > -> 9 libdovecot.0.dylib 0x0000000100102b83 > lib_signals_set_handler + 355 > -> 10 dovecot 0x0000000100027070 main_init + > 112 > -> 11 dovecot 0x0000000100026628 main + 2024 > -> 12 libdyld.dylib 0x00007fff889ac5ad start + 1 > > > It looks similar to this report: > > > http://article.gmane.org/gmane.mail.imap.dovecot/86319/match=panic+kevent > > HomeBrew installed 2.2.24, and it works in my Mac. Can someone confirm this > is a bug? > > I also built 2.2.25 with debug, but can't make it break at line > iolook-kqueue.c:67 > > i_panic("kevent(EV_ADD, READ, %d) failed: %m", io->fd); > > Thanks > > --mc > . > > -- > > > CONFIDENTIALITY NOTICE: This e-mail, including attachments, is for the sole > use of the intended recipient(s) and may contain confidential and privileged > information or otherwise be protected by law. Any unauthorized review, use, > disclosure or distribution is prohibited. If you are not the intended > recipient, please contact the sender and destroy all copies and the original > message.
