dovecot: Nov 24 12:49:06 Panic: IMAP(user): file ioloop-notify- kqueue.c: line 66 (event_callback): assertion failed: (io->refcount == 1) dovecot: Nov 24 12:49:06 Error: IMAP(user): Raw backtrace: 2 imap 0x0000000100068e82 default_fatal_finish + 41 -> 3 imap 0x0000000100068eed i_syslog_fatal_handler + 0 -> 4 imap 0x0000000100068687 i_info + 0 -> 5 imap 0x000000010006fc0a event_callback + 216 -> 6 imap 0x000000010006fdea io_loop_handler_run + 272 -> 7 imap 0x000000010006f1bf io_loop_run + 38 -> 8 imap 0x000000010006a319 dotlock_create + 532 -> 9 imap 0x000000010006ac0f file_dotlock_create + 177 -> 10 imap 0x000000010001a925 maildir_uidlist_lock_timeout + 169 -> 11 imap 0x000000010001aa14 maildir_uidlist_sync_init + 66 -> 12 imap 0x0000000100017d48 maildir_sync_context + 299 -> 13 imap 0x000000010001809a maildir_storage_sync_init + 104 -> 14 imap 0x000000010003e183 mailbox_sync + 31 -> 15 imap 0x000000010000bcca imap_status_get + 132 -> 16 imap 0x0000000100005355 cmd_status + 230 -> 17 imap 0x0000000100006cb5 client_command_input + 33 -> 18 imap 0x0000000100006e62 client_command_input + 462 -> 19 imap 0x0000000100006f61 client_handle_input + 239 -> 20 imap 0x00000001000070e8 client_input + 151 -> 21 imap 0x000000010006fdea io_loop_handler_run + 272 -> 22 imap 0x000000010006f1bf io_loop_run + 38 -> 23 imap 0x000000010000e046 main + 1671 -> 24 imap 0x0000000100001558 start + 52 -> 25 ??? 0x0000000000000001 0x0 + 1 Dovecot-1.1.7 on Mac OS X. Fixed by http://hg.dovecot.org/dovecot-1.2/rev/2c111b572eee ? (Just guessing.)
On Nov 25, 2008, at 12:05 AM, Mike Abbott wrote:> dovecot: Nov 24 12:49:06 Panic: IMAP(user): file ioloop-notify- > kqueue.c: line 66 (event_callback): assertion failed: (io->refcount > == 1)..> 8 imap 0x000000010006a319 dotlock_create + 532 -> > 9 imap 0x000000010006ac0f file_dotlock_create + 177 -> > 10 imap 0x000000010001a925 maildir_uidlist_lock_timeout + 169 -> > 11 imap 0x000000010001aa14 maildir_uidlist_sync_init + 66 ->Is this random, common or reproducible? I guess it's possible that kqueue notifications are just completely broken currently. Anyway since other people haven't complained I'm pretty sure this is kqueue- specific bug..> Fixed by http://hg.dovecot.org/dovecot-1.2/rev/2c111b572eee ? (Just > guessing.)I don't think so. I did this to get the new auth-master lookup code working without breaking. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20081125/4f2cfc30/attachment-0002.bin>
> Is this random, common or reproducible?Seen only once so far.> I guess it's possible that kqueue notifications are just completely > broken currently.Oh, really?
On Monday 24 November 2008 23.14.55 Timo Sirainen wrote:> On Nov 25, 2008, at 12:05 AM, Mike Abbott wrote: > > dovecot: Nov 24 12:49:06 Panic: IMAP(user): file ioloop-notify- > > kqueue.c: line 66 (event_callback): assertion failed: (io->refcount > > == 1) > > .. > > > 8 imap 0x000000010006a319 dotlock_create + 532 -> > > 9 imap 0x000000010006ac0f file_dotlock_create + 177 -> > > 10 imap 0x000000010001a925 maildir_uidlist_lock_timeout + 169 > > -> 11 imap 0x000000010001aa14 maildir_uidlist_sync_init + 66 -> > > Is this random, common or reproducible? I guess it's possible that > kqueue notifications are just completely broken currently.8-\ I've been compiling dovecot with --with-notify=kqueue and --with-ioloop=kqueue on OpenBSD since 1.0. If it needs testing just let me know.> Anyway since other people haven't complained I'm pretty sure this is > kqueue-specific bug..I haven't seen this so far, fortunatelly. Daniel -- LEVAI Daniel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1