Sun Microsystems Blade 1500 Service, Diagnostics, And Troubleshooting Manual page 63

Solaris Error Messages and Their Meanings (Continued)
TABLE 3-3
Message
Connection refused
Connection reset by
peer
Device busy
Error Host Unknown
Exec format error
File descriptor in
bad state
File exists
File name too long
giving up
Illegal Instruction
Illegal seek
INIT: Cannot create
/var/adm/utmpx
Invalid argument
Meaning
Remote host actively refused connection or
network security policy was violated.
Connection timed out.
Device is already mounted or there was an
attempt to unmount a device while a file was
in use. Typically seen when ejecting an optical
media disc.
Name services have not been set up correctly
or an alias is missing from NS maps.
Software is not compatible with platform. File
is not an executable, though identified as such.
Permissions on file prevent reading.
An attempt to overwrite a file occurred.
A file name was greater than 256 characters, or
a path name was over 1024 characters.
An action has been retried until it has timed
out. Can occur when syncing SCSI hard drive
file systems.
Application for a different platform was run,
there is too little swap space available, or a
data file was run as an executable.
Misuse of the pipe ( ).
|
The root file system has been mounted as read
only, or has become corrupted.
An invalid parameter was specified that the
system cannot interpret.
What to do
Try issuing
xhost +
local host.
Try again.
Close all files and quit all
applications from that mount
point. If it is an optical media
disc, stop the volume
manager.
Reconfigure name services or
update NS maps.
Check that the Binary
Compatibility Package is
installed. Check that the file is
truly executable.
Check and reset file
permissions.
Rename or remove the
existing file.
If more characters are
required, edit the
/usr/include/limits.
h file.
Check cabling to suspect
hardware. Check hardware
driver.
Verify the compatibility of the
software. Check swap space.
Set correct permissions for the
file.
Direct the output to a file, then
use the file as input.
Run fsck on the root file
system. If unsuccessful,
replace the root file system.
Check that the actions you are
taking make logical sense. For
example, don't mount a
nonexistent file system.
Chapter 3 Basic Troubleshooting
on the
3-9