Table 3-3 Solaris Error Messages And Their Meanings - Sun Microsystems Blade 1500 Service, Diagnostics, And Troubleshooting Manual

OpenBoot PROM Messages and Their Meaning (Continued)
TABLE 3-2
Message
WARNING: Timed out waiting for
NIS to come up
3.2.2.2 Solaris Error Messages
TABLE 3-3
while the Solaris operating system is functioning, their meanings, and what to do
next. These messages are high-level and might be related to software, rather than
hardware failure.
Solaris Error Messages and Their Meanings
TABLE 3-3
Message
Arguments too long
automountd[int]:
server hostname
responding
Bad address
Bad file number
BAD TRAP
Broken pipe
Bus error
Command not found
Connection closed
(by foreign host)
3-8 Sun Blade 1500 Service, Diagnostics, and Troubleshooting Manual • December 2004
Meaning
The name service cannot be
found.
lists some common error messages or portions of error messages displayed
Meaning
Too many arguments follow a C shell
command.
An NFS server cannot be mounted.
The value of an address is invalid.
A program error where the application does
not have permission to interact with the file.
Faulty hardware or mismatch of hardware and
its configuration. Can sometimes indicate a
bad or earlier version CPU. Usually precedes a
panic.
Occurs when a pipe ( |
I/O was attempted on a nonexistent device.
Might be caused by invalid file descriptors,
bad memory allocation, or corrupt boot blocks.
The C shell could not find the command you
typed.
Timeout has occurred or network connection
failed from remote host using either
or telnet .
) directs without data.
rlogin
What to Do
Check network connection.
See "Network Problem" on
page 4-17. Check system name
service configuration
information.
What to do
Run the command in the
Bourne shell.
Check the NFS server's status
and network connection.
Determine and use the correct
address.
Program bug, or change
permissions of the file.
Check configuration. Check
hardware functionality.
Check the structure of the
command.
Check for device and its
connection.
Check the command path.
Type the command explicitly.
Try again. Check network
connection.