[Dovecot] Seeing dovecot crash under rc6, seems to go almost exactly every 2.5 hours...
We're getting the following crash report, but I'm not sure it contains anything immediately useful (especially since we're running on a minority platform in OS X)... Anyone see where we might be able to resolve this? The crash doesn't kill existing imap processes, but dovecot/imap-login needs to be restarted.
Host Name: mailserver Date/Time: 2006-08-10 14:24:16.131 -0700 OS Version: 10.4.6 (Build 8I127) Report Version: 4
Command: dovecot Path: /opt/local/sbin/dovecot Parent: dovecot [10099]
Version: ??? (???)
PID: 13818 Thread: 0
Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000020
Thread 0 Crashed: 0 dovecot 0x0000482c log_set_prefix + 36 (log.c:190) 1 dovecot 0x000070b0 create_mail_process + 1576 (mail-process.c:535) 2 dovecot 0x00005150 auth_master_callback + 96 (login-process.c:92) 3 dovecot 0x00002d9c auth_process_input + 460 (auth-process.c:121) 4 dovecot 0x00017d58 io_loop_handler_run + 388 (ioloop-select.c:140) 5 dovecot 0x0001006c io_loop_run + 48 (ioloop.c:273) 6 dovecot 0x00008c54 main + 1816 (main.c:577) 7 dovecot 0x000020a8 _start + 344 (crt.c:272) 8 dovecot 0x00001f4c start + 60
Thread 0 crashed with PPC Thread State 64: srr0: 0x000000000000482c srr1: 0x100000000200d030 vrsave: 0x0000000000000000 cr: 0x84002404 xer: 0x0000000020000000 lr: 0x0000000000004810 ctr: 0x00000000901313a0 r0: 0x00000000000070b0 r1: 0x00000000bffff320 r2: 0x0000000000024810 r3: 0x0000000000000000 r4: 0x000000000006f380 r5: 0x0000000000000001 r6: 0x0000000000000000 r7: 0x0000000000000002 r8: 0x000000006b690073 r9: 0x000000000006f104 r10: 0x00000000bffff310 r11: 0x0000000000020b3c r12: 0x000000000006f399 r13: 0x00000000ffffffff r14: 0x0000000000000000 r15: 0x0000000000000000 r16: 0x000000000006f113 r17: 0x000000000006f228 r18: 0x0000000000000000 r19: 0x000000000006f0fc r20: 0x0000000000000014 r21: 0x000000000001b0c0 r22: 0x000000000000041a r23: 0x000000000001b0c0 r24: 0x00000000018006e8 r25: 0x000000000001bfe0 r26: 0x000000000006f133 r27: 0x000000000006f2a8 r28: 0x000000000006f380 r29: 0x0000000000000000 r30: 0x0000000024002422 r31: 0x0000000000004810
Binary Images Description:
0x1000 - 0x1ffff dovecot /opt/local/sbin/dovecot
0x8fe00000 - 0x8fe51fff dyld 44.4 /usr/lib/dyld
0x90000000 - 0x901bbfff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x90213000 - 0x90218fff libmathCommon.A.dylib
/usr/lib/system/libmathCommon.A.dylib
0x936d1000 - 0x936f2fff libmx.A.dylib /usr/lib/libmx.A.dylib
We're getting the following crash report, but I'm not sure it contains anything immediately useful (especially since we're running on a minority platform in OS X)... Anyone see where we might be able to resolve this? The crash doesn't kill existing imap processes, but dovecot/imap-login needs to be restarted.
Maybe this is related to my FreeBSD problem...
I have three imap-login processes running but none from around when I started dovecot. I have many stale imap processes (see the other thread).
As I don't know correct behaviour: should I normally have imap-login with start time of when I started dovecot?
My logs show multiple "dovecot: imap-login: Login" for same user (from same IP) -- over 130 times in less than one day. Is that normal?
On 11.8.2006, at 2.58, Dean Blackburn wrote:
We're getting the following crash report, but I'm not sure it
contains anything immediately useful (especially since we're
running on a minority platform in OS X)... Anyone see where we
might be able to resolve this? The crash doesn't kill existing imap
processes, but dovecot/imap-login needs to be restarted.
Do you have shutdown_clients=yes in dovecot.conf? If you do, the imap
processes should die if dovecot process dies.
Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000020
Thread 0 Crashed: 0 dovecot 0x0000482c log_set_prefix + 36 (log.c:190) 1 dovecot 0x000070b0 create_mail_process + 1576 (mail- process.c:535)
Is there anything in Dovecot's logs before this? Only way I can see
this happening is if it logs "pipe() failed" before crashing. If it
did, then maybe you should just increase the file descriptor limit.
I'll anyway fix this crash, assuming it's because of the pipe() problem.
participants (3)
-
Dean Blackburn
-
Jeremy C. Reed
-
Timo Sirainen