Troubleshooting A Process Crash On Line Cards - Cisco CRS-1 - Carrier Routing System Router Troubleshooting Manual

Troubleshooting High CPU Utilization and Process Timeouts
Current process = "pkg/bin/syslog_dev", PID = 24615 TID = 1
trace_back: #0 0xfc1f6130 [strncat]
trace_back: #1 0x482002a4 [<N/A>]
trace_back: #2 0x48200504 [<N/A>]
trace_back: #3 0xfc1e4408 [_resmgr_io_handler]
trace_back: #4 0xfc1e40b0 [_resmgr_handler]
trace_back: #5 0xfc15aa28 [_eventmgr_resmgr_handler]
trace_back: #6 0xfc159e04 [_event_message_handler]
trace_back: #7 0xfc159d54 [_event_message_handler]
trace_back: #8 0xfc1575a4 [event_dispatch]
trace_back: #9 0x482007bc [<N/A>]
ENDOFSTACKTRACE

Troubleshooting a Process Crash on Line Cards

To troubleshoot a process crash on the line card, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Command or Action
Step 1
show install active node-id
Example:
RP/0/RP0/CPU0:router# show install active
location 0/0/CPU0
Node 0/0/CPU0 [RP] [SDR: Owner]
Boot Device: mem:
Boot Image:
/c12k-os-mbi-3.7.0.26I/mbiprp-rp.vm
Active Packages:
mem:c12k-mpls-3.7.0.26I
mem:c12k-mini-3.7.0.26I
Step 2
show version
Example:
RP/0/RP0/CPU0:router# show version | begin
0/0/CPU0
Cisco IOS XR Troubleshooting Guide for the Cisco CRS-1 Router
8-192
Identify the process that crashed (PI or PD) from the crash log. In either case, the stack traces
obtained from the crash needs to be decoded to identify the location in the code where the process
crashed.
show install active
show version
show log
show exception
Chapter 8
Purpose
Use the show install active command to collect information
about the list of installed software for each node.
Gives the workspace (directory) and the build server where
image was built.
Process Monitoring and Troubleshooting
OL-21483-02