10.5: One fix for a runaway syslogd process

Search

From our Sponsor...

User Functions

Don't have an account yet? Sign up as a New User
Lost your password?

What's New:

Hints

No new hints

Comments last 2 days

Links last 2 weeks

No recent new links

What's New in the Forums?

The Editor's Corner...

Here are some of my (robg) other projects...

•	The Robservatory My blog - Macs, tech, etc.
•	Mac OS X Power Hound The best of Hints in print
•	Inside iWork An iWork training DVD
•	Macworld Column, features, online...

Hints by Topic

News from Macworld

The macosxhints Poll

What version of OS X are you running as your main OS?

Other polls | 11,370 votes | 42 comments

10.5: One fix for a runaway syslogd process | 25 comments | Create New Account

Click here to return to the '10.5: One fix for a runaway syslogd process' hint

The following comments are owned by whomever posted them. This site is not responsible for what they say.

10.5: One fix for a runaway syslogd process
Authored by: Fillman on Thu, Feb 14 2008 at 6:36PM PST

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.

com.apple.syslogd[1248]: syslogd(1248,0xa0750fa0) malloc: *** mmap(size=3095314432) failed (error code=12)
com.apple.syslogd[1248]: *** error: can't allocate region
com.apple.syslogd[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.....