Syslogd is always crashing ... :-(

Question

Hi all,
for several days now I have a very high CPU usage on both G5 processors here on my PowerMac immediately after booting & logging in.
From the Activity Monitor I learned that the syslog deamon was the one who ate all the CPU time. This behaviour lasts for a couble of minutes and then syslogd is simply gone.
I checked the system.log file and saw that it crashed.
The Crashreport lookes like this:
Process: syslogd [387]
Path: /usr/sbin/syslogd
Identifier: syslogd
Version: ??? (???)
Code Type: PPC (Native)
Parent Process: launchd [1]
Date/Time: 2008-01-04 16:42:02.869 +0100
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000000
Crashed Thread: 1
Thread 0:
0 libSystem.B.dylib 0x93479064 select$DARWIN_EXTSN + 12
1 syslogd 0x000091c0 main + 3432
Thread 1 Crashed:
0 libSystem.B.dylib 0x93498194 aslresponse_free + 44
1 syslogd 0x00007b18 _asl_serverquery + 452
2 syslogd 0x00007b18 _asl_serverquery + 452
3 syslogd 0x0000f810 aslipc_serverroutine + 932
4 syslogd 0x0000f450 aslipcserver + 164
5 syslogd 0x000078f0 database_server + 408
6 libSystem.B.dylib 0x93456bf8 pthreadstart + 316
Thread 2:
0 libSystem.B.dylib 0x93414a38 semaphorewait_signaltrap + 8
1 libSystem.B.dylib 0x9341bc94 pthreadmutexlock + 648
2 syslogd 0x000070dc db_worker + 152
3 libSystem.B.dylib 0x93456bf8 pthreadstart + 316
Thread 3:
0 libSystem.B.dylib 0x934149d8 machmsgtrap + 8
1 libSystem.B.dylib 0x9341b8fc mach_msg + 56
2 libSystem.B.dylib 0x9356af74 vprocmig_logdrain + 92
3 libSystem.B.dylib 0x9356a394 vprocmgr_logdrain + 72
4 syslogd 0x0000608c launchd_drain + 64
5 libSystem.B.dylib 0x93456bf8 pthreadstart + 316
Thread 1 crashed with PPC Thread State 32:
srr0: 0x93498194 srr1: 0x0200d030 dar: 0x00000000 dsisr: 0x40000000
r0: 0xc0040577 r1: 0xf0080c60 r2: 0x00000000 r3: 0x00102a70
r4: 0x00000000 r5: 0x00000001 r6: 0x0000015d r7: 0x00000000
r8: 0x001fc080 r9: 0x00000000 r10: 0x00019000 r11: 0x00011340
r12: 0x93498168 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x0010169c
r20: 0x00017964 r21: 0x00000001 r22: 0x00000001 r23: 0x00101750
r24: 0x001016bc r25: 0x00000000 r26: 0xffffffff r27: 0xffffffff
r28: 0x00000025 r29: 0x00102a70 r30: 0x00000001 r31: 0x00007964
cr: 0x42000448 xer: 0x00000000 lr: 0x00007b1c ctr: 0x93498168
vrsave: 0x00000000
Binary Images:
0x1000 - 0x10fff +syslogd ??? (???) <60797682dec426b47a16ac92ef309e81> /usr/sbin/syslogd
0x8fe00000 - 0x8fe309d3 dyld 95.3 (???) <a7be977c203ec5c76b2f25a7aef66554> /usr/lib/dyld
0x90003000 - 0x9000effb libgcc_s.1.dylib ??? (???) <ea47fd375407f162c76d14d64ba246cd> /usr/lib/libgcc_s.1.dylib
0x93413000 - 0x935acfe3 libSystem.B.dylib ??? (???) <8a6cd873dfa7ada786efac188f95ed1b> /usr/lib/libSystem.B.dylib
0x943e8000 - 0x943edff6 libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0xffff8000 - 0xffff9703 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
Anybody any idea what's going on here?
Thanks,
Stefan.

Answer 1

thanks, but didn't help. the largest file was 61Meg.
meanwhile I observed that syslogd uses always very much CPU time, the fans are rotating fast and the process doesn't seem to terminate as long as I don't kill it.
it doesn't use much physical or virtual memory, though. around 16MB physical and 618MB virtual.
not unusual I guess?
unfortunately, I still get these kinds of messages in system.log:
Jan 6 20:32:50 Tigger com.apple.launchd[1] (com.apple.syslogd[28641]): Exited abnormally: Bus error
Jan 6 20:37:04 Tigger com.apple.launchd[1] (com.apple.syslogd[28685]): Exited abnormally: Segmentation fault
Jan 6 20:37:13 Tigger com.apple.launchd[1] (com.apple.syslogd[28878]): Exited abnormally: Segmentation fault
Jan 6 20:37:13 Tigger com.apple.launchd[1] (com.apple.syslogd): Throttling respawn: Will start in 1 seconds
:-(((