원문 : http://www.ischo.net -- 조인상 //시스템 엔지니어

+++++++++++++++++++++++++++++++++++++++++++++++++++++++

Solaris Common Error Messages (alphabetized)


1. A command window has exited because its child exited.
2. admintool: Received communication service error 4
3. answerbook: XView error: NULL pointer passed to xv_set
4. Arg list too long
5. Argument out of domain
6. Arguments too long
7. assertion failed: variable, file variable, line N
8. automountd[N]: No network locking on variable: contact admin to install server change
9. automountd[N]: server variable not responding
10.automount[N]: variable: Not a directory

11. Bad address
12. BAD/DUP FILE I=i OWNER=o MODE=m SIZE=s MTIME=t
13. Bad file number
14. N BAD I=N
15. bad module/chip at: variable
16. BAD SUPER BLOCK: variable
17. BAD TRAP
18. bad trap = N
19. /bin/sh: variable: too big
20. Block device required
21. Boot device: /iommu/sbus/variable/variable/sd@3,0
22. Broadcast Message from root (pts/N) on server [date]
23. Broken pipe
24. Bus Error

25. Cannot allocate colormap entry for "variable"
26. Can't create public message device (Device busy)
27. Can't invoke /etc/init, error N
28. can't synchronize with hayes
29. cd: Too many arguments
30. Channel number out of range
31. chmod: ERROR: invalid mode
32. Command not found
33. Connection closed.
34. Connection closed by foreign host.
35. [Connection closed.Exiting]
36. Connection refused
37. Connection timed out
38. console login: ^J^M^Q^K^K^P
39. core dumped
40. Could not initialize tooltalk (tt_open): TT_ERR_NOMP
41. Could not start new viewer
42. cpio: Bad magic number/header.
43. Cross-device link

44. data access exception
45. Data fault
46. Deadlock situation detected/avoided
47. Device busy
48. /dev/rdsk/variable: CAN'T CHECK FILE SYSTEM.
49. /dev/rdsk/variable: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
50. Directory not empty
51. Disc quota exceeded
52. dumptm: Cannot open `/dev/rmt/variable': Device busy
53. DUP/BAD I=i OWNER=o MODE=m SIZE=s MTIME=t FILE=f  REMOVE?
54. N DUP I=N

55. error: DPS has not initialized or server connection failed
56. ERROR: missing file arg (cm3)
57. ERROR [SCCS/s.variable]: writable `variable' exists (ge4)
58. esp0: data transfer overrun
59. Event not found
60. EXCESSIVE BAD BLKSI=N  CONTINUE?
61. EXCESSIVE DUP BLKS I=N  CONTINUE?
62. Exec format error

63. fd0: unformatted diskette or no diskette in the drive
64. File exists
65. File locking deadlock
66. filemgr: mknod: Permission denied
67. File name too long
68. FILE SYSTEM STATE IN SUPERBLOCK IS WRONG; FIX?
69. File table overflow
70. File too large
71. FREE BLK COUNT(S) WRONG IN SUPERBLK  SALVAGE?
72. fsck: Can't open /dev/dsk/variable
73. fsck: Can't stat /dev/dsk/variable

74. giving up
75. Graphics Adapterdevice /dev/fb is of unknown type
76. group.org_dir: NIS+ servers unreachable

77. /home/variable: No such file ordirectory
78. Host is down
79. host name configuration error
80. hosts.org_dir: NIS+ servers unreachable

81. I can't read your attachments. What mailer are you using?
82. ie0: Ethernet jammed
83. ie0: no carrier
84. Illegal Instruction
85. Illegal instruction "0xN" was encountered at PC 0xN
86. Illegal seek
87. Image Tool: Unable to open XIL Library.
88. Inappropriate ioctl for device
89. INCORRECT BLOCK COUNT I=N (should be N)  CORRECT?
90. inetd[N]: execv /usr/sbin/in.uucpd: No such file or directory
91. inetd[N]: variable/tcp: unknown service
92. inetd[N]: variable/udp:unknown service
93. inetd: Too many open files
94. INIT: Cannot create /var/adm/utmp or /var/adm/utmpx
95. InitOutput: Error loading module for /dev/fb
96. Interrupted system call
97. Invalid argument
98. Invalid null command
99. I/O error
100. Is a directory

101. kernel read error
102. Killed
103. kmem_free block already free

104. last message repeated N times
105. ld.so.1: variable: fatal: relocation error: symbol not found: variable
106. ld.so.1: variable: fatal: variable: can't open file: errno=2
107. le0: Memory error!
108. le0: No carrier-- cable disconnected or hub link test disabled?
109. le0: No carrier-- transceiver cable problem?
110. LINK COUNT FILE I=i OWNER=o MODE=m SIZE=s MTIME=t COUNT...  ADJUST?
111. LL105W: Protocol error detected.
112. ln: cannot create /dev/fb: Read-only file system
113. lockd[N]: create_client: no name forinet address 0xN
114. Login incorrect
115. lp hang

116. mailtool: Can't create dead letter: Permission denied
117. mailtool: Could not initialize the Classing Engine
118. Mail Tool is confused about the state of your Mail File.
119. mail: Your mailfile was found to be corrupted (Content-length mismatch).
120. Memory address alignment
121. memory leaks
122. mount: /dev/dsk/variable is already mounted, /variable is busy, or...
123. mount: giving up on: /variable
124. mount: mount-point /variable does not exist.
125. mount: the state of /dev/dsk/variable is not okay

126. /net/variable: No such file or directory
127. Network is down
128. Network is unreachable
129. NFS getattr failed for server variable: RPC: Timed out
130. nfs mount: Couldn't bind to reserved port
131. nfs mount: mount: variable: Device busy
132. NFS mount: /variable mounted OK
133. NFS read failed for server variable
134. nfs_server: bad getargs for N/N
135. NFS server variable not responding still trying
136. NFS server variable ok
137. nfs umount:variable: is busy
138. NFS write error on host variable: No space left on device.
139. NFS write failed for server variable: RPC: Timed out
140. NIS+ authentication failure
141. No buffer space available
142. No child processes
143. No default media available
144. No directory! Logging in with home=/
145. No message of desired type
146. No recipients specified
147. No record locks available
148. No route to host
149. No shell  Connection closed
150. No space left on device
151. No such device
152. No such device or address
153. No such file or directory
154. no such map in server's domain
155. No such process
156. No such user as variable-- cron entries not created
157. Not a directory
158. Not enough space
159. not found
160. NOTICE: /variable: out of inodes
161. Not login shell
162. Not on system console
163. Not owner
164. Not supported

165. operation failed [error 185], unknown group error 0, variable
166. Operation not applicable
167. out of memory

168. PARTIALLY ALLOCATED INODE I=N  CLEAR?
169. passwd.org_dir: NIS+ servers unreachable
170. Password does not decrypt secret key for unix.uid@variable
171. Permission denied
172. Please specify a recipient.
173. Protocol not supported
174. Protocol wrong type for socket

175. Read error from network: Connection reset by peer
176. Read-only file system
177. rebooting...
178. Recipient names must be specified
179. Reset tty pgrp from N to N
180. Resource temporarily unavailable
181. Result too large
182. rmdir: variable: Directory not empty
183. ROOT LOGIN /dev/console
184. ROOT LOGIN /dev/pts/N FROM variable
185. rx framing error

186. SCSI bus DATA IN phase parity error
187. SCSI transport failed: reason 'reset'
188. Segmentation Fault
189. sendmail[N]: NOQUEUE: SYSERR: net hang reading from variable
190. setmnt: Cannot open /etc/mnttab for writing
191. share_nfs: /home: Operation not applicable
192. Soft error rate (N%) during writing was too high
193. Soft error rate (retries = N) during writing was too high
194. Stale NFS file handle
195. statd: cannot talk to statd at variable
196. stty: TCGETS: Operation not supported on socket
197. su: No shell
198. su: 'su root' failed for variable on /dev/pts/N
199. su: 'su root' succeeded for variable on /dev/pts/N
200. syncing file systems...
201. syslog service starting.

202. tar: /dev/rmt/0: No such file or directory
203. tar: directory checksum error
204. tar: tape write error
205. Text is lost because the maximum edit log size has been exceeded.
206. THE FOLLOWING FILE SYSTEM(S) HAD AN UNEXPECTED INCONSISTENCY:
207. The SCSI bus is hung. Perhaps an external device is turned off.
208. THE SYSTEM IS BEING SHUT DOWN NOW !!!
209. The system will be shut down in N minutes
210. This mail file has been changed by another mail reader.
211. Timeout waiting for ARP/RARP packet
212. timeout waiting for input during variable
213. Too many links
214. Too many open files

215. umount: warning: /variable not in mnttab
216. Unable to install/attach driver 'variable'
217. undefined control
218. Unmatched `
219. UNREF FILE I=i OWNER=o MODE=m SIZE=s MTIME=t ======== CLEAR?
220. Use "logout" to logout.
221. /usr/openwin/bin/xinit: connection to X server lost

222. Value too large for defined data type
223. variable... Host unknown
224. variable... User unknown
225. variable... Local configuration error

226. WARNING: Clock gained N days-- CHECK AND RESET THE DATE!
227. WARNING: No network locking on variable: contact adminto install server change
228. WARNING: processorlevel 4 interrupt not serviced
229. WARNING: /tmp: File system full, swap space limit exceeded
230. WARNING: TOD clock not initialized-- CHECK AND RESET THE DATE!
231. WARNING:Unable to repair the / filesystem. Run fsck
232. Watchdog Reset
233. Watchdog Reset, Rebooting.
234. Who are you?
235. Window Underflow

236. X connection to variable:0.0 broken (explicit kill or server shutdown).
237. xinit: not found
238. XIO: fatal IO error 32 (Broken pipe) on X server "variable:0.0"
239. Xlib: Client is not authorized to connect to Server
240. Xlib: connection to "variable:0.0" refused by server
241. xterm: fatal IO error 32 (Broken Pipe) or KillClient on X server " variable:0.0"
242. XView warning: Cannot load font set 'variable' (Font Package)

243. ypbind[N]: NIS server for domain "variable" OK
244. ypbind[N]: NIS server not responding for domain "variable"; still trying
245. ypwhich: can't communicate with ypbind

246. zsN: silo overflow

timeout waiting for input during variable
=============================================

When sendmail(1M) reads from anything that might time out, such
as an SMTP connection, it sets a timer to the value of the r
processing option before reading begins. If the read doesn't
complete before the timer expires, this message appears and
reading stops. (Usually this is during RCPT.) The mail message is
then queued for later delivery.

If you see this message often, increase the value of the r
processing option in the /etc/mail/sendmail.cf file. If the timer
is already set to a large number, look for hardware problems such
as poor network cabling or connections.

For more information about setting the timer, see the section
describing the sendmail configuration options in the Mail
Administration Guide. If you are using the AnswerBook, the term
"timeouts" is a good search string.

variable... Host unknown
============================

This sendmail(1M) message indicates that the destination host
machine, specified by the address portion after the @ (at-sign),
was not found during DNS (Domain NamingSystem) lookup.

Use the nslookup(1M) command to verify that the destination host
exists in that or other domains, perhaps with a slightly
different spelling. Failing that, contact the intended recipient
and ask for a proper address.

Sometimes thisreturn message indicates that the intended host is
merely down, rather than unknown. If a DNS record contains an
unknown alternate host, and the primary host is down, sendmail
returns a "Host unknown" message from the alternate host.?
For uucp mail addresses, the "Host unknown" message probably
means that the destination hostname is not listed in the
/etc/uucp/Systems file.

?This is a known sendmail version 8.6.7 bug.

For information on how sendmail works, see the Mail
Administration Guide.

variable... User unknown
============================

This sendmail(1M) message indicates that the intended recipient,
specified by the address portion before the @ (at-sign), could
not be located on the destination host machine.

Check the e-mail address and try again, perhaps with a slightly
different spelling. If this doesn't work, contact the intended
recipient and ask for a proper address.

For information on how sendmail works, see the Mail
Administration Guide.

variable... Local configuration error
=========================================

This sendmail(1M) message usually indicates that the local host
is trying to send mail to itself.

Check the value of the $j macro in the /etc/mail/sendmail.cf file
to ensure that this value is a fully-qualified domain name.

When the sending system provides its hostname to the receiving
system (in the SMTP HELO command), the receiving system compares
its name to the sender's name. If these are the same, the
receiving system issues this error messageand closes the
connection. The name provided in the HELO command is the value of
the $j macro.

For information on how sendmail works, see the Mail
Administration Guide.

A command window has exited because its child exited.
=====================================================

The argument to a cmdtool(1) or a shelltool(1) window looks like
it is supposed to be a command, but the system cannot find the
command.

To run this command inside a cmdtool or a shelltool, make sure
the command is spelled correctly and is in your search path (if
necessary, use a full path name). If you intended this argument
as an option setting, use a minus sign (-) at the beginning of
the option.

Both the cmdtool and the shelltool are OpenWindows terminal
emulators.

admintool: Received communication service error 4
=================================================

AdminTool could not start a display method because a remote
procedure call timed out, so it can't send the request. This
error results when admintool tries to access the NIS or NIS+
tables when networking is not enabled.

Verify the system network status with ifconfig -a to make sure
the system is connected to the network. Make sure the ethernet
cable is connected and the system is configured to run NIS or
NIS+.

answerbook: XView error: NULL pointer passed to xv_set
======================================================

The AnswerBook navigator window comes up, but the document viewer
window does not. This message appears on the console, and the
message "Could not start new viewer" appears in the navigator
window. This situation indicates that you have an unknown client
or a problem with the network naming service.

Run the ypmatch(1) or nismatch(1) command o determine if the
client hostname is in the hosts map. If it isn't, add it to to
NIS hosts map on the NIS master server. Then make sure the
/etc/hosts file on the client contains an IP address and entry
for that hostname followed by loghost (reboot if you changed the
/etc/hosts file). Check that the ypmatch or nismatch client hosts
command returns the same IP host address as in the /etc/hosts
file. Finally, quit all existing AnswerBooks and restart.

For more information on the NIS hosts map, see the section on the
default search criteria in the NIS+ and FNS Administration Guide.
If you are using the AnswerBook, "NIS hosts map" is a good search
string.

Arg list too long
=================

The system could not handle the number of arguments given to a
command or program when it combined those arguments with the
environment's exported shell variables. The argument list limit
is the size of the argument list plus the size of the
environment's exported shell variables.

The easiest solution is to reduce the size of the parent process
environment by unsetting extraneous environment variables. (See
the man page for the shell you're using to find out how to list
and change your environment variables.) Then run the program
again.

An argument list longer than ARG_MAX bytes was presented to a
member of the exec() family of system calls.

The symbolic name for this error is E2BIG, errno=7.

Argument out of domain
======================

This is a programming error or a data input error.

Ask the program's author to fix this condition,or supply data in
a different format.

This indicates an attempt to evaluate a mathematical programming
function at a point where its value is not defined. The argument
of a programming function in the math package (3M) is out of the
domain of the function. This could happen when taking the square
root, power, or log of a negative number, when computing a power
to a non-integer, or when passing an out-of-range argument to a
hyperbolic programming function.

To help pinpoint a program's math errors, use the matherr(3M)
facility.

The symbolic name for this error is EDOM, errno=33.

Arguments too long
==================

This C shell error message indicates that there are too many
arguments after a command. For example, this can happen by
invoking rm * in a huge directory. The C shell cannot handle more
than 1706 arguments.

Temporarily start a Bourne shell with sh and run the command
again. The Bourne shell dynamically allocates command line
arguments. Return to your original shell by typing exit.

assertion failed: variable, file variable, line N
=================================================

A condition in the program that was never expected to happen has
happened.

Contact the vendor or author of the program to ask why it failed.
If you have the source code for the program, you can look at the
file and line number where the assertion failed. This might give
you an idea of how to run the program differently.

This message results from a diagnostic macro called assert() that
a programmerinserted into the specified line of a source file.
The expression that evaluated untrue precedes the file name and
line number.

automountd[N]: No network locking on variable: contact admin to install server change
=====================================================================================

See "WARNING: No network locking on variable: contact admin to
install server" message for details. If the server is not
changed, data loss is possible in applications that depend on
locking.

automountd[N]: server variable not responding
=============================================

This automounter message indicates that the system tried to mount
a filesystem from an NFS server that is either down or extremely
slow to respond. In some cases thismessage indicates that the
network link to the NFS server is broken, although that condition
produces other error messages as well.

If you are the system administrator responsible for the non-
responding NFS server, check it out to see whether the machine
needs repair or rebooting. Encourage your user community to
report such problems quickly but only once. When the NFS server
is back in operation, the automounter will be able to access the
requested filesystem.

For more information on NFS failures, seethe section on NFS
troubleshooting in the NFS Administration Guide. If you are using
the AnswerBook, a good search string is "NFS Service."

automount[N]: variable: Not a directory
=======================================

The file specified after the first colon is not a valid mount
point because it is not a directory.

Ensure that the mount point is a directory, and not a regular
file or a symbolic link.

Bad address
===========

The system encountered a hardware fault in attempting to access a
parameter of a programming function.

Check if the bad address resulted from supplying the wrong device
or option to a command. If that is not the problem, contact the
vendor or author of the program for an update.

This error could occur any time a function that takes a pointer
argument is passed an invalid address. Because processors differ
in their ability to detect bad addresses, on some architectures
passing bad addresses can result in undefined behaviors.

The symbolic name for this error is EFAULT,errno=14.

BAD/DUP FILE I=i OWNER=o MODE=m SIZE=s MTIME ==== CLEAR?

While checking inode link counts during phase 4, fsck(1M) found a
file (or directory) that either does not exist or exists
somewhere else.

To clear the inode of its reference to this file or directory,
answer yes. With the -p (preen) option, fsck automatically clears
bad or duplicate file references, so answering yes to this
question seldom causes a problem.

Bad file number
===============

Generally this is a program error, not a usage error.

Contact the vendor or author of the program for an update.

Either a file descriptor refers to no open file, or a read (or
write) request is made to a file that is open only for writing
(or reading).

The symbolic name for this error is EBADF, errno=9.

N BAD I=N
=========

Upon detecting an out-of-range block, fsck(1M) prints the bad
block number and its containing inode (after I=).

In fsck phases 2 and 4, you will decide whether ornot to clear
these bad blocks.  Before committing to repair with fsck, you
could determine which file contains this inode by passing the
inode number to the ncheck(1M) command: by passing the inode
number to the ncheck(1M) command:

# ncheck -iinum filesystem

For more information, see the chapter on checking filesystem
integrity in the System Administration Guide, Volume I.

bad module/chip at: variable
============================

This message from the memory management system often appears with
parity errors, and indicates a bad memory module or chip at the
position listed. Data loss is possible if the problem occurs
other than at boot time.

Replace the memory module or chip at the indicated position.
Refer to the vendor's hardware manual forhelp finding this
location.

BAD SUPER BLOCK: variable
=========================

This message from fsck(1M) indicates that a filesystem's super-
block is damaged beyond repair and must be replaced. At boot time
(with the -p option) this message is prefaced by the filesystem's
device name. After this message comes the actual damage
recognized (see Action). Unfortunately fsck does not print the
number of the damaged super-block.

The most common cause of this error is overlapping disk
partitions. Donot immediately rerun fsck as suggested by the
lines that display after the error message.  First make sure that
you have a recent backup of the filesystem involved; if not, try
to back up the filesystem now using ufsdump(1M). Then run the
format(1M) command, select the disk involved, and print out the
partition information.

# format : N > partition > print

Note whether the overlap occurs at the beginning or end of the
filesystem involved.  Then run newfs(1M) with the -N option to
print out the filesystem parameters, including the location of
backup super-blocks.

# newfs -N /dev/dsk/device

Select a super-block from a non-overlapping area of the disk, but
note that in most cases you have only one chance to select the
proper replacement super-block, which fsck soon propagates to all
the cylinders. If you select the wrong replacement super-block,
data corruption will probably occur, and you will have to restore
from backup tapes.  After you select a new super-block, provide
fsck with the new master super-block number:

# fsck -o b=NNNN /dev/dsk/device

Specific reasons for a damaged super-block include: a wrong magic
number, out of range NCG (number of cylinder groups) or CPG
(cylinders per group), the wrong number of cylinders, a
preposterously large super-block size, and trashed values in
super-block. These reasons are generally not meaningful because a
corrupt super-block is usually extremely corrupt.

For more information on bad superblocks, see the sections on
restoring bad superblocks in the System Administration Guide,
Volume I. If you are using the AnswerBook, "superblock" is a good
search string.

BAD TRAP
========

A bad trap can indicate faulty hardware or a mismatch between
hardware and its configuration information. Data loss is possible
if the problem occurs other than at boot time.

If you recently installed new hardware, verify that the software
was correctly configured. Check the kernel traceback displayed on
the console to see which device generated the trap. If the
configuration files are correct, you will probably have to
replace the device.

In some cases, the bad trap message indicates a bad or down-rev
CPU.

A hardware processor trap occurred, and the kernel trap handler
was unable to restore system state. This is a fatal error that
usually precedes a panic, after which the system performs a sync,
dump, and reboot. The following conditions can cause a bad trap:
a system text or data access fault, a system data alignment
error, or certain kinds of user software traps.

bad trap = N
============

See the message "BAD TRAP" for details.

/bin/sh: variable: too big
==========================

This Bourne shell message indicates a classic "no memory" error.
While trying to load the program specified after thefirstcolon,
the shell noticed that the system ran out of virtual memory (swap
space).

See the message "Not enough space" for information on
reconfiguring your system to add more swap space.

Block device required
=====================

A raw (character special) device was specified where a block
device was required, such as during a call to the mount(1M)
command.

To see which block devices are available, use ls -l to look in
/devices. Then specify a block device instead of a character
device. Block device modes start with a b, whereas raw character
device modes start with a c.

The symbolic name for this error is ENOTBLK, errno=15.

Boot device: /iommu/sbus/variable/variable/sd@3,0
=================================================

This message alwaysappears at the beginning of rebooting. If
there is a problem, the system hangs, and no other messages
appear. This condition is caused by conflicting SCSI targets for
the boot device, which is almost always target 3.

The boot device is usually the machine's internal disk drive,
target 3. Make sure that external and secondary disk drives are
targeted to 1, 2, or 0, and do not conflict with each other. Also
make sure that tape drives are targeted to 4 or 5, and CD drives
to 6, avoiding any conflict with each other or with the disk
drives. You can set a device's target number using pushbutton
switches or a dial on the back near the SCSI cables. If the
targeting of the internal disk drive is in question, check it by
powering off the machine, removing all external drives, turning
the power on, and running the probe-scsi-all or probe-scsi
command from the PROM monitor.

Broadcast Message from root (pts/N) on server [date]
====================================================

This message from the wall(1M) command gets transmitted to all
users logged into a system. You could see it during a rlogin or
telnet session, or on terminals connected to a timesharing
system.

Carefully read the broadcast message. Often this broadcast is
followed by a shutdown warning.

See the message "The system will be shut down in N minutes" for
details about system shutdown.

For more information on bringing down the system, see the section
on halting the system in the System Administration Guide, Volume
I. If you areusing the AnswerBook, "halting the system" is a
good search string.

Broken pipe
===========

This condition is often normal, and the message is merely
informational (as when piping many lines to the head program).
The condition occurs when a write on a pipe does not find a
reading process. This usually generates a signal to the executing
program, but this message displays when the program ignores the
signal.

Check the process at the end of the pipe to see why it exited.

The symbolic name forthis error is EPIPE, errno=32.

Bus Error
=========

A process has received a signal indicating that it attempted to
perform I/O to a device that is restricted or that does not
exist. This message is usually accompanied by a core dump, except
on read-only filesystems.

Use a debugger to examine the core file and determine what
program fault or system problem led to the bus error. If
possible, check the program's output files for data corruption
that might have occurred before the bus error.

Bus errors canresult from either programming error or device
corruption on your system. Some common causes of bus errors are:
invalid file descriptors, unreasonable I/O requests, bad memory
allocation, misaligned data structures, compiler bugs, and
corrupt boot blocks.

Cannot allocate colormap entry for "variable"
=============================================

This message from libXt (X Intrinsics library) indicates that the
system colormap was full even before the color name specified in
quotes was requested. Some applications can continue after this
message. Other applications, such as Workspace Properties Color,
fail to come up when the colormap is full.

Exit the programs that make heavy use of the colormap, then
restart the failed application and try again.

Can't create public message device (Device busy)
================================================

This message comes from the lp print scheduler, indicating that
it is either extremely busy or hung.

If print jobs are coming out of the printer in question, wait
until they are finished and then resubmit this print job. If you
see this message again, the lp system is probably hung.

See the message "lp hang" for a procedure to clear the queue.

If lp is unable to create a device for printer messages, the
message FIFO could be already in use, or locked by another print
job.

For more information on the print scheduler, see the section on
administrating printers in the System Administration Guide Volume
II.

Can't invoke /etc/init, error N
===============================

This message can appear while a system is booting, indicating
that the init program is missing or corrupted. Note that
/etc/init is a symbolic link to /sbin/init.

Boot the miniroot so you can replace init. Halt the machine by
typing Stop-A or by pressing the reset button. Reboot single-user
from CDROM, the net, or diskette. For example, type boot cdrom -s
at the ok prompt to boot from CDROM. After the system comes up
and gives you a # prompt, mount the device corresponding to the
original / partition somewhere, with a command similar to the
mount command below. Then copy the init program from the miniroot
to the original / partition, and reboot the system.

# mount /dev/dsk/c0t3d0s0 /mnt # cp /sbin/init /mnt/sbin/init #
reboot

If this doesn't work, other files might be corrupted, and you
might need to reinstall the entire system.

The error number is 2 if /sbin/init is missing, or 8 if
/sbin/init has an incorrect executable format. This is usually
followed by a "panic:icode" message. The system tries to reboot
itself, but goes into a loop, because rebooting is impossible
without init.

For more information on booting the system, see the section on
halting and booting the system in the System Administration
Guide, Volume I.

can't synchronize with hayes
============================

This message sometimes appears when using a modem that the system
regards as a "Hayes" type modem, which includes most modems
manufactured today. The message can be caused by incorrectswitch
settings, by poor cable connections, or by not turning the modem
on.

Check that the modem is on and that the cables between the modem
and your system are securely connected. Check the internal and
external modem switch settings. Turn themodem off and then on
again, if necessary.

cd: Too many arguments
======================

The C shell's cd(1) command takes only one argument. Either more
than one directory was specified, or a directory name containing
a space was specified.  Directory names with spaces are easy to
create with File Manager.

Use only one directory name. To change to a directory whose name
contains spaces, enclose the directory name in double (") or
single (') quotes, or use File Manager.

Channel number out of range
===========================

The system has run out of stream devices. This error results when
a stream head attempts to open a minor device that does not exist
or that is currently in use.

Check that the stream device in question exists and was created
with an appropriate number of minor devices. Make sure that the
hardware corresponds to this configuration. If the stream device
configuration is correct, try again later when more system
resources might be available.

The symbolic name for this error is ECHRNG, errno=37.

chmod: ERROR: invalid mode
==========================

This message from the chmod(1) command indicates a problem in the
first non-option argument.

If you are specifying a numeric file mode, you can provide any
number of digits (although only the final one to four are
considered), but all digits must be between 0 and 7. If you are
specifying a symbolic file mode, use the syntax provided in the
chmod usage message to avoid the "invalid mode" error message:

Usage: chmod [ugoa][+-=][rwxlstugo] file ...

Note that some combinations of symbolic keyletters produce no
error message but fail to have any effect. The first group,
[ugoa], is truly optional. The second group, [+-=], is mandatory
for chmod to have an effect. The third group,[rwxlstugo], is
also mandatory for effect, and can be used in combination when
that combination does not conflict.

Command not found
=================

The C shell could not find the program you gave as a command.

Check the form and spelling of the command line. If that looks
correct, echo $path to see if the user's search path is correct.
When communications are garbled, it is possible to unset a search
path to such an extent that only built-in shell commands are
available. Here is a command to reset a basic search path:

 % set path = (/usr/bin /usr/ccs/bin /usr/openwin/bin .)

If the search path looks correct, check the directory contents
along the search path to see if programs are missing or if
directories are not mounted.

For moreinformation about the C shell, see csh(1).

Connection closed.
==================

This message can appear when using rlogin(1) to another system if
the remote host cannot create a process for this user, if the
user takes too long to type the correct password, if the user
interrupts the network connection, or if the remote host goes
down. Data loss is possible if files were modified and not saved
before the connection closed.

Just try again. If the other system has gone down, wait for it to
reboot first.

Connection closed by foreign host.
==================================

When a user telnets to another system, this message can appear if
the user takes too long to type the correct password, if the
remote host cannot create a login for this user,or if theremote
host goes down or terminates the connection. Data loss is
possible if files were modified and not saved before the
connection closed.

Just try again. If the other system has gone down, wait for it to
reboot first.

[Connection closed.Exiting]
============================

After using the talk(1) command to communicate with another user,
the other person enters an interrupt (usually Control-c), and
this message appears on your screen.

Sending an interrupt like this is the usual wayof exiting the
talk program. The talk session is over and you can return to your
work.

Connection refused
==================

No connection could be made because the target machine actively
refused it. This happens either when trying to connect to an
inactive service or when a service process is not present at the
requested address.

Activate the service on the target machine, or start it up again
if it has disappeared. If for security reasons you do not intend
to provide this service, inform the user community, possibly
suggesting an alternative.

The symbolic name for this error is ECONNREFUSED, errno=146.

Connection timed out
====================

This occurs either when the destination host is down or when
problems in the network cause lost transmission.

First check the operation of the host system, for example by
using ping(1M) and ftp (1), then repair or reboot as necessary.
If that doesn't solve the problem, check the network cabling and
connections.

No connection was established in aspecified time. A connect or
send request failed because the destination host did not properly
respond after a reasonable interval. (The timeout period is
dependent on the communication protocol.)

The symbolic name for this error is ETIMEDOUT, errno=145.

console login: ^J^M^Q^K^K^P
===========================

This usually occurs because OpenWindows exited abnormally,
leaving the system's keyboard in the wrong mode. The characters
that appear when someone attempts to login are garbage
transliterations of what someone types.

Find another machine and remote login to this system, then run
this command:

$ /usr/openwin/bin/kbd_mode -a

This puts the console back into ASCII mode. Note that kbd_mode is
not a windows program, it just fixes the consolemode.

The usual reason for this problem occurring is an automated
script run from cron that clears out the /tmp directory every so
often. Ensure that any such scripts do not remove the /tmp/.X11-
pipe or /tmp/.X11-unix directories, or any files therein.

core dumped
===========

A core file contains an image of memory at the point of software
failure, and is used by programmers to find the reason for the
failure.

To see which program produced a core file, run either the file(1)
command or the adb (1) command. The following examples show the
output of the file and adb commands on a core file from the
dtmail program.

$ file core core: ELF 32-bit MSB core file SPARC Version 1, from
`dtmail'

$ adb core core file = core -- program `dtmail' SIGSEGV 11:
segmentation violation ^D      (use Control-d to quit the
program)

Ask the vendor or author of this program for a debugged version.

Some signals, such as SIGQUIT, SIGBUS, and SIGSEGV, produce a
core dump. See the signal(5) man page for a complete list.

If youhave the source code for the program, you can try
compiling it with cc -g, and debugging it yourself using dbx or a
similar debugger. The where directive of dbx provides a stack
trace.

On mixed networks, it can be difficult to discern which machine
architecture produced a particular core dump, since adb on one
type of system generally cannot read a core file from another
type of system, and will produce an "unrecognized file" message.
Run adb on various machine architectures until youfind the right
one.

The term "core" is archaic-- ferrite core memory was supplanted
by silicon RAM in the 1970s, although spaceships still employ
core memory for its imperviousness to radiation.

For information on saving and viewing crash informationsee the
System Administration Guide, Volume II. If you are using the
AnswerBook, "system crash" is a good search string.

Could not initialize tooltalk (tt_open): TT_ERR_NOMP
====================================================

Various desktop tools display or print this message when the
ttsession(1) process is not available. The TookTalk service
generally tries to restart ttsession if it is not running. So
this error indicates that the ToolTalk service is either not
installed or is not installed correctly.

Verify that the ttsession command exists in /usr/openwin/bin or
/usr/dt/bin. If this command is not present, ToolTalk is not
installed correctly. The packages constituting ToolTalk are the
runtime SUNWtltk, developer support SUNWtltkd, and themanual
pages SUNWtltkm. CDE ToolTalk packages have the same names with
".2" appended.

The full TT_ERR_NOMP message string reads as follows: "No
ttsession is running, probably because tt_open() has not been
called yet. If this is returned from tt_open() it means ttsession
could not be started, which generally means ToolTalk is not
installed on the system."

Could not start new viewer
==========================

This message appears in the AnswerBook navigator window, along
with an XView error messageon the console.

See the message "answerbook: XView error: NULL pointer passed to
xv_set" for details.

cpio: Bad magic number/header.
==============================

A cpio(1) archive has either become corrupted or was written out
with an incompatibleversion of cpio.

Use the -k option to cpio to skip I/O errors and corrupted file
headers. This might permit you to extract other files from the
cpio archive. To extract files with corrupted headers, try
editing the archive with a binary editor such asemacs. Each cpio
file header contains a filename as a string.

For more information on magic numbers, see magic(4).

Cross-device link
=================

An attempt was made to make a hard link to a file on another
device, such as on another filesystem.

Establish a symbolic link using ln -s instead. Symbolic links are
permitted across filesystem boundaries.

The symbolic name for this error is EXDEV, errno=18.

data access exception
=====================

This message can result from running an old version of the
operating system that does not support new hardware, or by
running an operating system that is not configured for new
hardware. It can also result from incorrectly installed DSIMMs or
from a disk problem.

Upgrade your operating system toa version that supports the new
hardware or machine architecture. For example, upgrading a
SPARCstation 2 (with sun4c kernel architecture) to a SPARCstation
20 (with sun4m kernel architecture) requires an operating system
upgrade or reconfiguration.

For more information onupgrades, see the section describing
system and device configuration in the Solaris 1.x to Solaris 2.x
Transition Guide.

Data fault
==========

This is a kind of bad trap that usually causes a system panic.
When this message appears after a bad trap message, a system text
or data access fault probably occurred.?In the absence of a bad
trap message, this message might indicate a user text or data
access fault. Data loss is possible if the problem occurs other
than at boot time.

Make sure the machine can reboot, then check the log file
/var/adm/messages for hints about what went wrong.

?See the message "BAD TRAP" for more information.

Deadlock situation detected/avoided
===================================

A programming deadlock situation was detected and avoided.

If the system had not detected and avoided a deadlock, a piece of
software would have hung. Run the program again. The deadlock
might not reoccur.

This error usually relates to file and record locking, but can
also apply to mutexes, semaphores, condition variables, and
read/write locks.

The symbolic name for this error is EDEADLK, errno=45.

See the section on deadlock handling in the System Interface
Guide. See the section on avoiding deadlock in the Multithreaded
Programming Guide.

Device busy
===========

An attempt was made to mount a device that was already mounted or
to unmount a device containing an active file (such as an open
file, a current directory, a mount point, or a running program).
Thismessage also occurs when trying to enable accounting that is
already enabled.

To unmount a device containing active processes, close all the
files under that mount point, quit any programs started from
there, and change directories out of that hierarchy. Then try to
unmountagain.

Mutexes, semaphores, condition variables, and read/write locks
set this error condition to indicate that a lock is held.

The symbolic name for this error is EBUSY, errno=16.

/dev/rdsk/variable: CAN'T CHECK FILE SYSTEM.
============================================

The system cannot automatically clean (preen) this filesystem
because it appears to be set up incorrectly or is having hard
disk problems. This message asks that you run fsck(1M) manually,
since data corruption might already haveoccurred.

Run fsck to clean the filesystem in question. See the message
"/dev/rdsk/N:  UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY" for
proper procedures.

/dev/rdsk/variable: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
================================================================

At boot time the /etc/rcS script runs the fsck(1M) command to
check the integrity of filesystems marked "fsck" in /etc/vfstab.
If fsck cannot repair a filesystem automatically, it interrupts
theboot procedure and produces this message. When fsck gets into
this state, it cannot repair a filesystem without losing one or
more files, so it wants to defer this responsibility to you, the
administrator. Data corruption has probably already occurred.

First run fsck -n on the filesystem, to see how many and what
type of problems exist.  Then run fsck again to repair the
filesystem. If you have a recent backup of the filesystem, you
can generally answer "y" to all the fsck questions. It's a good
idea to keep a record of all problematic files and inode numbers
for later reference. To run fsck yourself, specify options as
recommended by the boot script. For example:

# fsck /dev/rdsk/c0t4d0s0

Usually the files lost during fsck repair are these that were
created just before a crash or power outage, and they cannot be
recovered. If you lose important files, you can recover them from
backup tapes.

If you don't have a backup, ask an expert to run fsck for you.

For more information on file checking, see the section on
checking filesystem integrity in the System Administration Guide,
Volume I.

Directory not empty
===================

The directory operation that was attempted, such as directory
removal with rmdir, can be performed only on an empty directory.

To removethe directory, first remove all the files that it
contains. A quick way to remove a non-empty directory hierarchy
is with the rm -r command.

The symbolic name for this error is ENOTEMPTY, errno=93.

Disc quota exceeded
===================

The user'sdisk limit has been exceeded on a user filesystem,
usually because a file was just created or enlarged beyond the
limit. This almost always refers to a magnetic disk, and not to
an optical disc. Any data created after this condition occurs
will be lost.

The user can delete files to bring disk usage under the limit, or
the server administrator can use the edquota(1M) command to
increase the user's disk limit.

The symbolic name for this error is EDQUOT, errno=49.

dumptm: Cannot open `/dev/rmt/variable': Device busy
====================================================

During filesystem backup, the dump program cannot open the tape
drive because some other process is holding it open.

Find the process that has the tape drive open, and either kill(1)
the process or wait for it to finish.

# ps -ef | grep /dev/rmt # kill -9 processID

DUP/BAD I=i OWNER=o MODE=m SIZE=s MTIME=t FILE=f  REMOVE?
=========================================================

During phase 1, fsck(1M) found duplicate blocksor bad blocks
associated with the file or directory specified after FILE= whose
inode number appears after I= (with other information).

To remove this file or directory, answer yes. If you end up
removing more than a few files in this manner, data loss will
result, so it might be preferable to restore the filesystem from
backup tapes.

For more information on checking filesystems, see the section on
checking filesystem integrity in the System Administration Guide,
Volume I.

N DUP I=N
=========

Upon detecting a block that is already claimed by another inode,
fsck(1M) prints the duplicate block number and its containing
inode (after I=).

In fsck phases 2 and 4, you will decide whether or not to clear
these bad blocks.  Before committing to repairwith fsck, you
could determine which file contains this inode by passing the
inode number to the ncheck(1M) command:

# ncheck -iinum filesystem

For more information, see the chapter on checking filesystem
integrity in the System Administration Guide,Volume I.

error: DPS has not initialized or server connection failed
==========================================================

This message appears when trying to run AnswerBook with a generic
X11 window server or on a generic X terminal.

Running AnswerBook requires Display PostScript (DPS), or a NeWS
server, or the Adobe DPS NS remote display software. In addition,
a complete LaserWriterII Type-1 font set (including Palatino)
should be installed on the X server. To find out if your X server
has DPS, run xdpyinfo(1) to verify the presence of an "Adobe-
DPS-Extension" line. X servers without this line don't know about
DPS.

ERROR: missing file arg (cm3)
=============================

An attempt was madd to run some sccs(1) operation that requires a
filename, such as create, edit, delget, or prt.

Supply the appropriate filename after the SCCS operation.

ERROR [SCCS/s.variable]: `SCCS/p.variable' nonexistent (ut4)
============================================================

An attempt was made to sccs edit or sccs get a file that is not
yet under SCCS control.

Run sccs create on that file to place it under SCCS control.

ERROR [SCCS/s.variable]: writable `variable' exists (ge4)
=========================================================

An attempt was made to sccs edit a file that is writable,
probably because it is already checked out.

Run sccs info to see who has the file checked out. If it is you,
go ahead and edit it. If it is somebody else, ask that personto
check in the file.

esp0: data transfer overrun
===========================

When a user tries to mount a CDROM on a third-party CD drive,
mount(1M) fails with the above error, followed by the "sr0: SCSI
transport failed" message. The CD drive probably comes from a
vendor unknown to the system.

Third-party CD drives generally have an 8192 block size, as
opposed to the 512 block size on supported Sun drives. Check with
the vendor to see if any special configuration is possible to
allow the drive to operate on a Sun workstation.

Event not found
===============

This C shell message indicates that a user tried to repeat a
command from the history list, but that command or number does
not exist in the list.

Run the C shell history command to display recent events in the
history list. If a user often tries to run commands that have
disappeared from the history list, make the list longer by
setting history to a higher value.

For more information about the C shell, see csh(1).

EXCESSIVE BAD BLKSI=N  CONTINUE?
==================================

During phase 1, fsck(1M) found more than 10 bad (out-of-range)
blocks associated with the specified inode number.

With this many bad blocks, it might be preferable to restore the
filesystem from backup tapes.

For more information on bad blocks, see the section on checking
filesystem integrity in the System Administration Guide, Volume
I. If you are using the AnswerBook, "bad blocks" is a good search
string.

EXCESSIVE DUP BLKS I=N  CONTINUE?
==================================

During phase 1, fsck(1M) found more than 10 duplicate (previously
claimed) blocks associated with the specified inode number.

With this many duplicate blocks, it might be preferable to
restore the filesystem from backup tapes.

For more informationon blocks, see the section on checking
filesystem integrity in the System Administration Guide, Volume
I. If you are using the AnswerBook, "bad blocks" is a good search
string.

Exec format error
=================

This often happens when trying to runsoftware compiled for
different systems or architectures, such as when executing
Solaris 2.x programs on a SunOS 4.1.x system, or when trying to
execute SPARC-specific programs on an x86 machine. On a Solaris
2.x system, it can also occur if the BinaryCompatibility Package
was not installed.

Make sure that the software matches the architecture and system
you're using. The file(1) command can help you determine the
target architecture. If you're using SunOS 4.1.x softwareon a
Solaris 2.x system, make sure that the Binary Compatibility
Package is installed. You can check for it using this command:

$ pkginfo | grep SUNWbcp

A request was made to execute a file that, although it has the
appropriate permissions, does not start with a valid format.

The symbolic name for this error is ENOEXEC, errno=8.

See the a.out(4) man page for a description of executable files.

fd0: unformatted diskette or no diskette in the drive
=====================================================

This message appears on the system console to indicate that the
floppy driver fd(7) could not read the label on a diskette.
Usually this is either because a new diskette has not yet been
formatted, or a formatted diskette has become corrupted. This
message often appears along with "read failed" and "bad format"
messages after volcheck(1) is run.

If you are certain that the diskette contains no data, run
fdformat -d to format the diskette in DOS format. (You can also
format a diskette in UFS format if you like, although then it is
not transportable to most other systems.) When the diskette is
formatted, you can write on it, if it was not corrupted beyond
repair.

File exists
===========

The name of an existing file was mentioned in an inappropriate
context. For example,it is not allowed to establish a link to an
existing file, or to overwrite an existing file when the csh(1)
noclobber option is set.

Look at the names of files in the directory, then try again with
a different name or after renaming or removing the existing file.

The symbolic name for this error is EEXIST, errno=17.

File locking deadlock
=====================

This is a programming problem, in some cases unavoidable.

All a user can do is restart the program and hope deadlock does
not reoccur.

Inthe file locking subsystem, two processes tried to modify some
lock at the same time. In the multithreading subsystem, two
threads became deadlocked and could not continue. When a program
using the threads library encounters this error, it should
restart the deadlocked threads.

The symbolic name for this error is EDEADLOCK, errno=56.

filemgr: mknod: Permission denied
=================================

File Manager issues this message and fails to come up whenever
the /tmp/.removable directory is owned by another user and is not
1777 mode. This can happen, for example, when multiple users
share a workstation.

Have the original owner change the mode ((chmod(1)) of this file
back to 1777, its default creation mode. Rebooting the
workstation also resolves this problem.

This is a known problem that was fixed in Solaris 2.4.

File name too long
==================

The specified file name has too many characters.

If a file name or path name component is too long, devise a
shorter name. If the totalpath name is longer than PATH_MAX
characters, first change to an intermediate directory, then
specify a shorter path name. Newly-created data will be lost
unless written to another file with a shorter name.

In a UFS or NFS-mounted UFS filesystem, the length of a path name
component exceeds MAXNAMLEN (255) characters, or the total length
of the path name exceeds PATH_MAX (1024) characters. In a System
V filesystem, the length of a path name component exceeds
NAME_MAX (14) characters while no-truncation mode is in effect.
These values are defined in the /usr/include/limits.h(4) file.

The symbolic name for this error is ENAMETOOLONG, errno=78.

FILE SYSTEM STATE IN SUPERBLOCK IS WRONG; FIX?
==============================================

The fsck(1M) command has just checked a filesystem, and has
determined that the filesystem is clean. The filesystem's
superblock, however, still thinks the filesystem is "dirty" in
some way.

If you believe that the filesystem is adequately repaired, answer
yes to mark the filesystem as clean.

Different "dirty" filesystem types are listed in
/usr/include/sys/fs/ufs_fs.h, and include FSACTIVE, FSBAD, FSFIX,
FSLOG, and FSSUSPEND.

For more information on superblocks, see the section onchecking
filesystem integrity in the System Administration Guide, Volume
I. If you are using the AnswerBook, "bad superblock" is a good
search string.

File table overflow
===================

The kernel file table is full because too many files are open on
the system.  Temporarily, no more files can be opened. New data
created under this condition will probably be lost.

Simply waiting often gives the system time to close files.
However, if this message occurs often, reconfigure the kernel to
allow more open files. To increasethe size of the file table in
Solaris 2.x, increase the value of maxusers in the /etc/system
file.  The default maxusers value is the amount of main memory in
MB, minus 2.

The symbolic name for this error is ENFILE, errno=23.

File too large
==============

The file size exceeded the limit specified by ulimit(1), or the
file size exceeds the maximum supported by the file system. New
data created under this condition will probably be lost.

In the C shell, use the limit command to see or set the default
file size. In the Bourne or Korn shells, use the ulimit -a
command. Even when the shells claim that the file size is
unlimited, in fact the system limit is FCHR_MAX (usually 1
gigabyte).

The symbolic name for this error is EFBIG, errno=27.

FREE BLK COUNT(S) WRONG IN SUPERBLK  SALVAGE?
=============================================

During phase 5, fsck(1M) detected that the actual number of free
blocks in the filesystem did not match the superblock's free
block count.The df(1M) command accesses this free block count
when measuring filesystem capacity.

Generally you can answer yes to this question without harming the
filesystem.

For more information on superblocks, see the section on checking
filesystem integrity in the System Administration Guide, Volume
I. If you are using the AnswerBook, "bad superblock" is a good
search string.

fsck: Can't open /dev/dsk/variable
==================================

The fsck(1M) command cannot open the disk device, because
although a similar filesystem exists, the partition specified
does not.

Run the mount(1M) or the format(1M) command to see what
filesystems are configured on the machine. Then run fsck again on
an existing partition.

fsck: Can't stat /dev/dsk/variable
==================================

The fsck(1M) command cannot open the disk device, because the
specified filesystem does not exist.

Run the mount(1M) or the format(1M) command to see what
filesystems are configured on the machine. Then run fsck again on
an existing filesystem.

giving up
=========

This message appears in the SCSI log to indicate that a read or
write operation has been retried until it timed out. With SCSI
disk the timeout period is usually 30 seconds; with tape the
period is usually 20 attempts. Timeout periods are generally
coded into the drivers.

Check that all SCSI devices are connected and powered on. Make
sure that SCSI target numbers are correct and not in conflict.
Verify that all cables are no longer than six meters, total, and
that all SCSI connections are properly terminated.

The scsi_log(9F) routine usually displays messages on the system
console and in the /var/adm/messages file. Run the dmesg(1M)
command to see the most recent message buffer.

Graphics Adapterdevice /dev/fb is of unknown type
==================================================

The /dev/fb driver is either missing or corrupted.

See "InitOutput: Error loading module for /dev/fb" for details.

group.org_dir: NIS+ servers unreachable
=======================================

This is the second of three messages that an NIS+ client prints
when it cannot locate an NIS+ server on the network.

See the message "hosts.org_dir: NIS+ servers unreachable" for
details.

/home/variable: No such file ordirectory
=========================================

An attempt was made to change to a user's home directory, but
either that user does not exist or the user's fileserver has not
shared (exported) that filesystem.

To check on the existence of a particular user, run the
ypmatch(1) or nismatch(1) command, specifying the user name and
then the passwd map.

To export filesystems from the remote fileserver, become
superuser on that system and run the share(1M) command with the
appropriate options. If that system is sharing (exporting)
filesystems for the first time, also invoke
/etc/init.d/nfs.server start to begin NFS service.

For more information on sharing filesystems, see the
share_nfs(1M) man page.

Host is down
============

A transport connection failed because the destination host was
down. For example, mail delivery was attempted over several days,
but the destination machine was not available during any of these
attempts.

Report this error to the system administrator for the host. If
you are the person responsible for this system, check to see if
the machine needs repair or rebooting.

This error results from status information delivered by the
underlying communication interface. If there is no known
connection to the host, a different message usually results. See
"No route to host" for details.

The symbolic name for this error is EHOSTDOWN, errno=147.

host name configuration error
=============================

This is an old sendmail message, which replaced "I refuse to talk
tomyself" and is now replaced by the "Local configuration error"
message.

See the message "554 variable... Local configuration error" for
details.

hosts.org_dir: NIS+ servers unreachable
=======================================

This is the third of three messages that an NIS+ client prints
when it cannot locate an NIS+ server on the network.

If other NIS+ clients are behaving normally, check the Ethernet
cabling on the workstation showing this message. On SPARC
machines, disconnected network cablingalso produces a series of
"no carrier" messages. On x86 machines, the NIS+ messages might
be your only indication that network cabling is disconnected.

If many NIS+ clients on the network are giving this message, go
to the NIS+ server in question and reboot or repair it, as
necessary. When the server machine is back in operation, NIS+
clients will give an "NIS server for domain OK" message.

I can't read your attachments. What mailer are you using?
=========================================================

The SunView mailtool andpre-3.3 OpenWindows mailtool produce
this message when they cannot cope with an attachment. The
attachment is probably in MIME (Multipurpose Internet Mail
Extensions) format, using base64 encoding.

To read a mail message containing MIME attachments, use
mailtool(1) from Solaris 2.3 or later. If you are running an
earlier version of Solaris, rlogin(1) to a later version of
Solaris, set the DISPLAY environment variable back to the first
system, and run mailtool remotely. If those options prove
impossible, ask the originator to send the message again using
mailtool, or using the CDE dtmail compose File->SendAs-
>SunMailTool option.

Standard MIME attachments with base64 encoding, for example,
produce this message and fail to display in older mailtools.

Look into using metamail, available on the Internet, which allows
you to send and receive MIME attachments.

ie0: Ethernet jammed
====================

This message can appear on SPARCservers or x86 machines with an
Intel 82586 Ethernet chip. It indicates that 16 successive
transmission attempts failed, causing the driver to give up on
the current packet.

If this error occurs sporadically or at busy times, it probably
means that the network is saturated. Wait for network traffic to
clear. If bottlenecks arise frequently, think about reconfiguring
the network or adding subnets.

Another possible cause of this message is a noise source
somewhere in the network, such as a loose transceiver connection.
Use snoop(1M)or a similar program to isolate the problem area,
then check and tighten network connectors as necessary.

ie0: no carrier
===============

This message can appear on SPARCservers or x86 machines with an
Intel 82586 Ethernet chip. It indicates that thechip has lost
input to its carrierdetect pin while trying to transmit a
packet, causing the packet to be dropped.

Check that the Ethernet connector is not loose or disconnected.
Other possible causes include an open circuit somewhere in the
network and noise on the carrier detect linefrom the
transceiver. Use snoop(1M) or a similar program to isolate the
problem area, then check the network connectors and transceivers,
as needed.

Illegal Instruction
===================

A process has received a signal indicating that it attempted to
execute an instruction that is not allowed by the kernel. This
usually results from running programs compiled for a slightly
different machine architecture. This message is usually
accompanied by a core dump, excepton read-only filesystems.

If you are booting from CDROM or from the net, check README files
to make sure you are using an image appropriate for your machine
architecture. Run df to make sure there is enough swap space on
the system; too little swap space can cause this error. If you
recently upgraded your CPU to a new architecture, replace your
operating system with one that supports the new architecture (an
operating system upgrade might be required).

Sometimes this condition results from programming error, such as
when a program attempts to execute data as instructions. This
condition can also indicate device file corruption on your
system.

Illegal instruction "0xN" was encountered at PC 0xN
===================================================

The machine is trying to boot from a non-boot device, or from a
boot device for a different hardware architecture.

If you are booting from the net, check README files to make sure
you are using a boot image for that architecture. If you are
booting from disk, make sure the system is looking at the right
disk, which is usually SCSI target 3. Failing these solutions,
connect a CD drive to the system and boot from CDROM.

Illegal seek
============

Using a pipe ("|") on the command line doesn't work here.

Rather than using a pipe on the command line, redirect the output
of the first program into a file and then run the second program
on that file.

A call to lseek(2) was issued to a pipe. This error condition can
also be fixed by altering the program to avoid using lseek().

The symbolic name for this error is ESPIPE, errno=29.

Image Tool: Unable to open XIL Library.
=======================================

This message follows multiple multi-line "XilDefaultErrorFunc"
errors, indicating that ImageTool could not locate the X Imaging
Library. Many OpenWindows and CDE deskset programs require XIL.

Run pkginfo(1) to determine what packages are installed on the
system. If the following packages are not present, install them
from CDROM or over thenet:  SUNWxildg, SUNWxiler, SUNWxilow, and
SUNWxilrt.

Inappropriate ioctl for device
==============================

This is a programming error.

Ask the program's author to fix this condition. The program needs
to be changed so it employs a device driver that can accept
special character device controls.

The ioctl() system call was given as an argument for a file that
is not a special character device. This message replaces the
traditional but puzzling "Not a typewriter" message.

The symbolic name for this error is ENOTTY, errno=25.

INCORRECT BLOCK COUNT I=N (should be N)  CORRECT?
=================================================

During phase 1, fsck(1M) determined that the specified inode
pointed to a number of bad or duplicate blocks, sothe block
count should be corrected to the actual number shown.

Generally you can answer yes to this question without harming the
filesystem.

For more information on bad blocks, see the section on checking
filesystem integrity in the System Administration Guide, Volume
I.

inetd[N]: execv /usr/sbin/in.uucpd: No such file or directory
=============================================================

This message indicates that the Internet services daemon
inetd(1M) tried to start up the UUCP service without the UUCP
daemon existing on the system.

The SUNWbnuu package must be installed before the machine can run
UUCP. Run pkgadd(1M) to install this package from the
distribution CDROM or over the network.

inetd[N]: variable/tcp: unknown service
=======================================

This message indicates that the Internet services daemon
inetd(1M) could not locate the TCP service specified after the
first colon.

Check the current machine's /etc/services file, and the NIS
services map, to see if the service is described. To start this
service, add an appropriate entry into the /etc/services file and
possibly the services map as well. Note that NIS+ does not
consult the local /etc/services file unless you put "files" right
after "nisplus" on the services line of the system's
/etc/nsswitch.conf file.

If you do not want to start this service, edit the system's
/etc/inetd.conf file and delete the entry that tries to start it
up.

For more information about NIS+, see the NIS+ and FNS
Administration Guide.

inetd[N]: variable/udp:unknown service
=======================================

This message indicates that the Internet services daemon
inetd(1M) could not locate the UDP service specified after the
first colon.

See the message "inetd[N]: variable/tcp: unknown service" fora
solution.

inetd: Too many open files
==========================

This message can appear when someone runs a command from the
shell or uses a third-party application. The sar(1M) command does
not indicate that the system-wide open file limit has been
exceeded.

The probable cause for this is that the shell limit has been
exceeded. The default open file limit is 64, but can be raised to
256.

See the message "Too many open files" for a solution.

INIT: Cannot create /var/adm/utmp or /var/adm/utmpx
===================================================

This console message indicates that init(1M) cannot write in the
/var directory, which is usually part of the / (root) filesystem.
Some other messages follow, andthe system usually comes up
single-user. The problem is often that / or /var is mounted
read-only. Sometimes a brief power outage leaves the system
believing that many filesystems are still mounted.

If /var is a separate filesystem on the machine, andis not yet
not mounted, mount it now. If the filesystem containing /var is
mounted read-only, remount it read-write with a command similar
to this:

# mount -o rw,remount /

Then type Control-d and try to bring up the system multi-user. If
that fails, the root filesystem is probably corrupted.  Run
fsck(1M) on the root filesystem, halt the machine, power cycle
the CPU, and wait for the system to reboot. Should this problem
still occur, restore the root filesystem from backup tapes, or
re-install the system from net or CDROM to replace the root
filesystem.

InitOutput: Error loading module for /dev/fb
============================================

This fatal X server error message indicates that /dev/fb, the
"dumb frame buffer," is either missing or corrupted. It is
usually followed by a "giving up" message and a few xinit errors.

If other devices on the system are working correctly, the most
likely reason for this error is that the SUNWdfb package was
removed or never installed. Insert the installation CD-ROM,
change to the Solaris_2.xdirectory, and run the following
command to install the packages SUNWdfbh and SUNWdfb (for your
machine architecture):

pkgadd -d .

If other devices on the system are not working correctly, the
system might havea corrupt /devices directory. Halt the system
and boot using the -r (reconfigure) option.  The system will run
fsck(1M) if the /devices filesystem is corrupted, most likely
fixing the problem.

Interrupted system call
=======================

The user issued an interrupt signal (usually Control-c) while the
system was in the middle of executing a system call. When network
service is slow, interrupting cd(1) to a remote-mounted directory
can produce this message.

Proceed with your work, this message is purely informational.

An asynchronoussignal (such as interrupt or quit), which a
program was set up to catch, occurred during an internal system
call. If execution is resumed after processing the signal, it
will appear as if the interrupted programming function returned
this error condition, so the program might exit with an incorrect
error message.

The symbolic name for this error is EINTR, errno=4.

Invalid argument
================

An invalid parameter was specified that the system cannot
interpret. For example, trying to mount an uncreated filesystem,
printing without sufficient system support, or providing an
undefined signal to a signal(3c) library function, can all
produce this message.

If you see this message when you are trying to mount a
filesystem, make sure that you have run newfs(1M) to create the
filesystem. If you see this message when you are trying to read a
diskette, make sure that the diskette was properly formatted with
fdformat(1), either in DOS format (pcfs) or as a UFS filesystem.
If you see this message while you are trying to print, make sure
that the print service is configured correctly.

The symbolic name for this error is EINVAL, errno=22.

Invalid null command
====================

This C shell message results from a command line with two pipes
(|)in a row or from a pipe without a command afterwards.

Change the command line so that each pipe is followed by a
command.

I/O error
=========

Some physical Input/Output error has occurred. If the process was
writing a file, data corruption is possible.

First find out which device is experiencing the I/O error. If the
device is a tape drive, make sure a tape is inserted into the
drive. When this error occurs with a tape in the drive, it is
likely that the tape contains an unrecoverable bad spot.

If the device is a floppy drive, an unformatted or defective
diskette could be at fault.  Format the diskette, or obtain a
replacement.

If the device is a hard disk drive, you might need to run
fsck(1M) and possibly even reformat the disk.

In some cases this error might occur on a call following the one
to which it actually applies.

The symbolic name for this error is EIO, errno=5.

Is a directory
==============

An attempt was made to read or write a directory as if it were a
file.

Look at a listing of all the files in the current directory and
try again, specifying a file instead of a directory.

The symbolic name for this error is EISDIR, errno=21.

kernel read error
=================

This message appears when savecore(1M), if activated, tries to
copy a debugging image of kernel memory to disk but cannot read
various kernel data structures correctly. Generally this occurs
after a system panic has corrupted main memory.  Data corruption
on the systemis possible.

Look at the kernel error messages that preceded this one to try
to determine the cause of the problem. Error messages such as
"BAD TRAP" usually indicate faulty hardware. Until the problem
that caused the kernel panic is resolved, a kernel core image
cannot be saved for debugging.

Killed
======

This message is purely informational. If the killed process was
writing a file, some data might be lost.

Continue with your work.

This message from the signal handler or various shells indicates
that a process has been terminated with a SIGKILL. However, if
you don't see this message and cannot terminate a process with a
SIGKILL, you might have to reboot the machine to get rid of that
process.

kmem_free block already free
============================

This is a programming error,probably from a device driver.

Determine which driver is giving this message and contact the
vendor for a software update, as this message indicates a bug in
the driver.

This message is from the DDI programming function kmem_free(9F),
which releases a block of memory at address addr of size siz that
was previously allocated by the DDI function kmem_alloc(9F). Both
addr and siz must correspond to the original allocation. If you
have source code for the driver, follow kmem_alloc() and
kmem_free() in the code to make sure they allocate and free the
same chunk of memory.

last message repeated N times
=============================

This message comes from syslog(1M), the facility that prints
messages on the console and records them in /var/adm/messages. To
reduce the log size and minimize buffer usage, syslog collapses
any identical messages it sees during a 20 second period, then
prints this message with the number of repetitions.

Look above this message to see which message was repeated so
often. Then consider the repeated message and take action
accordingly. If repeated log entries such as "su ...  failed"
appear, consider the possibility of a security breach.

ld.so.1: variable: fatal: relocation error: symbol not found: variable
======================================================================

This message from the run-time linker ld.so.1 indicates that in
trying to execute the application given after the first colon,
the specified symbol could not be found for relocation. The
message goes on to say in what file the symbol was referenced.
Since this is a fatal error, the application terminates with this
message.

Run the ldd -d command on the application to show its shared
object dependencies and symbols that aren't found. Probably your
system contains an old version of the shared object that should
contain this symbol. Contact the library vendor or author for an
update.

This error does not necessarily occur when you first bring up an
application. It could take months to develop, if ordinary use of
the application seldom references the undefined symbol.

ld.so.1: variable: fatal: variable: can't open file: errno=2
============================================================

This message indicates that the run-time linker, ld.so.1, while
running the program specified after the first colon, could not
find the shared object specified after the third colon. (A shared
object is sometimes called a dynamically linked library.) Error
number 2 translates to "No such file or directory" (ENOENT).

As a workaround, set the environment variable LD_LIBRARY_PATH to
include the location of the shared object in question, for
example:

/usr/dt/lib:/usr/openwin/lib

Better yet, if you have accessto source code, recompile the
program using the -Rpath loader option. Using LD_LIBRARY_PATH is
discouraged because it slows down performance.

le0: Memory error!
==================

This message indicates that the network interface encountered an
access time-out from the CPU's main memory. There is probably
nothing wrong except system overload.

If the system is busy with other processes, this error can occur
frequently. If possible, try to reduce the system load by
quitting applications or killing some processes.

The Lance Ethernet chip timed out while trying to acquire the bus
for a DVMA transfer. Most network applications wait for a
transfer to occur, so generally no data gets lost. However, data
transfer might fail after too many time-outs.

For more information about the Lance Ethernet chip, see the
le(7D) man page.

le0: No carrier-- cable disconnected or hub link test disabled?
===============================================================

Standalone machines with no Ethernet port connection get this
error when the system triesto access the network. If the
Ethernet cable is disconnected, SPARC machines with the sun4m
architecture usually display this message, whereas machines with
the sun4c architecture usually display the "le0: No carrier--
transceiver cable problem" message instead. If the Ethernet cable
is connected, this message could result from a mismatch between
the machine's NVRAM settings and the Ethernet hub settings.

If this message is continuous, try to save any workto local
disk.

When a machine is configured as a networked system, it must be
plugged into the Ethernet with a twisted pair J45 connector.

If the Ethernet cable is plugged in, find out whether or not the
Ethernet hub does a Link Integrity Test. Then become superuser to
check and possibly set the machine's NVRAM. If the hub's Link
Integrity Test is disabled, set this variable to false.

# eeprom | grep tpe tpe-link-test?=true # eeprom 'tpe-link-
test?=false'

The default setting is true. If for some reason tpe-link-test?
was set to false,and the hub's Link Integrity Test is enabled,
set this variable to true.

le0: No carrier-- transceiver cable problem?
============================================

Standalone machines with no Ethernet port connection get this
error when the system tries to access the network.

If this message is continuous, try to save any work to local
disk.

When a machine is configured as a networked system, it must be
plugged into the Ethernet with either a twisted pair J45
connector or thicknet 10Base-T connector (depending on the
building's Ethernet cable type).

Older workstations have a thicknet connection on the back instead
of a twisted pair Ethernet connection, so they require a thicknet
to twisted pair transceiver to translate between cabling types.

LINK COUNT FILE I=i OWNER=o MODE=m SIZE=s MTIME=t COUNT...  ADJUST?
===================================================================

During phase 4, fsck(1M) determined that the inode's link count
for the specified file is wrong, and asks if you want to adjust
it to the value given.

Generally you can answer yes to this question without harming the
filesystem.

For more information on fsck, see the section on checking
filesystem integrity in the SystemAdministration Guide, Volume
I.

LL105W: Protocol error detected.
================================

This error message comes from Lifeline Mail, an unbundled PC
compatibility application.

The likeliest cause for this problem is that someone set up a
user account without a password. Assign the user a password to
solve this problem.

ln: cannot create /dev/fb: Read-only file system
================================================

During device reconfiguration at boot time, the system cannot
link to the frame buffer because /dev is on a read-only
filesystem.

Check that /dev/fb is a symbolic link to the hardware frame
buffer, such as cgsix or tcx. Ensure that the filesystem
containing /dev is mounted read-write.

lockd[N]: create_client: no name forinet address 0xN
=====================================================

This lock daemon message usually indicates that the NIS
hosts.byname and hosts.byaddr maps are not coordinated.

Wait a short time for the maps to synchronize. If they don't,
takesteps to coordinate them.

For information on updating NIS data, see the section on NIS maps
in the NIS+ and FNS Administration Guide. If you are using the
AnswerBook, "hosts.byaddr" is a good search string.

Login incorrect
===============

This message from the login(1) program indicates an incorrect
combination of login name and password. There is no way to tell
whether what's wrong is the login name, the password, or both.
Other programs such as ftp(1), rexecd(1M), sulogin(1M), and
uucp(1C) alsogive this error under similar conditions.

Check the /etc/passwd file and the NIS or NIS+ passwd map on the
local system to see if an entry exists for this user. If a user
has simply forgotten the password, su and set a new one with the
passwd usernamecommand. This command automatically updates the
NIS+ passwd map, but with NIS you'll need to coordinate the
update with the passwd map.

The "Login incorrect" problem can also occur with older versions
of NIS when the user name has more than eight characters. If this
is the case, edit the NIS password file, change the user name to
have eight or fewer characters, and then remake the NIS passwd
map.

If you cannot log in to the system as root, despite knowing the
proper password, it is possible that the /etc/passwd file is
corrupted. Try to log in as a regular user and su to root.

If that doesn't work, see the message "su: No shell" and follow
most of the instructions given there. Instead of changing the
default shell however, make the password field blank in
/etc/shadow.

lp hang
=======

On a print server, the queue continues to grow but nothing comes
out of the printer.  The printer daemon is hung.

Here is a simple procedure for flushing a hung printing queue:

 1. Login or switch user to root.
 2. Issue the reject printername command to make sure no one
sends any job to the
   printer.
 3. Turn off power to the printer.
 4. If the active job appears to be causing the hang, remove it
from the print queue
   with the cancel jobnumber command, and ask the owner to
requeue that print
   job.
 5. Shut down the print queue with the /usr/lib/lpshut command.
 6. Remove the lock file /var/spool/lp/SCHEDLOCK and the
temporary files
   /var/spool/lp/tmp/*/*.
 7. Turn the printer back on.
 8. Restart the print queue with the /usr/lib/lpsched command.

For more information on print queuing, see the System
Administration Guide, Volume II. If you are using the AnswerBook,
"print server" is a good search string.

mailtool: Can't create dead letter: Permission denied
=====================================================

An attempt was made to send a message with mailtool(1) from a
directory where the user does not have write permission, and the
user's home directory is currently unavailable.

Change to another directory and start mailtool again, or use
chmod(1) to change permissions for the directory (if possible).

mailtool: Could not initialize the Classing Engine
==================================================

When a user runs mailtool(1) on a remote machine, setting the
DISPLAY environment back to the local machine, this message might
appear inside a dialog box window. The dialog box goes on to say
that the Classing Engine must be installed to use Attachments.
This problem occurs because rlogin(1) does not propagate the
user's environment.

Exit mailtool and set your OPENWINHOME environment variable to
/usr/openwin.  Then run mailtool again. The error message will
not appear, and you will be able to use Attachments.

Classing Engine is a new name for Tool Talk. Earlier versions of
mailtool said "Tool Talk: TT_ERR_NOMP" instead of Classing
Engine.

Mail Tool is confused about the state of your Mail File.
========================================================

This message appears in a pop-up dialog box whenever you ask
mailtool(1) to access messages after another mail reader has
modified your inbox. A request follows:  "Please Quit this Mail
Tool."

Click "Continue" to close the dialog box, then exit mailtool. If
you continue trying to read mail, messages deleted by the other
mail reader will never appear, and mailtool will fail to see any
new messages.

mail: Your mailfile was found to be corrupted (Content-length mismatch).
=======================================================================

This message comes from mail(1) or mailx(1) whenever it detects
messages with a different content length than advertised. The
mail program tells you which message might be truncated or might
have another message concatenated to it.

Two common causes of content length mismatches are the
simultaneous use of different mail readers (such as mail and
mailtool), or using a mail reading program (or an editor) that
does not update the Content-Length field after altering a
message.

The mailx program can usually recover from this error and
delineate mail message boundaries correctly. Pay close attention
to the message that might be truncated or combined with another
message, and to all messages after that one. If a mail file
becomes hopelessly corrupted, run it through a text editor to
eliminate all Content-Length lines, and ensure that each message
has a From (no colon) line for each message, preceded by a blank
line.

To avoid mailfile corruption, exit from mailtool without saving
changes when you are currently running mail or mailx.

Memory address alignment
========================

This message can occur when printing large files on a
SPARCprinter attached to a SPARCstation 2.

Replace the SPARCstation 2 CPU with one that isat the most
recent dash level.

memory leaks
============

An application uses up more and more memory, until all swap space
is exhausted.

Many developers have found that third party software (such as
Purify) can help identify memory leaks in their applications. If
you suspect that you have a memory leak, you can use sar(1) to
check on the Kernel Memory Allocation (KMA). Any driver or module
that uses KMA resources, but does not specifically return the
resources before it exits, can create a memory leak.

For more information on memory leaks, see the section on
monitoring system activity in the System Administration Guide,
Volume II. If you are using the AnswerBook, "displaying disk
usage" is a good search string. Also, see the section on system
resource problems in the NIS+ and FNS Administration Guide.

mount: /dev/dsk/variable is already mounted, /variable is busy, or...
=====================================================================

While trying to mount a filesystem, the mount(1M) command
received a "Device busy" (EBUSY) error code.There are several
possible reasons: this /dev/dsk filesystem is already mounted on
a different directory, the busy path name is the working
directory of an active process, or the system has exceeded its
maximum number of mount points (unlikely).

Run /etc/mount to see if the filesystem is already mounted. If
not, check to see if any shells are active in the busy directory
(did the user cd into the directory?), or if any processes in the
ps(1) listing are active in that directory. If the reason for the
error message isn't obvious, try using a different directory for
the mount point.

mount: giving up on: /variable
==============================

An existing server did not respond to an NFS mount request, so
after retrying a number of times (default1000), the mount(1M)
command has given up. Nonexistent servers or bad mount points
produce different messages.

If the "RPC: Program not registered" message precedes this one,
the requested mount serverprobably did not share (export) any
filesystems, so it has no NFS daemons running. Have the superuser
on the mount server share(1M) the filesystem, then run
/etc/init.d/nfs.server start to begin NFS service.

If the requested mount server is down or slow to respond, check
to see whether the machine needs repair or rebooting.

mount: mount-point /variable does not exist.
============================================

Someone tried to mount a filesystem onto the specified directory,
but there is no suchdirectory.

If this is the directory name you want,run mkdir(1) to create
this directory as a mount point.

mount: the state of /dev/dsk/variable is not okay
=================================================

The system was unable to mount the filesystem that was specified
because the super-block indicates that the filesystem might be
corrupted. This is not an impediment for read-only mounts.

If you don't need to write on this filesystem, mount(1M) it using
the -o ro option.  Otherwise, do as one of the message
continuation lines suggests and run fsck(1M) to correct the
filesystem state and update the super-block.

For more information on using fsck, see the section on checking
filesystem integrity in the System Administration Guide, Volume
I.

/net/variable: No such file or directory
========================================

A user tried to change directory (for example with cd) to a
network partition on the system specified after /net/, but this
host either does not exist or has not shared (exported) any
filesystem.

To gain access to files on this system, try rlogin(1).

To export filesystems from the remote system, become superuser on
that system and run the share(1M) command with the appropriate
options. If that system is sharing filesystems for the first
time, also run /etc/init.d/nfs.server start to begin NFS service.

Network is down
===============

A transport connection failed because it encountered a dead
network.

Report this error to the system administrator for the network. If
you are the person responsible for this network, check to see why
the network is dead and what repairs are necessary.

This error results from status information delivered by the
underlying communication interface.

The symbolic name for this error is ENETDOWN, errno=127.

Network is unreachable
======================

An operational error occurred either because there was no route
to the network or because negative status information was
returned by intermediate gateways or switching nodes.

The returned status is not always sufficient to distinguish
between a network that is down and a host that is down. See the
"No route to host" message.

Check the network routers and switches to see if they are
disallowing these packet transfers. If they areallowing all
packet transfers, check network cablingand connections.

The symbolic name for this error is ENETUNREACH, errno=128.

NFS getattr failed for server variable: RPC: Timed out
======================================================

This message appears on an NFS client that requested a service
from an NFS server whose hardware is failing. Often the message
"NFS read failed" appears along with this message. If the server
were merely down or slow to respond, the "NFS server not
responding" message would appear instead. Data corruption on the
server system is possible.

Because this message usually indicates server hardware failure,
initiate repair procedures as soon as possible. Check the memory
modules, disk controllers, and CPU board.

For more information on NFS tuning, see chapter on monitoring
network performance in the System Administration Guide, Volume
II.

nfs mount: Couldn't bind to reserved port
=========================================

This message appears when a client attempts to NFS mount a
filesystem from a server that has more than one Ethernet
interface configured on the same physical subnet.

Always connect multiple Ethernet interfaces on one router system
to different physical subnetworks.

nfs mount: mount: variable: Device busy
=======================================

This message appears when the superuser attempts to NFS mount on
top of an active directory. The busy device is actually the
working directory of a process.

Determine which shell on the workstation is currently located
below the mount point, and change out of that directory. Be wary
of subshells (such as su shells) that could be in different
working directories while the parents remain below the mount
point.

NFS mount: /variable mounted OK
===============================

While booting, the system failed to mount the directory specified
after the first colon, probably because the NFS server involved
was down or slow to respond. The mount ran in the background and
successfully contacted the NFS server.

This is a purely informative message to let you know that the
mount process has completed.

NFS read failed for server variable
===================================

This is generally a permissions problem. Perhaps a directory or
file permission was changed while the client held the file open.
Perhaps the filesystem's share or netgroup permissions changed.
If the server were down or the network saturated, the "NFS server
not responding" message would appear instead.

Log in to the NFS server and check the permissions of directories
leading to the file.  Make certain that the filesystem is shared
with (exported to) the client experiencing an NFS read failure.

For more information, see the chapter on NFS troubleshooting in
the NFS Administration Guide.

nfs_server: bad getargs for N/N
===============================

This message comes from the NFS server when it gets a request
with unrecognized or incorrect arguments. Typically, it means the
request could not be XDR decoded properly. This can result from
corruption of the packet over the network, or from an
implementation bug causing the NFS client to improperly encode
its arguments.

If this message originates from a single client, investigate that
machine for NFS client software bugs. If this message appears all
over a network, especially accompanied by other networking
errors, investigate the network cabling and connectors.

NFS server variable not responding still trying
===============================================

In mostcases this very common message indicates that the system
has requested a service from an NFS server that is either down or
extremely slow to respond. In some cases this message indicates
that the network link to this NFS server is broken, although
usually that condition generates other error messages as well. In
a few cases this message indicates NFS client set-up problems.

Check the non-responding NFS server to see whether the machine
needs repair or rebooting. Encourage your user community to
report such problems quickly but only once.

Should this message appear when booting a diskless client, make
sure that the client's /etc/hosts file and the network naming
service (NIS, NIS+, or other /etc/hosts files on the network)
have been updated.

Formore information, see the chapter on NFS troubleshooting in
the NFS Administration Guide.

NFS server variable ok
======================

This message is the follow-up to the "NFS server not responding"
error. It indicates that the NFS server is back in operation.

When an NFS server first comes up, it will be busy fulfilling
client requests for a while. Be patient and wait for your client
system to respond. Making many extraneous requests only further
slows the NFS server response time.

nfs umount:variable: is busy
=============================

This message appears when the superuser attempts to unmount an
active NFS filesystem. The busy point is the working directory of
a process.

Determine which shell (or process) on the workstation is
currently located in the remotely mounted filesystem, and change
(cd) out of that directory. Be wary of subshells (such as su
shells) that could be in different directories while the parent
shells remain in the NFS filesystem.

NFS write error on host variable: No space left on device.
==========================================================

This console message indicates that an NFS-mounted partition has
filled up and cannot accept writing of new data. Unfortunately,
software that attempts to overwriteexisting files will usually
zero out all data in these files. This is particularly
destructive on NFS-mounted /home partitions.

Find the user or process that is filling up the filesystem, and
get the out-of-control process stopped as soon as you can. Then
delete files as necessary to create more space on the filesystem
(large core files are good candidates for deletion). Have users
write any modified files to local disk if possible. If this error
occurs often, redistribute directories to ease demandon this
partition.

For more information on disk usage, see the System Administration
Guide, Volume II.  If you are using the AnswerBook, "managing
disk use" is a good search string.

NFS write failed for server variable: RPC: Timed out
====================================================

This error can occur when a file system is soft-mounted, and
server or network response time lags. Any data written to the
server during this period could be corrupted.

If you intend to write on a filesystem, never specify the soft
mount option. Use the default hard mount for all the filesystems
that are mounted read-write.

For more information, see the chapter on NFS troubleshooting in
the NFS Administration Guide.

NIS+ authentication failure
===========================

This is a Federated Naming Service message. The operation could
not be completed because the principal making the request could
not be authenticated with the name service involved.

Run the nisdefaults(1) command to verify that you are identified
as the correct NIS+ principal. Also check that the system has
specified the correct public key source.

For more information, see the authentication and authorization
overview in the NIS+ and FNS Administration Guide.

No buffer space available
=========================

An operation on a transport endpoint or pipe was not performed
because the system lacked sufficient buffer space or because a
queue was full. The target system probably ran out of memory or
swap space. Any data written during this condition will probably
be lost.

To add more swap area, use the swap -a command on the target
system.  Alternatively, reconfigure the target system to have
more swap space. As a general rule, wwap space should be two to
three times as large as physical memory.

The symbolic name for this error is ENOBUFS,errno=132.

No child processes
==================

This message can appear when an application tries to communicate
with cooperating process that do not exist.

Restart the parent process so it can create the child processes
again. If that doesn't help, this could be the result of
programming error; contact the vendor or author of the program
for an update.

A wait(2) system call was executed by a process that had no
existing or unwaited-for child processes. The child processes
could have exited prematurely, or might never have been created.

The symbolic name for this error is ECHILD, errno=10.

No default media available
==========================

The volume manager issues this message if a user makes an
eject(1) request when the drives containno diskette or CDROM to
eject.

Insert a diskette or CDROM. If the volume manager is confused and
there actually is a diskette or CDROM in a drive, run volcheck to
update the volume manager. If the system remains confused, try
booting with the -r option to reconfigure devices.

No directory! Logging in with home=/
====================================

The login(1) program could not find the home directory listed in
the password file or NIS passwd map, so it deposited the user in
the root directory.

Check that the user's home directory is mounted and is owned by
and accessible to that user. Perhaps the automounter tried to
mount the home directory, but the NFS server did not respond
quicklyenough. Try listing the files in /home/username. If the
NFS server responds to this request, have the user log out and
log in again.

It is possible that the automounter daemon is not running. Run
the ps command to see if automountd is present. If not,run the
second command; if it appears to be wedged, run both these
commands:

# /etc/init.d/autofs stop # /etc/init.d/autofs start

When the automounter daemon is running, verify that the
/etc/auto_master file has a line like this:

/home  auto_home

Verify that the /etc/auto_home file has a line like this:

+auto_home

These entries depend on the NIS auto_home map.

It is also possible that the NFS server has not shared (exported)
this /home directory, or that the NFS daemons on the server have
disappeared.

For more information on NFS, see the NFS Administration Guide.

No message of desired type
==========================

An attempt was made to receive a message of a type that does not
exist on the specified message queue. See the msgop(2) man page
for details.

This indicates an error in the System V IPC message facility.
Generally the message queue is empty or devoid of the desired
message type, while IPC_NOWAIT is set.

The symbolic name for this error is ENOMSG, errno=35.

No recipients specified
=======================

This message comes from the mailx(1) command whenever a user
doesn't provide an address in the To: field.

See the message "Recipient names must be specified" for details.

No record locks available
=========================

No more record locks are available. The system lock table is
full.

The symbolic name for this error is ENOLCK, errno=46.

Perhaps a process called fcntl(2) with the F_SETLK or F_SETLKW
option, and the system maximum was exceeded. The system contains
several different locking subsystems, including fcntl,the NFS
lock daemon, and mail locking, all of which can produce this
error.

Try again later, when more locks might be available.

No route to host
================

An operational error occurred because there was no route to the
destination host, or because of status information returned by
intermediate gateways or switching nodes.

The returned status is not always sufficient to distinguish
between a host that is down and a network that isdown. See the
"Network is unreachable" message.

Check the network routers and switches to see if they are
disallowing these packet transfers. If they are allowing all
packet transfers, check network cabling and connections.

The symbolic name for thiserror is EHOSTUNREACH, errno=148.

No shell  Connection closed
===========================

A user has attempted to remote login to the system, and has a
valid account name and password, but the shell specified for
their account is not available on that system. For example, the
seventh field could request the GNUBourne-again shell /bin/bash,
which does not exist on standard Solaris distributions.

If you have a copy of the requested shell, become superuser and
install the missing shell on that system. Otherwise, change the
user's password file entry (perhaps only in the NIS+ or NIS
passwd map) to specify an available shell such as /bin/csh or
/bin/ksh.

No space left on device
=======================

While writing an ordinary file or creating a directory entry,
there was no free space left on the device. The disk, tape, or
diskette is full of data. Any data written to that device during
this condition will be lost.

Remove unneeded files from the hard disk or diskette until there
is space for all the data you are writing. It might be advisable
to move some directories onto another filesystem and create
symbolic links accordingly. When a tape is full, continue on
another one, use a higher density setting, or obtain a higher-
capacity tape.

To create multi-volume tapes or diskettes, use the pax(1) or
cpio(1) command; tar(1) is still limited to a single volume.

The symbolic name for this error is ENOSPC, errno=28.

No such device
==============

An attempt was made to apply an operation to an inappropriate
device, such as writing to a nonexistent device.

Look in the /devices directory to see why this device does not
exist, or why the program expects it to exist. The similar "No
such device or address" message tends to indicate I/O problems
with an existing device, whereas this message tends to indicate a
device that does not exist at all.

The symbolic name for this error is ENODEV, errno=19.

No such device or address
=========================

This can occur when a tape drive is off-line or when a device has
been powered off or removed from thesystem.

For tape drives, make sure the device is connected, powered on,
and toggled on-line (if applicable). For disk and CDROM drives,
check that the device is connected and powered on.

With all SCSI devices, ensure that the target switch or dial is
set to the number where the system originally mounted it. To
inform the system of a change to the target device number, reboot
using the -r (reconfigure) option.

This message results from I/O to a special file's subdevice that
either does not exist or that exists beyond the limit of the
device.

The symbolic name for this error is ENXIO, errno=6.

No such file or directory
=========================

The specified file or directory does not exist. Either the file
name or path name was entered incorrectly.

Check the file name and path name for correctness and try again.
If the specified file or directory is a symbolic link, it
probably points to a nonexistent file or directory.

The symbolic name for this error is ENOENT, errno=2.

no such map in server's domain
==============================

A user or an application tried to look up something using Network
Information Services (NIS), but NIS has no corresponding database
for this request.

Make sure the NIS map name is spelled correctly. To see a list of
nicknames for the various NIS maps, run the ypcat -x command. To
see a full list of the various NIS maps (databases), run the
ypwhich -m command. If the NIS service were not running on the
current machine, these commands would result in a "can't
communicate with ypbind" message.

No such process
===============

This process cannot be found. The process could have finished
execution and disappeared, or it might still be in thesystem
under a different numeric ID.

Use the ps(1) command tocheck that the process ID you're
supplying is correct.

No process corresponds to the specified process ID (PID), light-
weight process ID, or thread_t.

The symbolic name for this error is ESRCH, errno=3.

No such user as variable-- cron entries not created
===================================================

A file exists in /var/spool/cron/crontabs for the specified user,
but this user is not in /etc/passwd or the NIS passwd map. The
system cannot create cron entries for nonexistent users.

To eliminate this message at boot time, remove the cron file for
the nonexistent user, or rename it if the user's login name has
changed. If this is a valid user, create an appropriate password
entry for this name.

Not a directory
===============

A non-directory was specified where a directory is required, such
as in a path prefix or as an argument to the chdir(2) system
call.

Look at a listing of all the files in the current directory and
try again, specifying a directory instead of a file.

The symbolic name for this error is ENOTDIR, errno=20.

Not enough space
================

This message indicates that the system is running many large
applications simultaneously, and has run out ofswap space
(virtual memory). It could also indicate that applications failed
without freeing pages from the swap area. Swap space is an area
of disk set aside to store portions of applications and data not
immediately required in memory. Any data written during this
condition will probably be lost.

Reinstall or reconfigure the system to have more swap space. A
general rule of thumb is that swap space should be two to three
times as large as physical memory.  Alternatively, use mkfile(1M)
and swap(1M) to add more swap area. This example shows how to add
16 MB of virtual memory in the /usr/swap file (any filesystem
with enough free space would work):

# mkfile 16m /usr/swap # swap -a /usr/swap

To make this automatic at boot time, add the following line to
the /etc/vfstab file:

/usr/swap   -   -   swap   -   no  -

In calling the fork(2), exec(2), sbrk(2), or malloc(3C) routine,
a program asked for more memory than the system could supply.
This is not a temporary condition; swap space is a system
parameter.

The symbolic name for this error is ENOMEM, errno=12.

not found
=========

This message indicates that the Bourne shell could not find the
program name given as a command.

Check the form and spelling of the command line. If that looks
correct, echo $PATH to see if the user's search path is correct.
When communications are garbled, it is possible to unset a search
path to such an extent that only built-in shell commands are
available. Here is a command to reset a basic search path:

$ PATH=/usr/bin:/usr/ccs/bin:/usr/openwin/bin:.

If the search path looks correct, check the directory contents
along the search path to see if programs are missing or if
directories are not mounted.

NOTICE: /variable: out of inodes
================================

The filesystem specified after the first colon probably contains
many small files, exceeding the per-filesystem limit for inodes
(file information nodes).

If many small files were created unintentionally, removing them
will resolve the problem.

Otherwise, follow these steps to increase filesystem capacity for
small files. Make several backup copies of the filesystem on
different tapes (for safety), then bring the machine down to
single-user mode. Use the newfs(1M) command with the -i option to
increase inode density for this filesystem. Here is an example:

# newfs -i 1024 /dev/rdsk/partition

Finally, restore the filesystem from a backup tape. Note that
increasing the inode density slightly reduces total filesystem
capacity.

Not login shell
===============

This message results when a user triesto logout(1) from a shell
other than the one started at login time.

To quit a non-login shell, use the exit(1) command. Continue
doing so until you have logged out.

For more general information on the login shell, see the section
on customizing your work environment in the Solaris Advanced
User's Guide.

Not on system console
=====================

A user tried to login(1) to a system as the superuser (uid=0,
which is not necessarily root) from a terminal other than the
console.

Login to that system as a normal user, then run su(1M) to become
superuser. To allow superuser logins from any terminal, comment
out the CONSOLE line in /etc/default/login (this is not
recommended for security reasons).

Not owner
=========

Either an ordinary user tried to do something reserved for the
superuser, or the user tried to modify a file in a way restricted
to the file's owner or to the superuser.

Switch user to root and try again.

The symbolic name for this error is EPERM, errno=1.

Not supported
=============

This version of the system does not support the feature
requested, although future versions of the system might provide
support.

This is generally not a system message from the kernel, but an
error returned by an application. Contact the vendor or author of
the application for an update.

The symbolic name for this error is ENOTSUP, errno=48.

ok ==

This is the OpenBoot PROM monitor prompt. From this prompt, you
can boot the system (from disk, CDROM, or net), or you can use
the go command to continue where you left off.

If you suddenly see this prompt, look at the messages above it to
see if the system crashed. If no other messages appear, and you
just typed Stop-A or plugged in a new keyboard, type go to
continue. You might need to Refresh the window system from its
Workspace Menu.

Never invoke sync from the ok prompt without first running the
fsck(1M) command, especially if the filesystem has changed.

operation failed [error 185], unknown group error 0, variable
=============================================================

When you use admintool to add a user to a newly-created group,
admintool issues this error.

Apply patch 101384-05 to fix bug ID 1151837 and to provide a
workaround for bug ID 1153087.

Operation not applicable
========================

This error indicates that no system support exists for some
function that the application requested.

Ask the system vendor for an upgrade, or contact the vendoror
author of the application for an update.

This message indicates that no system support exists for an
operation. Many modules set this error when a programming
function is not yet implemented. If you are writing a program
that produces this message while calling a system library, try to
find and use an alternative library function. Future versions of
the system might support this operation; check system release
notes for further information.

The symbolic name for this error is ENOSYS, errno=89.

out of memory
=============

Hundreds of different programs can produce this message when the
system is running many large applications simultaneously. This
message usually means that the system has run out of swap space
(virtual memory).

See the message "Not enough space" for details. Any data written
during this condition will probably be lost.

PARTIALLY ALLOCATED INODE I=N  CLEAR?
=====================================

During phase 1, fsck(1M) found that the specified inode was
neither allocated nor unallocated. The reason is probably that
the system crashed in the middle of a sync(2) or write(2)
operation.

Should you answer yes to this question, "UNALLOCATED" messages
might result during phase 2, if any directory entries point to
this inode. If you are being careful, exit fsck(1M) and run
ncheck(1M) (specifying the inode number after the -i option) to
determine which file or directory is involved here. You might be
able restore this file or directory from another system. It is
also possiblethat fsck will copy this file to the lost+found
directory in a later phase.

For more information, see the chapter on checking filesystem
integrity in the System Administration Guide, Volume I.

passwd.org_dir: NIS+ servers unreachable
========================================

This is the first of three messages thatan NIS+ client prints
when it cannot locate an NIS+ server on the network.

See the message "hosts.org_dir: NIS+ servers unreachable" for
details.

Password does not decrypt secret key for unix.uid@variable
==========================================================

This message appears at login time when a user's password is not
identical to the user's keylogin network password. When a system
is running NIS+, the login program firstperforms UNIX
authentication, and then attempts a keylogin(1) for secure RPC
authentication.

To gain credentials for secure RPC, users can run keylogin (after
login) and type in their secret key. To stop this message from
appearing at login time, users can run the chkey -p command and
set their network password to bethe same as their NIS+ password.
If a user doesn't remember the network password, the system
administrator should delete and re-create the user's credentials
table entry so the user can establish a new network password with
chkey.

Permission denied
=================

An attempt was made to access a file in a way forbidden by the
protection system.

Check the ownership and protection mode of the file (with a long
listing from the ls-l command) to see who is allowed to access
the file. Then change the file or directory permissions as
needed.

The symbolic name for this error is EACCES, errno=13.

Please specify a recipient.
===========================

With mailtool, this message comes up in a dialog box whenever a
user tries to deliver a message with no address in the To: field.

See the message "Recipient names must be specified" for details.

Protocol not supported
======================

The requested networking protocol hasnot been configured into
the system, or no implementation for it exists. (A protocol is a
formal description of the messages to be exchanged and the rules
to be followed when systems exchange information.)

Verify that the protocol is in the /etc/inet/protocols file and
in the NIS protocols map, if applicable. If the protocol is not
listed, and you want to permit its use, configure the protocol as
documented or as required.

The symbolic name for this error is EPROTONOSUPPORT, errno=120.

Protocol wrong type for socket
==============================

This message indicates either application programming error, or
badly configured protocols.

Make sure that the /etc/protocols file corresponds number-for-
number with the NIS protocols map. It it does, ask the vendor or
author of the application for an update.

A protocol was specified that does not support the semantics of
the socket type requested. This amounts to a request for an
unsupported type of socket. Look at the source code that made
this socket request and check that it requested one of the types
specifiedin /usr/include/sys/socket.h.

The symbolic name for this error is EPROTOTYPE, errno=98.

Read error from network: Connection reset by peer
=================================================

This message appears when a user is remotely logged into a
machine that crashes or gets rebooted during the rlogin(1) or
rsh(1) session. Any data changes that were not saved are probably
lost. Sometimes this message appears only when the user types
something, even though the system went down hours before.

Try torlogin again, perhaps after waiting a few minutes for the
system to reboot.

Read-only file system
=====================

Files and directories on filesystems that are mounted read-only
cannot be changed.

If you only modify these files and directoriesoccasionally,
rlogin(1) to the servers from which the filesystems are mounted
and change the files or directories there. If you change these
files and directories frequently, mount(1M) the filesystems
read/write.

The symbolic name for this error is EROFS, errno=30.

rebooting...
============

This message appears on the console to indicate that the machine
is booting, either after the superuser issued a reboot command,
or after a system panic if the EEPROM's watchdog-reboot? variable
is set to true.

Allow the machine to boot itself. In case of a system panic, look
above this message for other indications of what went wrong.

Recipient names must be specified
=================================

Somebody sent mail without a valid recipient in the To: field, so
sendmail could not deliver the mail message. Using mail(1), the
recipient's address might have been specified using spaces or
non-alphanumeric characters. The mailtool(1)and mailx(1)
commands try to prevent this by issuing "Please specify a
recipient" or "No recipients specified" messages instead. If
there is at least one valid recipient, each invalid recipient
address will generate a "User unknown" message.

Look in the sender's dead.letter file for the automatically saved
message, andhave the originator send it again, this time
specifying a recipient.

For more information about sendmail, see the Mail Administration
Guide.

Reset tty pgrp from N to N
==========================

The C shell sometimes issues this message when it clears away the
window process group after the user exits the window system. This
can happen when the window system doesn't clean up after itself.

Proceed with your work. This message is purely informational.

Resource temporarily unavailable
================================

This indicates that the fork(2) system call failed because the
system's process table is full, or that a system call failed
because of insufficient memory or swap space. It is also possible
that a user is not allowed to create anymore processes.

Simply waiting often gives the system time to free resources.
However if this message occurs often on a system, reconfigure the
kernel and allow more processes.  To increase the size of the
process table in Solaris 2.x, increase the value of maxusers in
the /etc/system file. The default maxusers value is the amount of
main memory in MB, minus 2.

If one user is not allowed to create any more processes, that
user has probably exceeded the memorysize limit; see the limit(1)
man page for details.

The symbolic name for this error is EAGAIN, errno=11.

Result too large
================

This is a programming error or a data input error.

Ask the program's author to fix this condition.

This indicates an attempt to evaluate a mathematical programming
function at a point where its value would overflow or underflow.
The value of a programming function in the math package (3M) is
not representable within machine precision. This could occur
after floating point overflow or underflow (either single or
double precision), or after total loss of numeric significance in
Bessel functions.

Note that this message can indicate "Result too small" in the
case of floating pointunderflow.

To help pinpoint a program's math errors, use the matherr(3M)
facility.

The symbolic name for this error is ERANGE, errno=34.

rmdir: variable: Directory not empty
====================================

The rmdir(1) command can remove empty directories, only. The
directory whose name appears after the first colon in the message
still contains some files or directories.

Use rm(1) instead of rmdir. To remove this directory and
everything underneath it, use the rm -ir command to recursively
descend the directory, being asked if you want to delete each
element. To remove the directory and all its contents without
being asked for approval, use the rm -r command.

ROOT LOGIN /dev/console
=======================

This syslog message indicates that someone has logged in as root
on the system console.

If you have just logged in as root, don't worry. If this is not
you, consider the possibility of a security breach. The best
site-wide policy is for all system administrators to su instead
oflogging in as root.

ROOT LOGIN /dev/pts/N FROM variable
===================================

This syslog message indicates that someone has remote logged in
as root on a pseudo-terminal from the system specified after the
FROM keyword.

For security reasons, it is a bad idea to allow root logins from
anywhere besides the console. To restrict superuser logins to the
console, remove the comment from the CONSOLE line in
/etc/default/login.

rx framing error
================

Usually this error indicates a hardware problem.

Check the Ethernet cabling and connectors to locate a problem.

A framing error occurs when the Ethernet I/O driver receives a
non-integral unit of octets, such as 63 bytes and then 3 bits.
(Ethernet specifies the use of octets.) Framing errors are caused
by corruption of the starting or ending frame delimiters. These
can be corrupted by some violation of the encoding scheme.

Framing errors are a subset of CRC errors, which are usually
caused by anomalies on the physical media.An "alignment/framing
error" is a type of CRC error where octet boundaries do not line
up.

SCSI bus DATA IN phase parity error
===================================

The most common cause of this problem is unapproved hardware.
Some SCSI devices for thePC market do not meet the high I/O
speed requirements for the UNIX market.  Other possible causes of
this problem are improper cabling or termination, and power
fluctuations. Data corruption is possible but unlikely to occur,
because this parity error prevents data transfer.

Check that all SCSI devices on the bus are Sun approved hardware.
Then verify that all cables are no longer than six meters, total,
and that all SCSI connections are properly terminated. If power
fluctuations are occuring, invest in an uninterruptible power
supply.

SCSI transport failed: reason 'reset'
=====================================

This message indicates that the system sent data over the SCSI
bus, but the data never reached its destination because of a SCSI
bus reset. The most common cause of this condition is conflicting
SCSI targets.짣ata corruption is possible but unlikely to
occur, because this failure prevents data transfer.

Verify that all cables are no longer than six meters, total, and
that all SCSI connections are properly terminated. If power
surges are a problem, acquire a surge suppressor or
uninterruptible power supply.

A machine's internal disk drive is usually SCSI target 3. Make
sure that external and secondary disk drives are targeted to 1,
2, or 0, and do not conflict with each other.  Also make sure
that tape drives are targeted to 4 or 5, and CD drives to 6,
avoiding any conflict with each other or with disk drives. If the
targeting of the internal disk drive is in question, power off
the machine, remove all external drives, turn the power on, and
from the PROM monitor run the probe-scsi-all or probe-scsi
command.

If SCSI device targeting is acceptable, memory configuration
could be the problem, especially for machines with the sun4c
architecture. Ensure that high-capacity memory chips (such as 4MB
SIMMs) are in lower banks, while lower-capacity memory chips
(such as 1MB SIMMs) are in the upper banks.

Note that SPARC systems do not always support third party CDROM
drives, and might generate a similar "unknown vendor" error
message. Check with the CDROM vendor for specific configuration
requirements.

Some third party disk drives have a read-ahead cache that
interferes with Solaris device drivers. Make sure that any
existing read-ahead cache facility is turned off.

?For more information on SCSI targets, see the section on
device naming conventions in the Solaris 1.x to Solaris 2.x
Transition Guide. If you are using the AnswerBook, "scsi targets"
is a good search string.

Segmentation Fault
==================

Segmentation faults usually result from programming error. This
message is usually accompanied by a core dump, except on read-
only filesystems.

To see which program produced a core file, run either the file(1)
command or the adb (1) command. The following examples show the
output of the file and adb commands on a core file from the
dtmail program.

$ file core core: ELF 32-bit MSB core file SPARC Version 1, from
`dtmail'

$ adb core core file = core -- program `dtmail' SIGSEGV  11:
segmentation violation ^D      (use Control-d to quit the adb
rogram)

Ask the vendor or author of this program for a debugged version.

A process has received a signal indicating that it attempted to
access an area of memory that is protected or that does not
exist. The two most common causes of segmentation faults are
attempting to dereference a null pointer or indexing past the
bounds of an array.

sendmail[N]: NOQUEUE: SYSERR: net hang reading from variable
============================================================

This is a sendmail message that appears on the console and in the
log file /var/adm/messages. If this message occurs once for a
particular user, it is possible that a mail message from this
user ends with a partial line (having no terminating newline
character). If this message appears frequently or at busy times,
especially along with other networking errors, it could indicate
network problems.

Check the user's mail spool file to see if a message ends without
a newline character.  If so, talk with the user and determine how
to prevent the problem from occurring again. If these messages
are the result of network problems, you could try moving the mail
spool directory to another machine with a faster network
interface.

During the SMTP receipt of DATA phase, a message-terminating
period on a line of its own never arrived, so sendmail timed out
and produced this error.

setmnt: Cannot open /etc/mnttab for writing
===========================================

The system is having problems writing to /etc/mnttab. It is
possible that the filesystem containing /etc is mounted read-
only, or is not mounted at all.

Check that this file exists and is writable by root. If so,
ensure that the /etc filesystem has been mounted, and is mounted
read-write rather than read-only.

share_nfs: /home: Operation not applicable
==========================================

This message usually indicates that the system has a local
filesystem mounted on /home, which is where the automounter
usually mounts users' home directories.

When a systemis running the automounter, do not mount local
filesystems on the /home directory. Mount them on another
directory, such as /disk2, which on most systems you will have to
create.You could also change the automounter auto_home entry,
but that is a more difficult solution.

Soft error rate (N%) during writing was too high
================================================

This message from the SCSI tape drive appears when Exabyteor DAT
tapes generate too many soft (recoverable) errors. It is followed
bythe advisory "Please, replace tape cartridge" message. Soft
errors are an indication that hard errors could soon occur,
causing data corruption.

First clean the tape head witha cleaning tape as recommended by
the manufacturer. If that doesn't work, replace the tape
cartridge. You might need to replace the tape drive if the
problem still occurs with new tape cartridges.

Soft error rate (retries = N) during writing was too high
=========================================================

This message from the SCSI tape drive appears when Archive tapes
generate too many soft (recoverable) errors. It is followed by
the advisory "Periodic head cleaning required and/or replace tape
cartridge" message. Soft errors are an indication that hard
errors couldsoon occur, causing data corruption.

First clean the tape head with a cleaning tape as recommended by
the manufacturer. If that doesn't work, replace the tape
cartridge. Youmight need to replace the tape drive if the
problem still occurs with new tape cartridges.

Stale NFS file handle
=====================

A file or directory that was opened by an NFS client was either
removed or replaced on the server.

If you were editing this file, write it to a local filesystem
instead. Try remounting the filesystem on top of itself or
shutting down any client processes that refer to stale file
handles. If neither of these solutions works, reboot the system.

The original vnode isno longer valid. The only way to get rid of
this error is to force the NFS server and client to renegotiate
file handles.

The symbolic name for this error is ESTALE, errno=151.

statd: cannot talk to statd at variable
=======================================

This message comes from the NFS status monitor daemon statd,
which provides crash recovery services for the NFS lock daemon
lockd. The message indicates that statd has left old references
in the /var/statmon/sm and /var/statmon/sm.bak directories. After
a user has removed or modified a host in the hosts database,
statd might not properly purge files in these directories, which
results in its trying to communicate with a nonexistent host.

Remove the file named variable (where variable is the hostname)
from both the /var/statmon/sm and /var/statmon/sm.bak
directories. Then kill the statd daemon and restart it. If that
doesn't get rid of the message, kill and restart lockd as well.
If that doesn't work, reboot the machine at your convenience.

stty: TCGETS: Operation not supported on socket
===============================================

This message results when a user tries to remote copy with rcp(1)
or remote shell with rsh(1) from one machine to another, but has
an stty(1) command in the remote

The solution is to move the stty command to the user's .login (or
equivalent) file.  Alternatively, execute the stty command in
.cshrc only when the shell is interactive.  Here is a test to do
just that:

if ($?prompt) stty ...

The rcp andrsh commands make a connection using sockets, which
do not support stty's TCGETS ioctl.

su: No shell
============

This message indicates that someone changed the default login
shell for root to a program missing from the system. For example,
the final colon-separated field in /etc/passwd could have been
changed from /sbin/sh to/usr/bin/bash, which does not exist in
that location. Possibly an extra space was appended at the end of
line. The outcome is that you cannot login as root or switch user
to root, and so cannot directly fix this problem.

The only solution is to rebootthe system from another source,
then edit the password file to correct this problem. Invoke
sync(1M) several times, then halt the machine by typing Stop-A or
by pressing the reset button. Reboot single-user from CDROM, the
net, or diskette, such as by typing boot cdrom -s at the ok
prompt.

After the system comes up and gives you a # prompt, mount the
device corresponding to the original / partition somewhere, such
as with a mount(1M) command similar to the one below. Then run an
editor on the newly-mounted system password file (use ed(1) if
terminal support is lacking):

# mount /dev/dsk/c0t3d0s0 /mnt # ed /mnt/etc/passwd

Use the editor to change the password file's root entry to call
an existing shell, such as /usr/bin/csh or /usr/bin/ksh.

To keep the "No shell" problem from happening, habitually use
admintool or /usr/ucb/vipw to edit the password file. These tools
make it difficult to change password entries in ways that make
the system unusable.

su: 'su root' failed for variable on /dev/pts/N
===============================================

The user specified after "for" tried to become superuser, but
typed the wrong password.

If the user is supposed to know the root password, wait to see if
the correct password is supplied. If the user is not supposed to
know the root password, ask why he or she is attempting to become
superuser.

su: 'su root' succeeded for variable on /dev/pts/N
==================================================

The user specified after "for" just became superuser by typing
the root password.

If the user is supposed to know the root password, this message
is purely informational. If the user is not supposed to know the
root password, change this password immediately and ask how the
user learned it.

syncing file systems...
=======================

This indicates that the kernel is updating the super-blocks
before taking the system down, to ensure filesystem integrity.
This message appears after a halt(1M) or reboot (1M) command. It
can also appear after a system panic, in which case the system
might contain corrupted data.

If you just halted or rebooted the machine, don't worry-- this
message is normal. In case of a system panic, look up the panic
messages that appear above this one. Your system vendor might be
able to help diagnose the problem. So that you can describe the
panic to the vendor, either leave your system in its panicked
state or be sure that you can reproduce the problem.

Numbers that sometimes display after the three dots in the
message show the count of dirty pages that are being written out.
Numbers in brackets show an estimate of the number of busy
buffers in the system.

syslog service starting.
========================

During system reboot, this message might appear and theboot
seems to hang. After starting syslogd(1M) service, the system
runs /etc/rc2.d/S75cron, which in turn calls ps(1). Sometimes
after an abrupt system crash /dev/bd.off becomes a link to
nowhere, causing the ps command to hang indefinitely.

Reboot single user (for example with boot -s) and run ls -l
/dev/bd* to see if this is the problem. If so, remove
/dev/bd.off, then run bdconfig off or reboot with the -r
(reconfigure) option.

This is the most commonly reported situation that causes ps to
hang.

tar: /dev/rmt/0: No such file or directory
==========================================

The default tape device /dev/rmt/0, or possibly the device
specified by the TAPE environment variable, is not currently
connected to the system, is not configured, or its hardware
symbolic link is broken.

List the files in the /dev/rmt directory to see which tape
devices are currently configured. If none are configured, ensure
that a tape device is correctly attached to the system, and
reboot with the -r option to reconfigure devices.

If tape devices other than /dev/rmt/0 are configured, you could
specify one of them after the -f option of tar(1).

tar: directory checksum error
=============================

This error message from tar(1) indicates that the checksum of the
directory and the files it has read from tape does not match the
checksum advertised in the header block. Usually this indicates
the wrong blocking factor, although it could indicate corrupt
data on tape.

To resolve this problem, make certain that the blocking factor
you specify on the command line (after -b) matches the blocking
factor originally specified. If in doubt, leave out the block
size and let tar determine it automatically. If that doesn't
help, tape data could be corrupted.

tar: tape write error
=====================

A physical write error has occurred on the tar(1) output file,
which is usually a tape, although it could be a diskette or disk
file. Look on the system console, where the device driver should
provide the actual error condition. This might be a write-
protected tape, a physical I/O error, an end-of-tape condition,
or a File too large limitation.

In the case of write-protectedtapes, enable the write switch.
For physical I/O errors, the best course of action is to replace
the tape with a new one. For end-of-tape conditions, try using a
higher density if the device supports one, or use cpio(1) or pax
(1) for their multi-volume support., When encountering File too
large limitations, use the parent shell'slimit(1) or ulimit
facility to increase the maximum file size.

For more information on tar tapes, see the section on copying UFS
files in the System Administration Guide,Volume I.

Text is lost because the maximum edit log size has been exceeded.
=================================================================

This message appears at the beginning of a cmdtool(1) session
after 100,000 characters have gone by in the scrolling window.
Clicking on the top rectangle of the scrollbar might display this
message. No data were lost, but the user cannot scroll back
before this wraparound point.

To increase the maximum size of the Command Tool log file, use
cmdtool with the-M option, specifying more than 100,000 bytes.

THE FOLLOWING FILE SYSTEM(S) HAD AN UNEXPECTED INCONSISTENCY:
============================================================

At boot time the /etc/rcS script runs the fsck(1M) command to
check the integrity of filesystems marked "fsck" in /etc/vfstab.
If fsck cannot repair a filesystem automatically, it interrupts
the boot procedure and produces this message. When fsck gets into
this state, it cannot repair filesystems without losing one or
more files, so it wants to defer this responsibility to you, the
administrator. Data corruption has probably already occurred.

First run fsck -n on the filesystem, to see how many and what
type of problems exist.  Then run fsck again to repair the
filesystem. If you have a backup of the filesystem, you can
generally answer "y" to all the fsck questions. It's a good idea
to keep a record of all problematic files and inode numbers for
later reference. To run fsck yourself, specify options as
recommended by the boot script. For example:

# fsck /dev/rdsk/c0t4d0s0

Usually, files lost during fsck repair were created just before a
crash or power outage, and cannot be recovered. If important
files are lost, you can recover them from backup tapes.

If you don't havea backup, ask an expert to run fsck for you.

For more information, see the sectionon checking filesystem
integrity in the System Administration Guide, Volume I.

The SCSI bus is hung. Perhaps an external device is turned off.
===============================================================

This message appears near the beginning of rebooting, immediately
after a "Boot device: ..." message, and then the system hangs.
The problem is conflicting SCSI targets for a non-boot device.
Having an external device turned off is unlikely to cause this
problem.

See the message "Boot device:
/iommu/sbus/variable/variable/sd@3,0" for a solution.

For more information, see the section on halting and booting in
the System Administration Guide, Volume I.

THE SYSTEM IS BEING SHUT DOWN NOW !!!
=====================================

This message means the system is going down immediately and it's
too late to save any changes.

This message is often preceded by messages telling you that the
system is going down in 15 minutes, 10 minutes, and so on. When
you see these initial broadcast shutdown messages, save all your
work, send any e-mail you're working on, and close your files.
Fortunately vi sessions are automatically saved for later
recovery, but many otherapplications have no crash protection
mechanism. Data loss is likely.

For more information on shutting down the system, see the System
Administration Guide, Volume I. If you are using the AnswerBook,
"halting the system" is a good search string.

The system will be shut down in N minutes
=========================================

Thismessage from the system shutdown(1M) script informs you that
the superuser is taking down the system.

Save all changes now or your work will be lost. Write out any
files you were changing, send any e-mail messages you were
composing, and close your files.

For more information on shutting down the system, see the System
Administration Guide, Volume I. If you are using the AnswerBook,
"halting the system" is a good search string.

This mail file has been changed by another mail reader.
=======================================================

This message appears in a pop-up dialog box whenever you start
mailtool(1) while another mail reader has the inbox locked. A
question follows: "Do you wish to ask that mail reader to save
the changes?" You are given three choices.

If you choose "Save Changes" mailtool will request the other mail
reader to relinquish its lock and write out any changes it has
made to your inbox. If you choose "Ignore" mailtool will read
your inbox without locking it. If you choose "Cancel" mailtool
will exit.

Timeout waiting for ARP/RARP packet
===================================

This problem can occur while booting from the net, and indicates
a network connection problem.

Make sure the Ethernet cable is connected to the network. Check
that this system has an entry in the NIS ethers map or locally on
the boot server. Then check the IP address of the server and the
client to make sure they are on the same subnet. Local /etc/hosts
files must agree with each other and withthe NIS hosts map.

If those are not causing the problem, go to the system's PROM
monitor ok prompt and run test net to test the network
connection. (On older PROM monitors, use test-net instead.) If
the network test fails, check the Ethernet port, card, fuse, and
cable, replacing them if necessary. Also check the twisted pair
port to make sure it is patched to the correct subnet.

For more information on packets, see SPARC: Installing Solaris
Software. If you are using the AnswerBook, "ARP/RARP" isa good
search string.

Too many links
==============

An attempt was made to create more than the maximum number of
hard links (LINK_MAX, by default 32767) to a file. Because each
subdirectory is a link to its parent directory, the same error
results from trying to create too many subdirectories.

Check to see why there are so many links to the same file. To get
more than the maximum number of hard links, use symbolic links
instead.

The symbolic name for this error is EMLINK, errno=31.

Too many open files
===================

A process has too many files open at once. The system imposes a
per-process soft limit on open files, OPEN_MAX (usually 64),
which can be increased, and a per-process hard limit (usually
1024), which cannot be increased.

You can control the soft limit from the shell. In the C shell,
use the limit command to increase the number of descriptors. In
the Bourne or Korn shells, use the ulimit command with the -n
option to increase the number of file descriptors.

If the window system refuses to start new applications because of
this error, increase the open file limit in your login shell
before starting the window system.

The symbolic name for this error is EMFILE, errno=24.

umount: warning: /variable not in mnttab
========================================

This message results when the superuser attempts to unmount a
filesystem that is not mounted. Note that subdirectories of
filesystems,such as /var, cannot be unmounted.

Run the mount(1M) or df(1M) command to see what filesystems are
mounted. If you really want to unmount one of them, specify the
existing mount point.

Unable to install/attach driver 'variable'
==========================================

These messages appear in /var/adm/messages at boot time, when the
system tries to load drivers for devices the machine does not
have.

Despite the alarmist tone, this message is intended as purely
informational. You probably don't want all these device drivers,
because they make your system kernel larger, requiring more
memory.

undefined control
=================

This message, prefaced by the file name and line number involved,
is from the C preprocessor /usr/ccs/lib/cpp, and indicates a line
starting with a sharp (#) but not followed by a valid keyword
such as define or include.

A piece of software might be running the C preprocessor on an
initialization file that you thought was interpreted by a shell.
In most shells, the sharp (#) indicates a comment. The C
preprocessor considers comments to be anythingbetween /* and */
delimiters.

Unmatched `
===========

This message from the C shell csh(1) indicates that a user typed
a command containing a backquote symbol (`) without a closeing
backquote. Similar messages result from an unmatched single quote
(') or an unmatched double quote ("). Other shells generally give
a continuation prompt when a command line contains an unmatched
quote symbol.

Correct the command line and try again. To continue typing on
another line, give the C shell a backslash right before the
newline.

UNREF FILE I=i OWNER=o MODE=m SIZE=s MTIME=t
============================================= CLEAR?
======

During phase 4, fsck(1M) discovered that the specified file was
orphaned because the inode had no record of its pathname. In
other words, the file was not connected into any directory.

Answer yes to reconnect the file into the lost+found directory.
Then contact the file's owner to ask whether they want it back,
and where they want you to place it.

For more information, see the chapter on checking filesystem
integrity in the System Administration Guide, Volume I.

Use "logout" to logout.
=======================

This C shell message might come as a surprise to Bourne or Korn
shell users accustomed to logging out with a Control-d.

When ignoreeof is set, the C shell requires users to logout by
typing logout or exit.  Write any modified files to disk before
exiting.

/usr/openwin/bin/xinit: connection to X server lost
===================================================

This means that the xinit(1) program, which sets up X11 resources
and starts a window manager, failed to locate the X server
process. Perhaps the user interrupted window system startup, or
exited abnormally from OpenWindows (for example, by killing
processes or by rebooting). It is possible that the X server
crashed. Data loss is possible in some cases. Depending on
process timing, this message might be normal when OpenWindows
exits during a system reboot.

The only solution is to exit and restart OpenWindows. You do not
need to reboot the system unless it hangs and fails to give you a
console prompt. To exit OpenWindows, select Workspace->Exit. To
restart OpenWindows, type openwin at the system prompt.

Value too large for defined data type
=====================================

The user ID or group ID of an IPC object or file system object
was too large to be stored in an appropriate member of the
caller-provided structure.

Run the application on a newer system, or ask the program's
author to fix this condition.

This error occurs only on systems that support a larger range of
user or group ID values than a declared member structure can
support. This condition usually occurs because the IPC or file
system object resides on a remote machine with a larger value of
type uid_t, off_t, or gid_t than that of the local system.

The symbolic name for this error is EOVERFLOW, errno=79.

WARNING: Clock gained N days-- CHECK AND RESET THE DATE!
========================================================

Each workstation contains an internal clock powered by a
rechargeable battery. After the system is halted and turned off,
the internal clock continues to keep time. When the system is
powered on and reboots, the system notices that the internal
clock has gained time since the workstation was halted.

In most cases, especially if the power has been off for less than
a month, the internal clock keeps the correct time, and you do
not have to reset the date. Use the date(1) command to check the
date andtime on your system. If the date or time is wrong,
become superuser and use the date(1) command to reset them.

WARNING: No network locking on variable: contact adminto install server change
===============================================================================

The Solaris 2.x mount(1M) command issues this message whenever it
mounts a filesystem that doesn't have NFS locking, such as a
standard SunOS 4.1.x exported filesytem. Data loss is possible in
applications that depend on locking.

On the remote SunOS 4.1.x system, install the appropriate
rpc.lockd jumbo patch to implement NFS locking. For SunOS 4.1.4,
install patch #102264; for SunOS 4.1.3, install patch #100075;
for earlier 4.1 releases, install patch #101817.

WARNING: processorlevel 4 interrupt not serviced
=================================================

This message is basically a diagnostic from the SCSI driver.
Especially on machineswith the sun4c architecture, it can appear
on the console every 10 minutes or so.

To reduce the frequency of this message, add this line near the
bottom of the /etc/system file and reboot:

set esp:esp_use_poll_loop=0

You might also see this message repeatedly after manually
removing a CD when it was busy. Don't do this! To get the system
back to normal, reboot the system with the -r (reconfigure)
option.

WARNING: /tmp: File system full, swap space limit exceeded
==========================================================

The system swap area (virtual memory) has filled up. You needto
reduce swap space consumption by killing some processes or
possibly by rebooting the system.

See the message "Not enough space" for information about
increasingswap space.

WARNING: TOD clock not initialized-- CHECK AND RESET THE DATE!
========================================================-=====

This message indicates that the Time Of Day (TOD) clock reads
zero, so its time is the beginning of the UNIX epoch: midnight 31
December 1969. On a brand-new system, the manufacturer might have
neglected to initialize the system clock. On older systems it is
more likely that the rechargeable battery has run out and
requires replacement.

First replace the batteryaccording to the manufacturer's
instructions. Then become superuser and use the date(1) command
to set the time and date. On SPARC systems the clock is powered
by the same battery as the NVRAM, so a dead battery also causes
loss of the machine's Ethernet address and host ID, which are
more serious problems for networked systems.

WARNING:Unable to repair the / filesystem. Run fsck
====================================================

This message comes at boot time from the /etc/rcS script whenever
it gets a bad return code from fsck(1) after checking a
filesystem. The message recommends an fsck command line, and
instructs you to exit the shell when done to continue booting.
Then the script places the system in single-user mode so fsck can
be run effectively.

See "/dev/rdsk/variable: UNEXPECTED INCONSISTENCY" for
information about repairing UFS filesystems.

See "THE FOLLOWING FILE SYSTEM(S) HAD AN UNEXPECTED
INCONSISTENCY" for information about repairing non-UFS
filesystems.

Watchdog Reset
==============

This fatal error usually indicates some kind of hardware problem.
Data corruption on the system is possible.

Look for some other message that might help diagnose the problem.
By itself, a watchdog reset doesn't provide enough information;
because traps are disabled, all information has been lost. If all
that appears on the console is an ok prompt, issue the PROM
command below to view the final messages that occurred just
before system failure:

ok f8002010 wector p

Yes, that word iswector, not vector.

The result is a display of messages similar to those produced by
the dmesg(1M) command. These messages can be useful in finding
the cause of system failure.

This message doesn't come from the kernel, but from the OpenBoot
PROM monitor, a piece of Forth software that gives you the ok
prompt before you boot UNIX. If the CPU detects a trap when traps
are disabled (an unrecoverable error), it signals a watchdog. The
OpenBoot PROM monitor detects the watchdog, issues this message,
and brings down the system.

Watchdog Reset, Rebooting.
==========================

See the message "Watchdog Reset" for details. This rebooting
message occurs under the same conditions, but when the EEPROM's
watchdog-reboot? variable is set to true, causing the machine to
automatically reboot itself. Data corruption on the system is
possible.

Who are you?
============

Many networking programs can print this message, including
from(1B), lpr(1B), lprm(1B), mailx(1), rdist(1), sendmail(1M),
talk(1), and rsh(1). The command prints this message when it
cannot locate a password file entry for the current user.  This
might occur if a user logged in just before the superuser deleted
that user's password entry, or if the network naming service
fails for a user who has no entry in the local password file.

If a user's password file entry was accidentally deleted, restore
it from backups or from another password file. If a user's login
name or user ID was changed, ask that user to logout and login
again. If the network naming service failed, check the NIS
server(s) and repair or reboot as necessary.

There is a known problem (bug 1138025) with starting hundreds of
rsh processes on another machine. This message appears because
rsh hangs while binding to a reserved port, and responds too
slowly to interact with the network naming service.

Window Underflow
================

This message often occurs at boot time, sometimes along with a
"Watchdog Reset" error. It comes from the OpenBoot PROM monitor,
which was passed a processor trap from the hardware. This error
indicates that some programtried to access a SPARC register
window that wasn't accessible from the processor.

On some system architectures, specifically sun4c, the problem
could be that different capacity memory chips are mixed together.
Someone might have placed 1MB SIMMs in the same bank with 4MB
SIMMs. If this is so, rearrange the memory chips. Make sure to
put higher-capacity SIMMs in the first bank(s), and lower-
capacity SIMMs inthe remaining bank(s); never mix different
capacity SIMMs in the same bank.

The problem could also be that cache memory on the motherboard
has gone bad and needs replacement. If main memory is installed
correctly, try swapping the motherboard.

The best way to isolate the problem is to look at the %pc
register to see where it got its arguments from, and why the
arguments were bad. If you can reproduce the condition causing
this message, your system vendor might be able to help diagnose
the problem.

X connection to variable:0.0 broken (explicit kill or server shutdown).
=======================================================================

This means that the client has lost its connection to the X
server. The "0.0" represents the display device, which is usually
the console. This message can appear when a user is running an X
application on a remote system with the DISPLAY set back to the
original system and the remote system's X server disappears,
perhaps because someone exited X windows orrebooted the machine.
It sometimes appears locally when a user exits the window system.
Dataloss is possible if applications were killed before saving
files.

Try to run the application again in a few minutes after the
system has rebooted and the window system is running.

xinit: not found
================

OpenWindows was probably not installed properly, and the
openwin(1) program could not find xinit(1) to start up the X
windows system. If the user is running another version of X
windows, such as the MIT X11 distribution, the startx program
serves the same function as xinit.

Check the PATH environment variable to make sure it contains the
appropriate X windows install directory. Verify that xinit is in
this directory as an executable program.

XIO: fatal IO error 32 (Broken pipe) on X server "variable:0.0"
===============================================================

This means that I/O with the X server has been broken. The "0.0"
represents the display device, which is usually the console. This
message can appear when a user is running Display PostScript
applications and the X server disappears or the client is shut
down. Data loss is possible if applications disappeared before
saving files.

Try to run the application again in a few minutes after the
system has rebooted and the window system is running.

Xlib: Client is not authorized to connect to Server
===================================================

See the message "Xlib: connection to ... refused by server" for
details.

Xlib: connection to "variable:0.0" refused by server
====================================================

This message is immediately followed by the "Xlib: Client is not
authorized to connect to Server" message. These messages indicate
that an X windows application tried to run on the X server
specified inside double quotes, which did not allow the request.
The "0.0" represents the display device, which is usually the
console. If no server name appears, the superuser probably tried
to run an X application on the current machine in an X session
that was owned by somebody else.

To allow this client to connect to the X server, run xhost
+clientname on the X server system. Only the owner of the current
X session (who is not necessarily the superuser) isallowed to
run the xhost command. If somebody else is running X windows on
the server, ask them to log out and then start your own X session
on that server; remote X connections are usually allowed for the
same user ID.

xterm: fatal IO error 32 (Broken Pipe) or KillClient on X server
variable:0.0"
=============

This means that xterm(1) has lost its connection to the X server.
The "0.0" represents the display device, which is usually the
console. This message can appear when a user is running xterm and
the X server disappears or the client gets shut down. Data loss
is possible if applications were killed before saving files.

Try to run the terminal emulator again in a few minutes after the
system has rebooted and the window system is running.

XView warning: Cannot load font set 'variable' (Font Package)
=============================================================

This message from the XView library warns that a requested font
is not installed on the X server. Often multiple warnings appear
about the same font. The set of available fonts can vary from
release to release.

To see which fonts are available on the X server, run the
xlsfonts(1) program. Then specify another font name that you see
in the output of xlsfonts. Sometimes it is possible to locate a
similar font from a different vendor.

There are two packages of X windowsfonts: the common but not
required fonts (SUNWxwcft), and the optional fonts (SUNWxwoft).
Run pkginfo(1) to see if both these packages are installed, and
add them to the system as you wish.

ypbind[N]: NIS server for domain "variable" OK
==============================================

This message appears after an "NIS server not responding" message
to indicate that ypbind(1M is able to communicate with an NIS
server again.

Proceed with your work. This message is purely informational.

ypbind[N]: NIS server not responding for domain "variable"; still trying
========================================================================

This means that the NIS client daemon ypbind(1M) cannot
communicate with an NIS server for the specified domain. This
message appears when a workstation running the NIS naming service
has become disconnected from the network, or when NIS servers are
down or extremely slow to respond.

If other NIS clients are behaving normally, check the Ethernet
cabling on the workstation that is getting this message. On SPARC
machines, disconnected network cabling also produces a series of
"no carrier" messages. On x86 machines, the above message might
be your only indication that network cabling is disconnected.

If many NIS clients on the network are giving this message, go to
the NIS server in question and reboot or repair as necessary. To
locate the NIS server for a domain, run the ypwhich(1) command.
When the server machine comes back in operation, NIS clients give
an "NIS server for domain OK" message.

For more information about ypbind, see the section on
administering secure NFS in the NFS Administration Guide.

ypwhich: can't communicate with ypbind
======================================

This message from the ypwhich(1) command indicates that the NIS
binder process ypbind(1M) is not running on the local machine.

If the system is not configured to use NIS, this message is
normal and expected.  Configure the system to use NIS if
necessary.

If the system is configured to use NIS, but the ypbind process is
not running, invoke the following command to start it up:

# /usr/lib/netsvc/yp/ypbind -broadcast

zsN: silo overflow
==================

This message means that the Zilog 8530 character input silo (or
serial portFIFO) overflowed before it could be serviced. The
zs(4S) driver, which talks to a Zilog Z8530 chip, is reporting
that the FIFO (holding about two characters) has been overrun.
The number after zs shows which serial port experienced an
overflow:

zs0 - tty serial port 0 (/dev/ttya) zs1 - tty serial port 1
(/dev/ttyb) zs2 - keyboard port (/dev/kbd) zs3 - mouse port
(/dev/mouse)

Silo overflows indicate that data in the respective serial port
FIFO has been lost.  However, consequences of silo overflows
might be negligible if the overflows occur infrequently, if data
loss is not catastrophic, or if data can be recovered or
reproduced.  For example, although a silo overflow on the mouse
driver (zs3) indicates that the system could not process mouse
events quickly enough, the user can perform mouse motions again.
Similarly, lost data from a silo overflow on a serial port with a
modem connection transferring data using uucp(1C) will be
recovered when uucp discovers the loss of data and requests
retransmission of the corrupted packet.

Frequent silo overflow messages can indicate a zs hardware FIFO
problem, a serial driver software problem, or abnormal data or
system activity. For example, the system ignores interrupts
during system panics, so mouse and keyboard activity result in
silo overflows.

If the serial ports experiencing silo overflows are not being
used, a silo overflow could indicate the onset of a hardware
problem.

Another type of silo overflow is one that occurs during reboot
when an HDLC line is connected to any of the terminal ports. For
example, an X.25 network could be sending frames before the
kernel has been told to expect them. Such overflow messages can
be ignored.
(*.95.187.237)