Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Mac OS X > Diagnose ???.crash.log

Diagnose ???.crash.log
Thread Tools
Fresh-Faced Recruit
Join Date: Feb 2000
Status: Offline
Reply With Quote
Mar 21, 2005, 06:42 PM
 
I had an Xserve crash tonight. It just froze up. When I restarted, I found the following in the /Library/Logs/CrashReporter/???.crash.log:

Date/Time: 2005-03-21 18:10:40 -0600
OS Version: 10.2.8 (Build 6R73)
Host: www.grayloon.com

Command: Unknown
PID: Unknown

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
(null)
PPC Thread State:
srr0: 0x000103c0 srr1: 0x0000f030 vrsave: 0x00000000
xer: 0x20000000 lr: 0x000103b8 ctr: 0x9005e1f8 mq: 0x00000000
r0: 0x000103b8 r1: 0xf0305ad0 r2: 0x6f6e3a20 r3: 0x00000000
r4: 0x00000000 r5: 0x00000007 r6: 0x303a3336 r7: 0x00000000
r8: 0x000a0010 r9: 0xa0001048 r10: 0x000a0290 r11: 0xa00044b0
r12: 0x9005e1f8 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x00000000 r26: 0x00000000 r27: 0x00000000
r28: 0x00000000 r29: 0x00000000 r30: 0x00000000 r31: 0xffffc909

The Xserve G4/dual 1.33Ghz with 2GB RAM is a colocated webserver (Apache 2.0.29) running PHP (4.3.10) and MySQL (4.0.18) with some limited FTP access (ProFTPD 1.2.9). During the crash, I was unable to access it via SSH. Anyone know how to diagnose this or provide insight?
     
Clinically Insane
Join Date: Oct 2000
Location: Los Angeles
Status: Offline
Reply With Quote
Mar 21, 2005, 08:19 PM
 
That log looks really small. If that's a kernel panic log there's not enough information there to determine anything from a cursory examination. Sometimes the kernel panic will give you conclusive clues as to its cause, while other times it will not.

"The natural progress of things is for liberty to yield and government to gain ground." TJ
     
Dedicated MacNNer
Join Date: Dec 2001
Location: Promised Land
Status: Offline
Reply With Quote
Mar 22, 2005, 12:01 AM
 
That's not a kernel panic, so if the machine did actually lock up, then that's the wrong thing to look at. The panic log file is located in /Library/Logs/panic.log.

The OP's log is a normal process crash log. And in this case it's for a zombie process. Zombies are processes that have been destroyed, but still have an entry in the kernel process table while waiting for their parent process to reap them (to obtain exit state). This is why the Command and PID are unknown and the only execution state is a register dump (where you would normally have a stack backtrace for each thread, a list of shared libs and the register dump).
G5 2.5 DP/2GB RAM/NVidia 6800 Ultra
PowerBook Al 1Ghz/768MB RAM
6gb Blue iPod Mini
     
Clinically Insane
Join Date: Oct 2000
Location: Los Angeles
Status: Offline
Reply With Quote
Mar 22, 2005, 01:54 PM
 
You're right, someone_else, good call. I was up really late last night, although that's not much of an excuse. If we were looking at a panic log it would say panic(cpu <N>).

"The natural progress of things is for liberty to yield and government to gain ground." TJ
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 04:56 AM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2