Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the '10.5: One fix for a runaway syslogd process' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: One fix for a runaway syslogd process
Authored by: Fillman on Feb 14, '08 06:36:23PM

I can also confirm that zapping the file asl.db fixed the problem. My file was about 2 months old and had grown to around 250Mb. The system log file was full of three line messages varying from seconds to a minute apart telling me that syslogd had a memory error.[1248]: syslogd(1248,0xa0750fa0) malloc: *** mmap(size=3095314432) failed (error code=12)[1248]: *** error: can't allocate region[1248]: *** set a breakpoint in malloc_error_break to debug

One CPU has spent the last three months maxed out at 100%. I fixed this three days ago after 10.5.2 didn't fix it and I found this thread and syslogd has not complained since.

I also notice that the asl.db clears itself frequently now. The current file is less than 24 hours old so some daily task is doing its required cleanup job.

Happy again.....

[ Reply to This | # ]