This appendix explains the SUPER-UX system daemon messages for each daemon. These messages are classified into the following six levels:
Indicates that an error requiring prompt action (for example, reorganization of a system database) was detected. Take the action indicated by the daemon message.
Indicates that an error requiring prompt action (for example, hardware device error) was detected. Take the action indicated by the daemon message.
Indicates that a daemon detected an error. Take the action indicated by the daemon message.
Warning message from a daemon. A warning message is displayed when a temporary error occurs or when an error occurs in a limited function. Take the action indicated by the daemon message.
Message for a notice event that occurs in a daemon. A notice message is displayed to call the system administrator's attention to the event that occurred. Take the action indicated by the daemon message.
Message directed to the system administrator
For each level, system daemon messages are explained in alphabetical order.
| Home |
|---|
The output destination for aad error messages is syslog.
Refer to the SUPER-UX Automatic Operation System Administrator's Guide for details.
The output destination for aocd error messages is syslog.
Refer to the SUPER-UX Automatic Operation System Administrator's Guide for details.
The output destination for biod error messages is syslog.
biod: cannot fork
| Cause: | biod failed in fork. |
| Action: | Restart biod. |
biod: usage: biod [<count>]
| Cause: | The start format is incorrect. |
| Action: | Check arguments. |
The output destination for comsat error messages is syslog.
comsat: pid: chdir: /usr/mail: system error message
| Cause: | Process pid could not perform chdir for /usr/mail. |
| Action: | Respond according to system error message. |
comsat: pid: main: /etc/utmp: system error message
| Cause: | Process pid could not open /etc/utmp. |
| Action: | Respond according to system error message. |
comsat: pid: malloc failed
| Cause: | Process pid could not allocate work memory having a size greater than or equal to the /etc/utmp size. |
| Home |
|---|
The output destination for cron error messages is console.
cron aborted: can't change directory to the crontab directory.
| Cause: | The directory could not be changed to the crontab directory. |
| Action: | Create a /usr/spool/cron/crontabs directory and restart cron. |
cron aborted: can't read the crontab directory
| Cause: | No directory information could be read from the crontab directory. |
| Action: | Check the permission of the /usr/spool/cron/crontabs directory and restart cron. |
cron aborted: cannot create fifo queue
| Cause: | A /usr/lib/cron/FIFO file could not be created. |
| Action: | There may be insufficient i nodes in the disk containing usr/lib/cron or the directory may not exist. Check these possibilities, then restart cron. |
cron aborted: cannot access fifo queue
| Cause: | The FIFO file could not be accessed. |
| Action: | Check the permission of the /usr/lib/cron/FIFO file, enable the file to be accessed, then restart cron. |
cron aborted: cannot start cron: FIFO exists
| Cause: | cron cannot be newly executed because the FIFO file already exists (cron is already active). |
| Action: | None. |
cron aborted: cannot open fifo queue
| Cause: | The FIFO file could not be opened. |
| Action: | Check the permission of the /usr/lib/cron/FIFO file, enable the file to be opened, then restart cron. |
| Home |
|---|
cron aborted: cannot open /usr/lib/cron/log
| Cause: | The log file could not be opened. |
| Action: | Check the permission of the /usr/lib/cron/log file, enable the file to be opened, then restart cron. |
cron aborted: cannot stat fifo queue
| Cause: | No information could be acquired from the /usr/lib/cron/FIFO file. |
| Action: | The /usr/lib/cron/FIFO file or directory may not exist. Check these possibilities, then restart cron. |
cron aborted: cron could not unlink FIFO
| Cause: | The /usr/lib/cron/FIFO file could not be deleted. |
| Action: | Check whether the /usr/lib/cron/FIFO file exists. When the file exists, use the rm command to delete it. |
cron aborted: SIGTERM
| Cause: | cron terminated because it received the SIGTERM signal. |
| Action: | None. |
cannot allocate n byte of space
| Cause: | Memory could not be allocated. |
| Action: | If necessary, increase the value of kernel system constant MAXUMEM. |
| Home |
|---|
The output destination for errdemon error messages is syslog.
errdemon[pid]: Can't fork
| Cause: | fork failed because system memory is insufficient. |
| Action: | Wait for a while, then restart errdemon. |
errdemon[pid]: illegal option
| Cause: | The specified argument is invalid. |
| Action: | Specify a correct argument. |
errdemon[pid]: Too long banner number
| Cause: | The specified banner number is too large. |
| Action: | Specify a correct banner number. |
errdemon[pid]: malloc failed
| Cause: | Memory could not be allocated. |
| Action: | If necessary, increase the value of kernel system constant MAXUMEM. |
errdemon[pid]: Can't create logfile
| Cause: | A log file could not be created. |
| Action: | There may be no inode in the disk, the right to write the directory may be unavailable, or the directory itself may not exist. Check these possibilities, then restart errdemon. |
errdemon[pid]: Can't open /dev/error
| Cause: | /dev/error could not be opened. |
| Action: | The right to read /dev/error may be unavailable or /dev/error itself may not exist. Check these possibilities, then restart errdemon. |
| Home |
|---|
The output destination for ftpd error messages is syslog.
getpeername (ftpd): system error message
| Cause: | The name (host name) of the connected client machine could not be fetched. |
| Action: | Refer to the descriptions of getpeername(2) in the SUPER-UX Programmer's Reference Manual according to system error message. |
getsockname (ftpd): system error message
| Cause: | The address of the socket to be connected to the standard input device could not be fetched. |
| Action: | Refer to the descriptions of getsockname(2) in the SUPER-UX Programmer's Reference Manual according to system error message. |
setsockopt: system error message
| Cause: | The SO_OOBLINE option could not be set for the socket connected to the standard input device. |
| Action: | Respond according to system error message. |
signal: system error message
| Cause: | The SIGURG signal capture function could not be set. |
| Action: | This error does not cause any particular problem because SUPER-UX currently does not support the SIGURG signal. For the cause of this error, see system error message. |
The following are ftpd notice messages. The output destination for ftpd notice messages is syslog.
FTP LOGIN REFUSED FROM host, name
| Cause: | The FTP login from client host of user name was refused because the shell program specifying user name in the password file is not registered in the /etc/shells file. This FTP login is also refused when login cannot be performed because the name of user name is registered in the /etc/ftpusers file. User name cannot be logged in. |
| Action: | When the shell program used by user name is not written in the /etc/shells file, the system administrator must modify the /etc/shells file. When the limitations on FTP login specified in the /etc/ftpusers file are unnecessary, delete user name from the entry. |
repeated login failures from host
| Cause: | The connection was released because password input from client host failed six times or more. ftpd terminated normally. |
| Action: | None. |
| Home |
|---|
The following are ftpd information messages. The output destination for ftpd information messages is syslog.
ANONYMOUS FTP LOGIN FROM host, passwd
| Cause: | Client host performed anonymous ftp login. The client is host and the mail address of the login user is passwd. This message is output only when ftpd is started with the -l option specified. |
| Action: | None. |
connection from host at time
| Cause: | The connection from host was established at time. This message is output only when ftpd is started with the -l option specified. |
| Action: | None. |
FTP LOGIN FROM host, name
| Cause: | User name performed FTP login from client host host. This message is output only when ftpd is started with the -l option specified. |
| Action: | None. |
User name timed out after timeout seconds at time
| Cause: | The connection of user name was released at time because no key was pressed during the specified time (timeout). |
| Action: | None. |
| Home |
|---|
The output destination for inetd error messages is standard error output (except where noted).
inetd: -r cannot be specified with 0
| Cause: | 0 is specified in the argument of the inetd -r option. |
| Action: | Modify the argument of the -r option. |
inetd: _r is specified with invalid argument.
| Cause: | An invalid value is specified in the argument of the inetd -r option. |
| Action: | Modify the argument of the -r option. |
inetd: Unknown flag _option ignored.
| Cause: | An invalid option (option) is specified in the inetd argument. |
| Action: | Modify the option. |
inetd[pid]: Out of memory.
| Cause: | Memory needed by inetd cannot be allocated. inetd terminates abnormally. The output destination for this message is syslog. |
| Action: | Check the memory size that can be used by the system and the memory load status. |
inetd[pid]: execv servname: system error message
| Cause: | inetd cannot activate the process for service servname. The output destination for this message is syslog. |
| Action: | Respond according to system error message. |
inetd[pid]: getpwnam: user
| Cause: | inetd cannot fetch the password entry of user from the configuration file. The output destination for this message is syslog. |
| Action: | Modify the user description in the configuration file. |
inetd[pid]: internal service servname unknown
| Cause: | An invalid internal service is specified in the inetd configuration file. The output destination for this message is syslog. |
| Action: | Modify the description of internal service servname in the configuration file. |
inetd[pid]: setsockopt (SO_DEBUG): system error message
| Cause: | inetd cannot set the SO_DEBUG option in the socket. The output destination for this message is syslog. |
| Action: | Respond according to system error message. |
| Home |
|---|
inetd[pid]: setsockopt (SO_REUSEADDR): system error message
| Cause: | inetd cannot set the SO_REUSEADDR option in the socket. The output destination for this message is syslog. |
| Action: | Respond according to system error message. |
inetd[pid]: servname/proto: bind: system error message
| Cause: | inetd cannot bind socket for service servname. The output destination for this message is syslog. |
| Action: | Respond according to system error message. |
inetd[pid]: servname/proto: server failing (looping), service terminated
| Cause: | inetd stopped service servname. The output destination for this message is syslog. |
| Action: | To restart service servname, transmit the SIGHUP signal to the inetd process. |
inetd[pid]: servname/proto: socket: system error message
| Cause: | inetd cannot create a socket for service servname. The output destination for this message is syslog. |
| Action: | Respond according to system error message. |
inetd[pid]: servname/proto: unknown service
| Cause: | Service servname is not registered in the /etc/services file. The output destination for this message is syslog. |
| Action: | Register service servname in the /etc/services file. |
inetd[pid]: config: system error message
| Cause: | inetd cannot read configuration file config. The output destination for this message is syslog. |
| Action: | Respond according to system error message and check configuration file config. |
| Home |
|---|
The following are inetd warning messages. The output destination for these messages is syslog.
inetd[pid]: accept: system error message
| Cause: | inetd failed in accept(2). |
| Action: | Respond according to system error message. |
inetd[pid]: select: system error message
| Cause: | inetd failed in select(2). |
| Action: | Respond according to system error message. |
inetd[pid]: server: exit status 0xnumber
| Cause: | Process server activated by inetd terminated abnormally. |
| Action: | None. |
The output destination for init error messages is console.
INIT: Cannot open /etc/inittab errno: errno
| Cause: | The /etc/inittab file could not be opened. |
| Action: | Check the /etc/inittab file. |
INIT: Cannot create /etc/utmp
| Cause: | The /etc/utmp file could not be opened for creation. |
| Action: | Check the status of the file system where the /etc directory exists. |
INIT: execlp of /bin/su failed; errno = errno
| Cause: | /bin/su could not be executed. |
| Action: | Check the cause of the unsuccessful execution according to system error number errno. |
| Home |
|---|
The output destination for init warning messages is console.
INIT: Cannot open /etc/TIMEZONE. Environment not initialized.
| Cause: | No environment variable was initialized because the /etc/TIMEZONE file could not be opened. |
| Action: | Check the /etc/TIMEZONE file. |
INIT: Command "command" failed to execute. errno = errno (exec of shell failed)
| Cause: | The shell needed to execute command command could not be executed. |
| Action: | Check the cause of unsuccessful execution according to system error number errno. |
INIT: Command is respawning too rapidly. Check for possible errors.
id: id "command"
| Cause: | The id id "command" written in the /etc/inittab file was executed ten times or more in two minutes. |
| Action: | Check whether the id id "command" written in the /etc/inittab file operates normally. |
INIT: failed write of utmp entry: "id"
| Cause: | The /etc/utmp file could not be updated. |
| Action: | Check the /etc/utmp file and the file system where the /etc/utmp file exists. |
INIT: Internal process table is full.
| Cause: | The init internal process table overflowed. |
| Action: | Reduce the number of entries written in the /etc/inittab file. |
| Home |
|---|
The output destination for init information messages is console.
INIT: New run level: n
| Cause: | The system has shifted to new execution level n. |
INIT: SINGLE USER MODE
| Cause: | The system is in the single-user mode. |
| Home |
|---|
D.10 lockd MESSAGES
The output destination for lockd error messages is syslog.
lockd[pid]: main: cannot create NLM tcp service.
| Cause: | The tcp service for the network lock manager could not be created. |
| Action: | Check the NFS environment. |
lockd[pid]: main: unable to register (NLM_PROG, NLM_VERS, tcp).
| Cause: | The tcp service for the network lock manager could not be registered. |
| Action: | Check the NFS environment. |
lockd[pid]: main: cannot create NLM udp service.
| Cause: | The udp service for the network lock manager could not be created. |
| Action: | Check the NFS environment. |
lockd[pid]: main: unable to register (NLM_PROG, NLM_VERS, udp).
| Cause: | The udp service for the network lock manager could not be registered. |
| Action: | Check the NFS environment. |
lockd[pid]: main: cannot create KLM udp service.
| Cause: | The udp service for the kernel lock manager could not be created. |
| Action: | Check the NFS environment. |
lockd[pid]: main: cannot get the address for UDP KLM. system error message
| Cause: | The address of the udp service for the kernel lock manager could not be obtained. |
| Action: | Check the NFS environment. |
lockd[pid]: main: unable to register (KLM_PROG, KLM_VERS, udp).
| Cause: | The udp service for the kernel lock manager could not be registered. |
| Action: | Check the NFS environment. |
| Home |
|---|
lockd[pid]: main: cannot create KLM tcp service.
| Cause: | The tcp service for the kernel lock manager could not be created. |
| Action: | Check the NFS environment. |
lockd[pid]: main: unable to register (KLM_PROG, KLM_VERS, tcp).
| Cause: | The tcp service for the kernel lock manager could not be registered. |
| Action: | Check the NFS environment. |
lockd[pid]: main: cannot create PRIV tcp service.
| Cause: | The tcp service for communication with statd could not be created. |
| Action: | Check the NFS environment. |
lockd[pid]: main: unable to register (KLM_PROG, KLM_VERS, tcp).
| Cause: | The tcp service for communication with statd could not be registered. |
| Action: | Check the NFS environment. |
lockd[pid]: main: cannot create PRIV udp service.
| Cause: | The udp service for communication with statd could not be created. |
| Action: | Check the NFS environment. |
lockd[pid]: main: unable to register (NLM_PROG, NLM_VERS, udp).
| Cause: | The udp service for communication with statd could not be registered. |
| Action: | Check the NFS environment. |
lockd[pid]: main /dev/lockd open failed: OS locks exist.
| Cause: | The /dev/lockd file could not be opened because a lock request was already processed by the kernel. |
| Action: | Release the lock request and restart lockd. |
lockd[pid]: main /dev/lockd open failed: system error message.
| Cause: | The /dev/lockd file could not be opened. |
| Action: | Check whether the /dev/lockd file exists. |
| Home |
|---|
lockd[pid]: main: /dev/lockd ioctl(L_SETCONF) failed; system error message, exiting.
| Cause: | ioctl for the /dev/lockd file failed. |
| Action: | Check whether the /dev/lockd file is a special file. |
lockd[pid]: main: /dev/lockd ioctl(L_ACTIVATE) failed: system error message, exiting.
| Cause: | ioctl for the /dev/lockd file failed. |
| Action: | Check whether the /dev/lockd file is a special file. |
lockd[pid]: main: udp_connect(): hostname NULL.
| Cause: | udp could not be connected because the host name is null. |
| Action: | Check the NFS environment. |
lockd[pid]: main:udp_connect(): unknown host hostname.
| Cause: | The specified host name is unknown. |
| Action: | Check the NFS environment. |
lockd[pid]: main: udp_connect(): create to hostname failed.
| Cause: | No connection could be created for the specified host. |
| Action: | Check the NFS environment. |
lockd[pid]: main: call_udp(): bad cache malloc.
| Cause: | Memory could not be allocated. |
| Action: | If necessary, increase the value of kernel system constant MAXUMEM. |
| Home |
|---|
The following are login error messages, which consist of critical, error, and notice messages.
The output destination for the following critical messages is syslog.
login: REPEATED LOGIN FAILURES ON ttyname (FROM hostname), username
| Cause: | User username failed in login because the number of unsuccessful login operations exceeded the limit. |
| Action: | None. |
login: ROOT LOGIN REFUSED ON ttyname (FROM hostname)
| Cause: | The login by superuser on terminal ttyname is refused. |
| Action: | None. |
The output destination for the following error messages is /usr/adm/loginlog (default).
<date and time> ILLEGAL ACCOUNT ID WAS GIVEN ON ttyname (FROM hostname), username
| Cause: | An attempt was made to perform login with an invalid account ID. |
| Action: | None. |
<date and time> ILLEGAL DIAL-UP PASSWORD WAS GIVEN ON ttyname (FROM hostname), username
| Cause: | User username entered an invalid dial-up password. |
| Action: | None. |
<date and time> ILLEGAL LOGIN USER ID WAS GIVEN ON ttyname (FROM hostname), username
| Cause: | An attempt was made to perform login with an invalid user name. |
| Action: | None. |
<date and time> ILLEGAL PASSWORD WAS GIVEN ON ttyname (FROM hostname), username
| Cause: | User username entered an invalid password. |
| Action: | None. |
<date and time> REPEATED LOGIN FAILURES ON ttyname (FROM hostname), username
| Cause: | The number of times user username failed in login operation exceeded the limit. |
| Action: | None. |
<date and time> TOO MUCH SESSIONS ON ttyname (FROM hostname), username
| Cause: | The number of logins by user username reached the maximum number permitted. |
| Action: | None. |
The output destination for the following notice message is syslog.
login: ROOT LOGIN ttyname FROM hostname
| Cause: | The superuser performed login with terminal ttyname. |
| Action: | None. |
| Home |
|---|
The following are lpd error messages, which consist of alert, error, and warning messages.
The output destination for the following alert message is syslog.
printer: can't send to remote printer, queue full
| Cause: | lpd cannot transmit a printer request because the remote printer queue is full. |
| Action: | Contact the administrator of the host system where the remote printer exists. |
The output destination for the following error messages is syslog.
lpd[pid]: /usr/spool/lpd.lock: system error message
| Cause: | lpd cannot execute open(2) or write(2) for the /usr/spool/lpd.lock file. Alternatively, lpd cannot lock the file. lpd terminates abnormally. |
| Action: | Check the /usr/spool/lpd.lock file according to system error message. |
lpd[pid]: Lost connection
| Cause: | lpd connection was released. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
| Home |
|---|
lpd[pid]: bad action (number) to dofork
| Cause: | lpd operation for the function dofork() is invalid. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
lpd[pid]: bind: System error message
lpd[pid]: ubind: System error message
| Cause: | lpd cannot execute bind(2) for the socket. lpd terminates abnormally. |
| Action: | Respond according to System error message. |
lpd[pid]: can't fork
| Cause: | lpd cannot create a child-process. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
lpd[pid]: can't open printer description file
lpd[pid]: cannot open printer description file
| Cause: | lpd cannot open the /etc/printcap file. |
| Action: | Check the /etc/printcap file. |
lpd[pid]: cannot find device major, minor
| Cause: | The disk device (major number (major), minor number (minor)) where the lpd spool directory exists was not found. |
| Action: | Check the lpd spool directory. |
lpd[pid]: cannot execl /bin/pr
| Cause: | lpd cannot activate /bin/pr. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
lpd[pid]: cannot execv prog
| Cause: | lpd cannot activate filter prog. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
| Home |
|---|
lpd[pid]: cannot restart output filter
| Cause: | lpd cannot restart the output filter. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
lpd[pid]: printer/tcp: unknown service
| Cause: | The printer service is not registered in the /etc/services file. lpd terminates abnormally. |
| Action: | Register the printer service in the /etc/services file. |
lpd[pid]: protocol screwup
| Cause: | The lpd communication protocol is abnormal. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
lpd[pid]: socket: system error message
| Cause: | lpd cannot create a socket. lpd terminates abnormally. |
| Action: | Respond according to system error message. |
lpd[pid]: unable to get hostname for remote machine name
| Cause: | lpd cannot acquire the host name of remote machine name. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
lpd[pid]: unable to get network name for local machine name
| Cause: | lpd cannot acquire the network name of local machine name. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
lpd[pid]: unknown printer: printer
| Cause: | printer is not registered in the /etc/printcap file. |
| Action: | Check the /etc/printcap file. |
| Home |
|---|
lpd[pid]: printer: Lost connection
| Cause: | lpd connection was lost while printer was processing the request. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
lpd[pid]: printer: can't spool spooldir
| Cause: | lpd cannot scan spool directory spooldir of printer. |
| Action: | Check spool directory spooldir. |
lpd[pid]: printer: can't create .railmag
| Cause: | lpd cannot create a .railmag file in the spool directory of printer. |
| Action: | Check the spool directory of printer. |
lpd[pid]: printer: illegal baud rate number
| Cause: | The baud rate (number) lpd attempted to set for printer is invalid. |
| Action: | Modify the baud rate description in the /etc/printcap file. |
lpd[pid]: printer: illegal format character 'format'
| Cause: | An invalid format exists in the control file to be processed by lpd. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
lpd[pid]: printer: ioctl(TCGETA): system error message
| Cause: | lpd cannot execute TCGETA of ioctl(2) for printer. |
| Action: | Respond according to system error message. |
lpd[pid]: printer: ioctl(TCSETA): system error message
| Cause: | lpd cannot execute TCSETA of ioctl(2) for printer. |
| Action: | Respond according to system error message. |
| Home |
|---|
lpd[pid]: printer: ioctl(TIOCEXCL): system error message
| Cause: | lpd cannot execute TIOCEXCL of ioctl(2) for printer. |
| Action: | Respond according to system error message. |
lpd[pid]: printer: ioctl(TIOCGETP): system error message
| Cause: | lpd cannot execute TIOCGETP of ioctl(2) for printer. |
| Action: | Respond according to system error message. |
lpd[pid]: printer: ioctl(TIOCSETP): system error message
| Cause: | lpd cannot execute TIOCSETP of ioctl(2) for printer. |
| Action: | Respond according to system error message. |
lpd[pid]: printer: no line printer device or host name
| Cause: | Both the line printer name and host name are not specified in the printer entry in the /etc/printcap file. |
| Action: | Specify the line printer name or host name. |
lpd[pid]: file: write error
| Cause: | write(2) failed when lpd read the data transmitted from the remote host. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
lpd[pid]: log file: system error message
| Cause: | lpd cannot execute open(2) for log file. |
| Action: | Check log file according to system error message. |
lpd[pid]: line printer: No such file or directory
| Cause: | line printer, which is the lpd output destination, does not exist. |
| Action: | Change the output destination. |
| Home |
|---|
lpd[pid]: file: system error message
| Cause: | lpd cannot execute open(2) for file used to read the data transmitted from the remote host. |
| Action: | Check file according to system error message. |
lpd[pid]: tfname: system error message
| Cause: | lpd cannot create a tfname (temporary copy of the control file) link. |
| Action: | Check tfname according to system error message. |
lpd[pid]: spool directory: system error message
| Cause: | lpd cannot change the work directory to spool directory. |
| Action: | Check spool directory according to system error message. |
lpd[pid]: printer: lock file: system error message
| Cause: | lpd cannot execute open(2), write(2), or chmod(2) for lock file. Alternatively, lpd cannot lock lock file. |
| Action: | Check lock file according to system error message. |
lpd[pid]: printer: ofilter: system error message
| Cause: | lpd cannot activate output filter ofilter of printer. |
| Action: | Check output filter ofilter according to system error message. |
lpd[pid]: printer: status file: system error message
| Cause: | lpd cannot execute open(2) for status file. Alternatively, lpd cannot lock status file. |
| Action: | Check status file according to system error message. |
lpd[pid]: printer: spool directory: system error message
| Cause: | lpd cannot change the work directory to spool directory.
lpd cannot execute stat(2) for spool directory. |
| Action: | Check spool directory according to system error message. |
| Home |
|---|
The output destination for the following lpd warning messages is syslog.
lpd[pid]: accept: system error message
| Cause: | lpd failed in accept(2). |
| Action: | Respond according to system error message. |
lpd[pid]: select:system error message
| Cause: | lpd failed in select(2). |
| Action: | Respond according to system error message. |
lpd[pid]: startup: cannot fork
| Cause: | lpd cannot create a child-process within the startup() function. lpd terminates abnormally. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
lpd[pid]: printer: Daemon filter 'format' exited number
| Cause: | The filter used by lpd terminated in status number. |
| Action: | None. |
lpd[pid]: printer: local mode set: number(8)
| Cause: | number (octal) is specified for the terminal, which is the printer output destination, as the local mode. |
| Action: | None. |
lpd[pid]: printer: lock file: system error message
| Cause: |
|
| Action: | Check lock file according to system error message. |
lpd[pid]: printer: output filter died (retcode)(stopval)
| Cause: | The output filter terminated abnormally when lpd was processing a printer request. |
| Action: | None. |
lpd[pid]: printer: disk device: system error message
| Cause: | lpd cannot open disk device it uses when processing a printer request. |
| Action: | Check disk device according to system error message. |
| Home |
|---|
The output destination for the following information messages is syslog.
lpd[pid]: restarting printer
| Cause: | lpd is going to attempt to output the printer request again. |
| Action: | None. |
lpd[pid]: printer: file: changed size
| Cause: | The file size was modified when lpd transmitted a printer request. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
lpd[pid]: printer: file: lost connection
| Cause: | lpd connection was lost when lpd was processing a printer request. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
lpd[pid]: printer: control file: system error message
| Cause: | lpd could not open control file when processing a printer request. |
| Action: | Check control file according to system error message. |
| Home |
|---|
The output destination for the following error messages is syslog.
mountd: inet: socket: aa
| Cause: | The socket system call could not be executed for aa. |
| Action: | Check the cause of aa. |
mountd: bind: aa
| Cause: | The bind system call could not be executed for aa. |
| Action: | Check the cause of aa. |
mountd: inet: getsockname: aa
| Cause: | The getsockname system call could not be executed for aa. |
| Action: | Check the cause of aa. |
mountd: rstat: getsockname: aa
| Cause: | The getsockname system call could not be executed for aa. |
| Action: | Check the cause of aa. |
mountd: dup2: aa
| Cause: | The dup2 function could not be executed for aa. |
| Action: | Check the cause of aa. |
mountd: couldn't create udp transport
| Cause: | An RPC client could not be created. |
| Action: | None. |
mountd: couldn't register MOUNTPROG
| Cause: | mountd could not be registered. |
| Action: | None. |
| Home |
|---|
mountd: couldn't reply to rpc call
| Cause: | Transmission to the client failed. |
| Action: | None. |
mountd: mountd: stat: aa
| Cause: | The stat system call for the directory to which a mount request was issued could not be executed for aa. |
| Action: | Check the cause of aa. |
mountd: mountd: getfh: aa
| Cause: | The getfh system call could not be executed for aa. |
| Action: | Check the cause of aa. |
mountd: Cannot stat /etc/xtab aa:
| Cause: | The stat system call for the /etc/xtab file could not be executed for aa. |
| Action: | Check the cause of aa. |
mountd: /etc/xtab: invalid at line aa
| Cause: | Line aa in the /etc/xtab file is invalid. |
| Action: | Check line aa in the /etc/xtab file. |
| Home |
|---|
The output destination for the following error messages is syslog.
nfsd: usage: nfsd [servers]
| Cause: | The nfsd start format is invalid. |
| Action: | Check the arguments. |
nfsd: aa
| Cause: | nfsd could not be started for aa. |
| Action: | Check the cause of aa. |
nfsd: fork: aa
| Cause: | nfsd could not execute the fork system call for aa. |
| Action: | Check the cause of aa. |
nfsd: server already active
| Cause: | nfsd is already active. |
| Action: | None. |
The output destination for nqsdaemon error messages is syslog.
nqs: Another NQS local daemon is already running.
| Cause: | nqsdaemon has already been running on the local host, or NQS shutdown has not been completed yet. |
| Action: | Please start a new nqsdaemon after the old NQS shutdown is completed. |
nqs: Bad queue name reported by request shepherd.
| Cause: | The queue to which a request has been submitted does not exist. |
| Action: | Check if the queue really exists with the qstatq(1) command. |
nqs: Can't know gid of bin.
| Cause: | There is no group ID of the group bin. |
| Action: | Check if the NIS specification and the /etc/passwd file are correct. |
nqs: Can't know uid of root.
| Cause: | There is no user ID of the user root. |
| Action: | Check if the NIS specification and the /etc/passwd file are correct. |
nqs: Cannot recover from previous error.
| Cause: | The file descriptor for the NQS control file cannot be found. |
| Action: | None. |
| Home |
|---|
nqs: Configuration database descr size exceeds ATOMICBLKSIZ.
| Cause: | The size of the NQS database is too large. |
| Action: | None. |
nqs: Configuration database descriptor size exceeds ATOMICBLKSIZ.
| Cause: | The size of the NQS database is too large. |
| Action: | None. |
nqs: Control file of request (seqno.mid) can't open.
| Cause: | The control file of the request seqno.mid cannot be opened. |
| Action: | Check the mode of directories under /usr/spool/nqs and NQS commands. |
nqs: Control-file header exceeds ATOMICBLKSIZ requirement.
| Cause: | The header of the NQS control file is too large. |
| Action: | None. |
nqs: Error opening s for reading.
| Cause: | The FIFO pipe s cannot be opened. |
| Action: | None. |
nqs: Error opening s for writing.
| Cause: | The FIFO pipe s cannot be opened. |
| Action: | None. |
nqs: Error opening dummy file.n
| Cause: | A dummy file cannot be opened. Errno is n. |
| Action: | None. |
nqs: Error reading NQS request pipe.
| Cause: | The reading request from the FIFO pipe failed. |
| Action: | None. |
| Home |
|---|
nqs: Execve() of shell: s failed
| Cause: | A shell server s for executing NQS requests cannot be started. |
| Action: | None. |
nqs: Failed in ulimit().
| Cause: | Executing ulimit(2) failed. |
| Action: | None. |
nqs: Failed to get NQS version file.
| Cause: | An NQS version file cannot be retrieved. |
| Action: | Check the mode of /usr/spool/nqs/private/root/database/version. |
nqs: Improper invocation of nqs spawn().
| Cause: | There is no request to be executed. |
| Action: | None. |
nqs: Inconsistent message packet received by NQS local daemon.
| Cause: | An invalid packet is received. |
| Action: | None. |
nqs: Insufficient memory to create TZ
| Cause: | The memory is running short. |
| Action: | None. |
nqs: Insufficient memory.
| Cause: | The memory is running short. |
| Action: | None. |
nqs: Invalid NQS database descriptor type.
| Cause: | An invalid NQS database descriptor type is specified. |
| Action: | None. |
| Home |
|---|
nqs: Invalid NQS general parameters file descriptor type
| Cause: | The NQS general parameters file descriptor type is invalid. |
| Action: | None. |
nqs: Invalid NQS general parameters file descriptor type specified in call to _sizedb().
| Cause: | The NQS general parameters file descriptor type is invalid. |
| Action: | None. |
nqs: MAX_EXTREQUESTS > MAX_TRANSACTS.
| Cause: | The number of requests that can be submitted from the remote hosts to the local host exceeds the number of requests that can be handled by the local host. |
| Action: | None. |
nqs: Mail request log structure size exceeds ATOMICBLKSIZ.
| Cause: | The NQS structure size for a request log exceeds 4096 bytes. |
| Action: | None. |
nqs: Mknod() error for: s.
| Cause: | mknod(2) for s failed. |
| Action: | None. |
nqs: Multiple database definitions for destination.
| Cause: | There are multiple definitions for the same destination in the NQS database. |
| Action: | None. |
nqs: Multiple database definitions for mapping.
| Cause: | There are multiple definitions for the same mapping in the NQS database. |
| Action: | None. |
| Home |
|---|
nqs: Multiple database definitions for queue.
| Cause: | There are multiple definitions for the same queue in the NQS database. |
| Action: | None. |
nqs: Multiple database entries for a complex.
| Cause: | There are multiple entries for the same complex in the NQS database. |
| Action: | None. |
nqs: Multiple database entries for a device.
| Cause: | There are multiple entries for the same device in the NQS database. |
| Action: | None. |
nqs: Multiple database entries for a group access.
| Cause: | There are multiple entries for the same group access in the NQS database. |
| Action: | None. |
nqs: Multiple database entries for a user access.
| Cause: | There are multiple entries for the same user access in the NQS database. |
| Action: | None. |
nqs: Multiple reservations on tid in nqs_rbuild().
| Cause: | A request that has already gotten its transaction ID tried to get another transaction ID. |
| Action: | None. |
nqs: NQS internal error.
| Cause: | An NQS internal error occurred. |
| Action: | None. |
nqs: NQS internal error: upd_deldes() no exist.
| Cause: | nqsdaemon tried to delete a pipe queue destination file though the file does not exist. |
| Action: | None. |
nqs: NQS internal error: upd_deldes() ref != 0.
| Cause: | nqsdaemon tried to delete a pipe queue destination file while the file was being used. |
| Action: | None. |
| Home |
|---|
nqs: NQS log daemon has exited.
| Cause: | The NQS logdaemon aborted. |
| Action: | Restart nqsdaemon. |
nqs: NQS not running as root in nqs_complt().
| Cause: | The user ID of nqsdaemon is not the user ID of root. |
| Action: | Restart nqsdaemon with the privilege of root. |
nqs: NQS not running as root in nqs_main().
| Cause: | The user ID of nqsdaemon is not the user ID of root. |
| Action: | Restart nqsdaemon with the privilege of root. |
nqs: NQS not running as root.
| Cause: | The user ID of nqsdaemon is not the user ID of root. |
| Action: | Restart nqsdaemon with the privilege of root. |
nqs: NQS restart directory can't change owner.
| Cause: | The owner of a directory for the NQS restart file cannot be changed. |
| Action: | None. |
nqs: NQS restart directory can't create.
| Cause: | A directory for the NQS restart file cannot be created. |
| Action: | None. |
nqs: Netdaemon uid or euid wrong.
| Cause: | The user ID for netdaemon is wrong. |
| Action: | Restart nqsdaemon with the privilege of root. |
| Home |
|---|
nqs: Netdaemon unable to create logfile stream.
| Cause: | A stream to output messages to logdaemon cannot be opened. |
| Action: | None. |
nqs: Netdaemon unable to duplicate stdout.
| Cause: | dup(2) for stdout failed. |
| Action: | None. |
nqs: Netdaemon: Bind() error.
| Cause: | bind(2) failed because netdaemon has already been running. |
| Action: | Kill netdaemon with the kill(1) command. |
nqs: Netdaemon: Improper invocation.
| Cause: | fstat(2) of FIFO for submitting requests failed. |
| Action: | None. |
nqs: Netdaemon: Listen() error.
| Cause: | listen(2) failed. |
| Action: | None. |
nqs: Netdaemon: Service [nqs] is unknown.
| Cause: | The port number for netdaemon cannot be found. |
| Action: | Check if an entry for NQS exists in /etc/services. |
nqs: Netdaemon: Socket() error.
| Cause: | socket(2) failed. |
| Action: | None. |
nqs: Netdaemon: Unable to chdir to s.
| Cause: | Changing the directory to s failed. |
| Action: | None. |
| Home |
|---|
nqs: Netdaemon: accept() error.
| Cause: | accept(2) failed. |
| Action: | None. |
nqs: Netdaemon: unable to determine machine-id of local host.
| Cause: | The machine ID of the local host is invalid. |
| Action: | Check if the local host is registered in nmap. |
nqs: Netdaemon: unable to open general parameters file.
| Cause: | The NQS parameters file cannot be opened. |
| Action: | None. |
nqs: No run slot available to spawn request.
| Cause: | The number of requests that can be executed at one time is full. |
| Action: | None. |
nqs: No such complex for database queue/complex mapping.
| Cause: | The specified complex is not on the NQS database. |
| Action: | None. |
nqs: No such device for database queue/device mapping.
| Cause: | The specified device is not on the NQS database. |
| Action: | None. |
nqs: No such queue for database queue/complex mapping.
| Cause: | The specified queue is not on the NQS database. |
| Action: | None. |
nqs: No such queue for database queue/device mapping.
| Cause: | The specified queue is not on the NQS database. |
| Action: | None. |
| Home |
|---|
nqs: PRECISION_ULONG exceeds actual value in nqs_tid.c
| Cause: | Formatting a table for managing the NQS transaction ID failed. |
| Action: | None. |
nqs: Plock() failure in nqs_ldconf.c.
| Cause: | plock(2) failed. |
| Action: | None. |
nqs: Request not found in nqs_reqcom().
| Cause: | A request whose execution has completed is not registered on the request execution managing table. |
| Action: | None. |
nqs: Shepherd[pid]: Can not read request control file. seqno=seqno, mid=mid
| Cause: | The NQS control file cannot be read. |
| Action: | None. |
nqs: The default network queue isn't prepared!!
| Cause: | There is no default network queue. |
| Action: | None. |
nqs: The request that is started stageout can't be found.
| Cause: | There is no request that has started staging out. |
| Action: | None. |
nqs: Too many NQS network daemon arguments.
| Cause: | Too many options are specified for netdaemon. |
| Action: | Reduce the options. |
nqs: Too many devices defined.
| Cause: | The number of devices exceeds the number that is permitted by the local host. |
| Action: | None. |
| Home |
|---|
nqs: Tra_read() error in nqs_rbuild().
| Cause: | The NQS transaction file cannot be read. |
| Action: | None. |
nqs: Tra_release() error in nqs_rbuild().
| Cause: | The NQS transaction file cannot be released. |
| Action: | None. |
nqs: Uid of owner of request (seqno.mid).
| Cause: | The owner ID of the request control file cannot be retrieved. |
| Action: | None. |
nqs: Unable to chdir() to s.
| Cause: | Changing a directory to s failed. |
| Action: | Check if s really exists. |
nqs: Unable to chdir() to the NQS root directory.
| Cause: | Changing a directory to the NQS root directory failed. |
| Action: | Check if the NQS root directory exists. |
nqs: Unable to create pipe between NQS local daemon and NQS log daemon.
| Cause: | A pipe for output to the NQS log cannot be created. |
| Action: | None. |
nqs: Unable to create read/write packet request pipe.
| Cause: | An FIFO pipe to receive NQS requests cannot be created. |
| Action: | None. |
nqs: Unable to create tmp-file to check whether it is booting.
| Cause: | A temporary file to check whether NQS is booting cannot be created. |
| Action: | None. |
| Home |
|---|
nqs: Unable to create/open Devicefile.
| Cause: | Creating/opening the device definition file failed. |
| Action: | None. |
nqs: Unable to create/open Formsfile.
| Cause: | Creating/opening the form definition file failed. |
| Action: | None. |
nqsS: Unable to create/open Mgrfile.
| Cause: | Creating/opening the manager definition file failed. |
| Action: | None. |
nqs: Unable to create/open Netqueuefile.
| Cause: | Creating/opening the network queue definition file failed. |
| Action: | None. |
nqs: Unable to create/open Paramfile.
| Cause: | Creating/opening the parameter definition file failed. |
| Action: | None. |
nqs: Unable to create/open Pipeqfile.
| Cause: | Creating/opening the pipe queue definition file failed. |
| Action: | None. |
nqs: Unable to create/open Qmapfile.
| Cause: | Creating/opening the queue map definition file failed. |
| Action: | None. |
nqs: Unable to create/open Queuefile.
| Cause: | Creating/opening the queue definition file failed. |
| Action: | None. |
| Home |
|---|
nqs: Unable to determine machine-id of local host.
| Cause: | The machine ID of the local host cannot be retrieved. |
| Action: | Check if the local host is registered on nmap, using nmapmgr(1M). |
nqs: Unable to execve() NQS network daemon.
| Cause: | Starting netdaemon failed. |
| Action: | None. |
nqs: Unable to fork NQS log process.
| Cause: | Starting logdaemon failed. |
| Action: | None. |
nqs: Unable to fork() NQS local daemon.
| Cause: | Starting netdaemon failed. |
| Action: | None. |
nqs: Unable to fork() NQS network daemon.
| Cause: | Starting netdaemon failed. |
| Action: | None. |
nqs: Unable to get machine-id of local host.
| Cause: | Getting the machine ID of the local host failed. |
| Action: | Check if the local host is registered on nmap, using nmapmgr(1M). |
nqs: Unable to open file.
| Cause: | open(2) of files failed. |
| Action: | None. |
nqs: Unable to open general parameters file.
| Cause: | Opening the NQS general parameters file failed. |
| Action: | None. |
| Home |
|---|
nqs: Unable to open inter-process communication directory.
| Cause: | Cannot access the directory to communicate between nqsdaemon and NQS clients. |
| Action: | Check if the directory exists. |
nqs: Unable to open new request directory.
| Cause: | Cannot access the directory to place the new request. |
| Action: | Check if the directory exists. |
nqs: Unable to open queue ordering directory.
| Cause: | The queue ordering file cannot be opened. |
| Action: | None. |
nqs: Unable to open request control file.
| Cause: | The request control file cannot be opened. |
| Action: | None. |
nqs: Unable to open request control file.
nqs: So, I can't make output any ACCT data.
| Cause: | The request control file cannot be opened, so an account record cannot be output. |
| Action: | None. |
nqs: Unable to open request control file.
nqs: So, I can't output any data of ACCT.
| Cause: | The request control file cannot be opened, so an account record cannot be output. |
| Action: | None. |
nqs: Unable to open request control file.
nqs: So, I'm very sorry but I can't output any data of ACCT information.
| Cause: | The request control file cannot be opened, so an account record cannot be output. |
| Action: | None. |
| Home |
|---|
nqs: Unable to open shell-script link directory.
| Cause: | Cannot access the directory for the link file to requests. |
| Action: | Check if the directory exists. |
nqs: Unable to open the NQS Qmgr help file.
| Cause: | The help file for qmgr(1M) cannot be opened. |
| Action: | Check if /usr/lib/nqs/qmgr.hlp exists. |
nqs: Unable to open the NQS Queue Complex file.
| Cause: | The NQS queue complex definition file cannot be opened. |
| Action: | None. |
nqs: Unable to open the NQS access definition database file.
| Cause: | The NQS access definition file cannot be opened. |
| Action: | None. |
nqs: Unable to open the NQS device definition database file.
| Cause: | The NQS device definition file cannot be opened. |
| Action: | None. |
nqs: Unable to open the NQS form definition database file.
| Cause: | The NQS form definition file cannot be opened. |
| Action: | None. |
nqs: Unable to open the NQS forms file.
| Cause: | The NQS form definition file cannot be opened. |
| Action: | None. |
nqs: Unable to open the NQS network queue definition database file.
| Cause: | The NQS network queue definition file cannot be opened. |
| Action: | None. |
| Home |
|---|
nqs: Unable to open the NQS parameters database file.
| Cause: | The NQS parameters file cannot be opened. |
| Action: | None. |
nqs: Unable to open the NQS pipe-queue destination database file.
| Cause: | The NQS pipe queue destination file cannot be opened. |
| Action: | None. |
nqs: Unable to open the NQS queue definition database file.
| Cause: | The NQS queue definition file cannot be opened. |
| Action: | None. |
nqs: Unable to open the NQS queue/device/destination mapping database file.
| Cause: | The NQS mapping definition file cannot be opened. |
| Action: | None. |
nqs: Unable to open the device descriptor file.
| Cause: | The NQS device definition file cannot be opened. |
| Action: | None. |
nqs: Unable to open the directory: s.
| Cause: | The directory s cannot be opened. |
| Action: | Check if s exists. |
nqs: Unable to open the general parameters file.
| Cause: | The NQS parameters file cannot be opened. |
| Action: | None. |
| Home |
|---|
nqs: Unable to open the network queue descriptor file.
| Cause: | The NQS network queue definition file cannot be opened. |
| Action: | None. |
nqs: Unable to open the non-network queue descriptor file.
| Cause: | The NQS non-network queue definition file cannot be opened. |
| Action: | None. |
nqs: Unable to open the pipe queue destination mapping file.
| Cause: | The NQS pipe queue destination file cannot be opened. |
| Action: | None. |
nqs: Unable to open the queue/device/destination mapping file.
| Cause: | The NQS mapping definition file cannot be opened. |
| Action: | None. |
nqs: Unable to setgid().
| Cause: | The group ID cannot be changed. |
| Action: | None. |
nqs: Unable to unlink tmp-file to check if it is booting.
| Cause: | The temporary file to check if NQS is booting cannot be deleted. |
| Action: | None. |
nqs: Unable to update next available seq#.
| Cause: | The sequence number of requests cannot be updated. |
| Action: | None. |
nqs: Utime() call error in nqs_complt().
| Cause: | Reporting the result of requests to the NQS client failed. |
| Action: | None. |
nqs: Version of NQS database does not match this NQS system.
| Cause: | The version of the NQS database does not match what the NQS requires. |
| Action: | Check if rebuilding the NQS database was done at version update. |
| Home |
|---|
nqs: Virtual timer table full in call to to nqs_vtimer().
| Cause: | The virtual timer table is full. |
| Action: | None. |
nqs: Wait() call in nqs_chkreqcom.c failed.
| Cause: | wait(2) for checkpointing failed. |
| Action: | None. |
nqs: Wait() call in nqs_hldchkcom.c failed.
| Cause: | wait(2) for checkpointing failed. |
| Action: | None. |
nqs: Wait() call in nqs_reqcom.c failed.
| Cause: | wait(2) for executing NQS requests failed. |
| Action: | None. |
nqs: Wait() call in nqs_shtchkcom.c
| Cause: | wait(2) for checkpointing failed. |
| Action: | None. |
nqs: Write error in _rewritedb().
| Cause: | An NQS internal error occurred. |
| Action: | None. |
nqs: Write error in allodb().
| Cause: | An NQS internal error occurred. |
| Action: | None. |
| Home |
|---|
nqs: Write error in freedb().
| Cause: | An NQS internal error occurred. |
| Action: | None. |
nqs: Write error in rewritedb().
| Cause: | An NQS internal error occurred. |
| Action: | None. |
nqs: Wrong queue type for database queue/complex mapping.
| Cause: | There is an invalid type queue in the NQS mapping file. |
| Action: | None. |
nqs: Wrong queue type for database queue/device mapping.
| Cause: | There is an invalid type queue in the NQS mapping file. |
| Action: | None. |
| Home |
|---|
The output destination for the following error messages is syslog.
talkd[pid]: chdir: /dev: system error message
| Cause: | ntalkd cannot change the work directory to the /dev directory. ntalkd terminates abnormally. |
| Action: | Respond according to system error message and check the /dev directory. |
talkd[pid]: gethostname: system error message
| Cause: | ntalkd could not fetch the host name. ntalkd terminates abnormally. |
| Action: | Respond according to system error message. |
talkd[pid]: insert_table: Out of memory
| Cause: | ntalkd cannot allocate necessary memory. ntalkd terminates abnormally. |
| Action: | Check the memory size that can be used by the system and the memory load status. |
The output destination for the following warning messages is syslog.
talkd[pid]: Bad address, family number
| Cause: | The protocol family of ntalkd's client is an invalid value (number). |
| Action: | None. |
talkd[pid]: Bad control address, family number
| Cause: | The protocol family of ntalkd's client is an invalid value (number). |
| Action: | None. |
talkd[pid]: Bad protocol version number
| Cause: | The protocol version differs from the version (number) of the client (talk). |
| Action: | None. |
talkd[pid]: announce: wait: system error message
| Cause: | ntalkd failed in wait(2) for the child-process within the announce() function. |
| Action: | Respond according to system error message. |
talkd[pid]: recv: system error message
| Cause: | ntalkd failed in recv(2) from the socket. |
| Action: | Respond according to system error message. |
talkd[pid]: sendto: system error message
| Cause: | ntalkd failed in sendto(2) to the socket. |
| Action: | Respond according to system error message. |
| Home |
|---|
The output destination for the following error messages is syslog.
portmap: cannot create socket aa
| Cause: | portmap could not execute the socket system call for aa. |
| Action: | Check the cause of aa. |
portmap: portmap cannot bind aa
| Cause: | portmap could not execute the bind system call for aa. |
| Action: | Check the cause of aa. |
portmap: couldn't do udp_create
| Cause: | portmap could not create an RPC client. |
| Action: | None. |
portmap: couldn't do tcp_create
| Cause: | portmap could not create an RPC client. |
| Action: | None. |
| Home |
|---|
The output destination for the following error messages is syslog.
rexd: - Must be Super User to run rexd -
| Cause: | rexd was started by a user other than the superuser. |
| Action: | None. |
rexd: cannot fork: aa
| Cause: | rexd could not execute fork for aa. |
| Action: | Check the cause of aa. |
rexd: can't chdir to aa
| Cause: | rexd could not execute the chdir system call to directory aa. |
| Action: | None. |
The output destination for the following error message is /usr/adm/loginlog (default).
<date and time> rexecd: ILLEGAL PASSWORD WAS GIVEN FROM hostname, username
| Cause: | The password specified by user username is invalid. rexecd terminates abnormally. |
| Action: | None. |
The output destination for the following error message is syslog.
usage: rlogind
| Cause: | The rlogind argument is invalid. |
| Action: | Correct the rlogind argument. |
The output destination for the following warning messages is syslog.
rlogind[pid]: setsockopt (SO_KEEPALIVE): system error message
| Cause: | rlogind cannot set the SO_KEEPALIVE option in the socket. |
| Action: | Respond according to system error message |
rlogind[pid]: setsockopt (SO_RCVBUF): system error message
| Cause: | rlogind cannot set the SO_RCVBUF option in the socket. |
| Action: | Respond according to system error message. |
rlogind[pid]: setsockopt (SO_SNDBUF): system error message
| Cause: | rlogind cannot set the SO_SNDBUF option in the socket. |
| Action: | Respond according to system error message. |
| Home |
|---|
The output destination for the following error messages is syslog (except where noted).
rshd[pid]: 2nd port not reserved
| Cause: | The second port number is not reserved. rshd terminates abnormally. |
| Action: | None. |
rshd[pid]: can't get stderr port: system error message
| Cause: | The socket used as the standard error output destination cannot be acquired. rshd terminates abnormally. |
| Action: | Respond according to system error message. |
rshd[pid]: malformed from address
| Cause: | The connection destination address is invalid. rshd terminates abnormally. |
| Action: | None. |
<date and time> rshd: PERMISSION DENIED FROM hostname, username
| Cause: | User username is not allowed to execute commands. rshd terminates abnormally. The output destination for this message is /usr/adm/loginlog file (default). |
| Action: | None. |
| Home |
|---|
The output destination for the following warning messages is syslog.
rshd[pid]: setsockopt(SO_KEEPALIVE): system error message
| Cause: | rshd cannot set the SO_KEEPALIVE option in the socket. |
| Action: | Respond according to system error message. |
rshd[pid]: setsockopt(SO_LINGER): system error message
| Cause: | rshd cannot set the SO_LINGER option in the socket. |
| Action: | Respond according to system error message. |
The output destination for the following notice messages is syslog.
rshd[pid]: connection from bad port
| Cause: | The client port number is invalid. rshd terminates abnormally. |
| Action: | None. |
rshd[pid]: read: system error message
| Cause: | rshd failed to read (read(2)) from the socket. rshd terminates abnormally. |
| Action: | Respond according to system error message. |
The output destination for the following information message is syslog.
rshd[pid]: connect second port: system error message
| Cause: | rshd failed in socket connection (connect(2)). rshd terminates abnormally. |
| Action: | Respond according to system error message. |
| Home |
|---|
The output destination for the following error messages is syslog (except where noted).
/etc/utmp: system error message
| Cause: | rwhod failed to read (read(2)) the /etc/utmp file. The output destination for this error message is standard error output. |
| Action: | Check the /etc/utmp file according to system error message. |
/usr/spool/rwho: system error message
| Cause: | rwhod cannot change the work directory to the /usr/spool/rwho directory. rwhod terminates abnormally. The output destination for this error message is standard error output. |
| Action: | Check the /usr/spool/rwho directory according to system error message. |
rwhod[pid]: /dev/kmem: system error message
| Cause: | rwhod cannot open /dev/kmem. rwhod terminates abnormally. |
| Action: | Check /dev/kmem according to system error message. |
rwhod[pid]: /etc/utmp: system error message
| Cause: | rwhod failed in open(2) or creat(2) for the /etc/utmp file. rwhod terminates abnormally. |
| Action: | Check the /etc/utmp file according to system error message. |
rwhod[pid]: bind: system error message
| Cause: | rwhod cannot bind socket. rwhod terminates abnormally. |
| Action: | Respond according to system error message. |
rwhod[pid]: chdir(/dev): system error message
| Cause: | rwhod cannot change the work directory to the /dev directory. rwhod terminates abnormally. |
| Action: | Check the /dev directory according to system error message. |
| Home |
|---|
rwhod[pid]: chdir(/usr/spool/rwho): system error message
| Cause: | rwhod cannot change the work directory to the /usr/spool/rwho directory. rwhod terminates abnormally. |
| Action: | Check the /usr/spool/rwho directory according to system error message. |
rwhod[pid]: gethostname: system error message
| Cause: | rwhod could not fetch the host name. rwhod terminates abnormally. |
| Action: | Respond according to system error message. |
rwhod[pid]: ioctl (get broadaddr)
| Cause: | rwhod cannot execute ioctl(2) (SIOCGIFBRDADDR option) for the socket. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
rwhod[pid]: ioctl (get dstaddr)
| Cause: | rwhod cannot execute ioctl(2) (SIOCGIFDSTADDR option) for the socket. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
rwhod[pid]: ioctl (get interface configuration)
| Cause: | rwhod cannot execute ioctl(2) (SIOCGIFCONF option) for the socket. rwhod terminates abnormally. |
| Action: | It is difficult to identify the cause of the error only from this message. If other errors occur, also check them. |
rwhod[pid]: ioctl (get interface flags)