GE Healthcare Brivo XR118 - Page 179

GE HEALTHCARE
DIRECTION 5461425-8EN, REVISION 6 BRIVO XR118 SERVICE MANUAL
Chapter 8 - - Troubleshooting Page 179
Step 1: You need to find out when exactly system crash has happened and who crashed.
a.) Open /magichome/xruser/log/sysError.log
b.) Go to the end of log file. [if you are using vi editor, press shift + g]
c.) Look for the last error to find which actor crashed
Sample:
5000051 480,2008-03-23,05:01:17:804,"VEN",5000051, AFRF has detected fault in the
system,2222,DO,DEFAULT, SysCntrl, SysCntrl, Software_Problem,2,1,1, Component
XRImDet has been classified as Severity 2. Restarting the component with notification to Fault
Notification Consumers.,./subsysmgr/subsysmgr/FaultRecovery.cpp,433
This indicates that XRImDet actor has crashed.
Step 2: Find the corresponding core file generated for the crashed actor.
cd /magichome/xruser/bin/
su root [passwd is #superxr]
ls –lrt core.*
file core.xxxx
Step 3: take and send snapshot and this core file to IB.
4.) How to use system error logs (sysError.log) ?
For any issues, first place to look is /magichome/xruser/log/sysError.log.
This can give right pointers to following issues.
- Boot failures
- Appsetup failures
- Exposure failures.
- Any other system failures such as crash, etc.
Sample 1:
This also find out partial failures in the system. Eg:
624,2008-03-27,02:09:27:352,"VEN",3600105, Config Cache error,2222,DO,DEFAULT,
SysCntrl, control, Check config cache value,1,1,1, Could not get VASite value. Assuming
NO,XRTechMgr.cpp,757
The above error indicates the error in accessing a config value by techmgr actor.
Note that 36 (starting number of error code) is the actor id of the techmgr actor.
Sample 2:
593,2008-03-26,07:28:19:299,"VEN",1600140, Aborting Image Processing for the specified
frame,2222,DO,DEFAULT, XRImProc, Constructor, 1. Retry the operation 2. Reset the
operation and try again. 3. Call service if problem persists.,1,0,1, Aborting Sequence:
1,XRImProc.cpp,4002
Here 16(starting number of the error code) is actor Id of the ImProc. This indicates ImProc is
responsible for this error.