Jump to content

syslogd consuming 100% of CPU


zoomie
 Share

7 posts in this topic

Recommended Posts

Today, I noticed that syslogd is using up 100% of CPU. Has anyone else experienced this...or know of any possible solutions?

 

here's a snippet of my /var/log/system.log:

 

Nov 28 22:35:07: --- last message repeated 1 time ---
Nov 28 22:34:20 Leopard SystemUIServer[170]: MenuCracker: Loading 'iStatMenusCPU'.
Nov 28 22:34:27 Leopard SyncServer[190]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Nov 28 22:34:27 Leopard mount_gentoo_nas.app[183]: Error loading /Library/QuickTime/AviImporter-r7 (Intel).component/Contents/MacOS/AviImporter:  dlopen(/Library/QuickTime/AviImporter-r7 (Intel).component/Contents/MacOS/AviImporter, 262): no suitable image found.  Did find:\n	/Library/QuickTime/AviImporter-r7 (Intel).component/Contents/MacOS/AviImporter: mach-o, but wrong architecture
Nov 28 22:35:07: --- last message repeated 2 times ---
Nov 28 22:34:28 Leopard mount_gentoo_nas.app[183]: Error loading /Library/QuickTime/XviD_Codec-r58 (Intel).component/Contents/MacOS/XviD_Codec:  dlopen(/Library/QuickTime/XviD_Codec-r58 (Intel).component/Contents/MacOS/XviD_Codec, 262): no suitable image found.  Did find:\n	/Library/QuickTime/XviD_Codec-r58 (Intel).component/Contents/MacOS/XviD_Codec: mach-o, but wrong architecture
Nov 28 22:35:07: --- last message repeated 1 time ---
Nov 28 22:34:29 Leopard Yojimbo Helper[191]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Nov 28 22:34:31 Leopard NetAuthAgent[192]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Nov 28 22:34:31 Leopard osascript[196]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Nov 28 22:34:31 Leopard ATSServer[198]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Nov 28 22:34:31 Leopard backupd-helper[199]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Nov 28 22:34:32 Leopard check_afp[201]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Nov 28 22:35:05 Leopard Terminal[204]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Nov 28 22:35:07 Leopard ReportCrash[206]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
Nov 28 22:35:07 Leopard ReportCrash[206]: Formulating crash report for process syslogd[12]
Nov 28 22:35:07 Leopard ReportCrash[206]: Saved crashreport to /Library/Logs/CrashReporter/syslogd_2007-11-28-223507_Leopard.crash using uid: 0 gid: 0, euid: 0 egid: 0
Nov 28 22:35:07 Leopard login[205]: USER_PROCESS: 205 ttys000
Nov 28 22:35:09 Leopard iStat menus Background Checker[219]: _CFGetHostUUIDString: unable to determine UUID for host. Error: 35

 

The rest of the system.log is much more of the same. Any ideas?

Link to comment
Share on other sites

From netkas.org the following Q&A entry:

 

Q: Time machine doesn’t work/I have error 35, what can i do to fix it ?

A: get fixed (compiled from sources, so legal) IONetworking by zef , http://tinyurl.com/27frv7, unpack it and install file:

 

sudo cp /path/to/unpacked/IONetworkingFamily /System/Library/Extensions/IONetworkingFamily.kext/Contents/MacOS/IONetworkingFamily

sudo chown 0:0 /System/Library/Extensions/IONetworkingFamily.kext/Contents/MacOS/IONetworkingFamily

sudo rm /System/Library/Extensions.mkext

 

MacOSX will recreate kexts cache, then reboot, Time machine should work now and no more Error 35

 

Good luck. This should resolve the error35 messages that keep filling up your syslog.

Link to comment
Share on other sites

From netkas.org the following Q&A entry:

Good luck. This should resolve the error35 messages that keep filling up your syslog.

 

 

Thanks for the reply. That patch certainly fixed the error 35's that populated my syslog. However, syslogd is still using up a lot of CPU time. The system.log shows several instances of errors loading quicktime avi importer, so I think I'll investigate that a bit further.

Link to comment
Share on other sites

After further investigation, CrashReporter has several instances of syslogd crashes. The syslogd crashes began yesterday, when I noticed that syslogd has been using up a lot of CPU time.

 

Here's the latest crash log:

syslogd_2007-11-29-094717_Leopard.crash

Process:		 syslogd [13]
Path:			/usr/sbin/syslogd
Identifier:	  syslogd
Version:		 ??? (???)
Code Type:	   X86 (Native)
Parent Process:  launchd [1]

Date/Time:	   2007-11-29 09:47:17.103 -0800
OS Version:	  Mac OS X 10.5.1 (9B18)
Report Version:  6

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread:  1

Thread 0:
0   libSystem.B.dylib			 	0x947042ee read$NOCANCEL$UNIX2003 + 10
1   libSystem.B.dylib			 	0x9473baa9 __srefill + 295
2   libSystem.B.dylib			 	0x94740b3d fread + 159
3   syslogd					   	0x0000e018 asl_store_archive + 368
4   syslogd					   	0x00006ad8 db_archive + 343
5   syslogd					   	0x000075fc klog_in_close + 720
6   syslogd					   	0x0000888e main + 4210
7   syslogd					   	0x00001982 start + 54

Thread 1 Crashed:
0   libSystem.B.dylib			 	0x9477293c aslresponse_free + 22
1   syslogd					   	0x00007018 __asl_server_query + 443
2   syslogd					   	0x0000ef90 asl_ipc_server_routine + 344
3   syslogd					   	0x0000ee2d asl_ipc_server + 113
4   syslogd					   	0x00006df0 database_server + 415
5   libSystem.B.dylib			 	0x94734075 _pthread_start + 321
6   libSystem.B.dylib			 	0x94733f32 thread_start + 34

Thread 2:
0   libSystem.B.dylib			 	0x9470392e semaphore_wait_signal_trap + 10
1   libSystem.B.dylib			 	0x9470b405 pthread_mutex_lock + 569
2   syslogd					   	0x000065e5 db_worker + 162
3   libSystem.B.dylib			 	0x94734075 _pthread_start + 321
4   libSystem.B.dylib			 	0x94733f32 thread_start + 34

Thread 3:
0   libSystem.B.dylib			 	0x947038e6 mach_msg_trap + 10
1   libSystem.B.dylib			 	0x9470b0dc mach_msg + 72
2   libSystem.B.dylib			 	0x948263e4 vproc_mig_log_drain + 97
3   libSystem.B.dylib			 	0x94825996 _vprocmgr_log_drain + 75
4   syslogd					   	0x00005617 launchd_drain + 73
5   libSystem.B.dylib			 	0x94734075 _pthread_start + 321
6   libSystem.B.dylib			 	0x94733f32 thread_start + 34

Thread 1 crashed with X86 Thread State (32-bit):
 eax: 0x00000000  ebx: 0x00006e6e  ecx: 0x00000001  edx: 0x00019000
 edi: 0x001018f0  esi: 0x00000000  ebp: 0xb0080e18  esp: 0xb0080e00
  ss: 0x0000001f  efl: 0x00010213  eip: 0x9477293c   cs: 0x00000017
  ds: 0x0000001f   es: 0x0000001f   fs: 0x0000001f   gs: 0x00000037
 cr2: 0x00000000

Binary Images:
0x1000 -	 0xfff7 +syslogd ??? (???) <afff45dbd9c0004baeb0c5e4e8437592> /usr/sbin/syslogd
0x8fe00000 - 0x8fe2d883  dyld 95.3 (???) <81592e798780564b5d46b988f7ee1a6a> /usr/lib/dyld
0x90003000 - 0x9000afe9  libgcc_s.1.dylib ??? (???) <f53c808e87d1184c0f9df63aef53ce0b> /usr/lib/libgcc_s.1.dylib
0x934ab000 - 0x934acfef  libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x94703000 - 0x9485dfe3  libSystem.B.dylib ??? (???) <8ecc83dc0399be3946f7a46e88cf4bbb> /usr/lib/libSystem.B.dylib
0xffff0000 - 0xffff1780  libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib

 

All the other syslogd crash logs are basically the same. Does anyone have an idea?

Link to comment
Share on other sites

  • 2 months later...

This is a general OS issue, not just an OSx86 (hackintosh) issue. here is your fix:

 

sudo nano /System/Library/LaunchDaemons/com.apple.syslogd.plist

 

after line #23 add two additional strings (these make sure that the syslogd logger only write emergency errors to the system log.

 

#23                <string>/usr/sbin/syslogd</string>
#24                <string>-c</string>
#25                <string>0</string>

 

Optionally you can also cap the log file to a certain file size using:

 

#23                <string>/usr/sbin/syslogd</string>
#24                <string>-c</string>
#25                <string>0</string>
#26                <string>-db_max 2500000</string>

 

This should help with the problem greatly, the issue here is that syslog is set to warn you/your admin of every little issue, which is great for debugging but bad when you're running poorly written/configured/incompatible applications. i'm sure that the many hackintosh users (myself included) run into this issue a bit more then regular mac users because of a lack of driver/software support.

 

anyhow, once you've done this just reboot and you should be all better.

 

Thanks to everyone who works hard to get our hackintoshes in tip top shape so that we too may enjoy a quality enthralling and beautiful OS :)

Link to comment
Share on other sites

 Share

×
×
  • Create New...