EasyManua.ls Logo

Sun Microsystems Blade 1500 - Page 63

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

Table of Contents

Related product manuals