NEC Express5800/320Fc Manual Page 150

  • Download
  • Add to my manuals
  • Print
  • Page
    / 156
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 149
System Log Messages
9-6 Express5800/ftServer: System Administrators Guide for the Linux Operating System
CAUTIONCAUTION
!
Boot monitoring is one of the fault-tolerant features of your
ftServer system. You must reenable it for full fault
tolerance.
System Log Messages
System log messages contain information on the operation state of the system. The file
/var/log/messages contains system log messages. You can find logs that are
specific to ftServer systems in the directory /var/opt/ft/log.
See ‘OpState:State Definitions’’ on page 8-158 and ‘‘OpState:Reason Definitions’’ on
page 8-159 for explanations of some of the terminology you may see in these
messages.
Error and Log Messages Regarding Keyboard and Mouse
In the system log or at system boot, you may see stderr messages such as those
shown in
Example 9-1. These and similar messages may occur multiple times. They
are not a cause for concern if the system boots without undue delay, and when the
operating system presents you with the logon prompt, it is appropriately presented on
your display device and your input devices are supported to interact with the system.
The messages are an unavoidable result of the order in which drivers need to be
loaded during the Linux operating system distribution boot process.
Example 9-1. Possible Keyboard and Mouse Error Messages at Boot Time
Mar 15 07:15:00 ftlx rc.sysinit: Initializing USB keyboard: failed
Mar 15 07:15:00 ftlx modprobe: modprobe: Can’t locate module mousedev
Mar 15 07:15:00 ftlx rc.sysinit: Initializing USB mouse: failed
Mar 15 07:15:07 ftlx ifup: SIOCSIFADDR: No such device
Mar 15 07:15:51 ftlx kernel: Keyboard timed out[1]
kernel: keyboard timed out[1]
Mar 15 07:15:52 ftlx kernel: keyboard: Timeout - AT keyboard not present? (f4)
Page view 149

Comments to this Manuals

No comments