Step 6: Display Error Messages in the System Log File

Action

To view Routing Engine error messages in the system log file, use the following CLI command:

user@host> show log messages

Sample Output

For compact flash drive errors:

user@host> show log messages

Feb  3 07:58:17 host /kernel: ad0: HARD WRITE ERROR blk# 135783 status=51 
error=10 Feb  3 07:58:17 host /kernel: ad0: HARD WRITE ERROR blk# 137633 
status=51 error=10 Feb  3 07:58:47 host /kernel: ad0: HARD WRITE ERROR blk# 
135731 status=51 error=10 Feb  3 07:58:47 host /kernel: ad0: HARD WRITE ERROR 
blk# 135783 status=51 error=10 Feb  3 07:58:47 host /kernel: ad0: HARD WRITE 
ERROR blk# 137633 status=51 error=10 

For hard drive errors:

user@host> show log messages

Jun  3 12:00:28 router /kernel: ad1: WRITE command timeout - resetting

Jun  3 12:00:44 router /kernel: ata0: resetting devices ..

Jun  3 12:00:44 router /kernel: ata0:  Succeeded in resetting devices.

Jun  3 12:00:28 router /kernel: ad1: WRITE command timeout - resetting

Jun  3 12:00:17 router /kernel: ata0: resetting devices ..

What It Means

The messages system log file records the time the failure or event occurred, the severity level, a code, and a message description. Use the show log messages CLI command to browse error messages that are generated at least 5 minutes before and after an event. You can also use the show log messages | match "device-name" command to view error messages that are specific to a device name. Use this information to diagnose a problem and to let JTAC know what error messages were generated and the router events prior to the event. For more information about system log messages, see the JUNOS Software System Log Messages Reference.