AFP548 Changing the world one server at a time.

timsieved crashing.

Home › Forums › OS X Server and Client Discussion › Mail › timsieved crashing.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #370268
    tiredofnick
    Participant

    Hi all, I’m trying to setup out of office replies for our mail server and I’m having some trouble with timsieved crashing constantly.

    here’s the log from console:

    Oct 22 17:42:30 server crashdump[22836]: timsieved crashed
    Oct 22 17:42:30 server crashdump[22836]: crash report written to: /Library/Logs/CrashReporter/timsieved.crash.log
    Oct 22 17:42:31 server master[18770]: process 22837 exited, signaled to death by 10
    Oct 22 17:42:31 server sieve[22839]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
    Oct 22 17:42:31 server master[18770]: process 22839 exited, signaled to death by 10
    Oct 22 17:42:31 server sieve[22841]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery

    and heres the crash log from timsieved:

    Host Name:      server
    Date/Time:      2007-10-23 10:32:17.370 -0400
    OS Version:     10.4.10 (Build 8R218)
    Report Version: 4
    
    Command: timsieved
    Path:    /usr/bin/cyrus/bin/timsieved
    Parent:  master [12969]
    
    Version: ??? (???)
    
    PID:    13150
    Thread: 0
    
    Exception:  EXC_BAD_ACCESS (0x0001)
    Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x0000000c
    
    Thread 0 Crashed:
    0   timsieved 	0x00022018 prot_printf + 24 (prot.c:656)
    1   timsieved 	0x00004f64 fatal + 88 (timsieved.c:175)
    2   timsieved 	0x000173d0 mboxlist_init + 136 (mboxlist.c:2320)
    3   timsieved 	0x00004f88 service_init + 20 (timsieved.c:191)
    4   timsieved 	0x00002d3c main + 1096 (service.c:385)
    5   timsieved 	0x000021e0 _start + 392 (crt.c:267)
    6   timsieved 	0x00002054 start + 48
    
    Thread 0 crashed with PPC Thread State 64:
      srr0: 0x0000000000022018 srr1: 0x100000000000f030                        vrsave: 0x0000000000000000
        cr: 0x24000032          xer: 0x0000000020000000   lr: 0x0000000000022010  ctr: 0x0000000090020594
        r0: 0x0000000000004f64   r1: 0x00000000bffff0e0   r2: 0x000000000003b5b0   r3: 0x0000000000000000
        r4: 0x0000000000031a74   r5: 0x0000000000034050   r6: 0x0000000000000000   r7: 0x0000000000000000
        r8: 0x0000000000000000   r9: 0x000000000000004b  r10: 0x0000000000000005  r11: 0x00000000a0006914
       r12: 0x0000000090020594  r13: 0x0000000000000000  r14: 0x0000000000000000  r15: 0x0000000000000000
       r16: 0x00000000bffffeec  r17: 0x000000000000003c  r18: 0x00000000000000fa  r19: 0x0000000000042900
       r20: 0x0000000000000000  r21: 0x0000000000000000  r22: 0x00000000a0011b08  r23: 0x0000000000042900
       r24: 0x00000000003001e0  r25: 0x0000000000000001  r26: 0x0000000000300210  r27: 0x0000000000000001
       r28: 0x00000000bffffee4  r29: 0x000000000004d660  r30: 0x000000000003a310  r31: 0x0000000000022010
    
    Binary Images Description:
        0x1000 -    0x39fff timsieved 	/usr/bin/cyrus/bin/timsieved
      0x205000 -   0x216fff libsasl2.2.dylib 	/usr/local/lib/libsasl2.2.dylib
      0x24b000 -   0x2e4fff libdb-4.1.dylib 	/usr/local/BerkeleyDB.4.1/lib/libdb-4.1.dylib
    0x8fe00000 - 0x8fe52fff dyld 46.12	/usr/lib/dyld
    0x90000000 - 0x901bcfff libSystem.B.dylib 	/usr/lib/libSystem.B.dylib
    0x90214000 - 0x90219fff libmathCommon.A.dylib 	/usr/lib/system/libmathCommon.A.dylib
    0x91a15000 - 0x91adcfff libcrypto.0.9.7.dylib 	/usr/lib/libcrypto.0.9.7.dylib
    0x9503c000 - 0x9506bfff libssl.0.9.7.dylib 	/usr/lib/libssl.0.9.7.dylib
    0x9507b000 - 0x95098fff libresolv.9.dylib 	/usr/lib/libresolv.9.dylib

    as you can see i’m running 10.4.10, with all the latest updates. does anyone have any idea why its crashing like this and/or what I can do to fix it?

    Also, I’m having no trouble receiving or sending mail while its crashing….

    #370271
    tiredofnick
    Participant

    Fixed it.

    not sure how, but it works now.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.