![]() ![]() 09:56:15 CET Automatic reboot timer disabled. 09:45:13 CET Automatic reboot timer enabled. 09:45:13 CET Started child "/usr/sbin/krb5kdc" as pid 342. 09:45:13 CET Started child "/usr/sbin/kadmind" as pid 341. 09:45:13 CET Started child "/usr/sbin/hwmond" as pid 340. 09:45:13 CET Started child "/usr/libexec/postfix/master" as pid 339. 09:45:13 CET Started child "/usr/sbin/PrintServiceMonitor" as pid 338. 09:45:13 CET Started child "/usr/sbin/PasswordService" as pid 337. Jan 3 10:54:29 localhost kernel: ApplePMU::PMU FORCED SHUTDOWN, CAUSE = -93Ĭhecked the '' in '/Library/Logs': Jan 3 09:43:42 localhost kernel: ApplePMU::PMU FORCED SHUTDOWN, CAUSE = -93 isn't exactly helping with the search for the cause of this problem.ĭoesn't seem to be any real pattern to it, and it is becoming quite annoying, really. The fact that every app has its own logfiles, crash logs per user etc. Jan 2 13:41:47 localhost kernel: ApplePMU::PMU FORCED SHUTDOWN, CAUSE = -93 We run OD, SMB, AFP, Filemaker Server, CommuniGate Pro plus print and DNS services on a lightly loaded single CPU Xserve running Panther (10.3.9).ĭec 1 15:37:27 localhost kernel: ApplePMU::PMU FORCED SHUTDOWN, CAUSE = -93ĭec 12 01:39:32 localhost kernel: ApplePMU::PMU FORCED SHUTDOWN, CAUSE = -93ĭec 14 09:33:41 localhost kernel: ApplePMU::PMU FORCED SHUTDOWN, CAUSE = -93ĭec 19 13:48:03 localhost kernel: ApplePMU::PMU FORCED SHUTDOWN, CAUSE = -93 We solved the latter, but still haven't found which process locks up the box and causes the watchdog timer to expire. So far, I've found that that '-93' relates to a process locking up or whatever, and '-122' relates to power issues, such as if your UPS is going bonkers. I've been having the same problem over and over again. ![]()
0 Comments
Leave a Reply. |