This section lists the error messages associated with UUCP.
Table 13-1 lists ASSERT error messages.
Table 13-1 ASSERT Error Messages
Table 13-2 is a list of the most common STATUS error messages.
Table 13-2 UUCP STATUS Messages
Error Message |
Description/Action |
---|---|
Status is okay. |
|
There is currently no device available for the call. Check to see that there is a valid device in the Devices file for the particular system. Check the Systems file for the device to be used to call the system. |
|
A call was placed to the system at a time other than what is specified in the Systems file. |
|
Self-explanatory. |
|
The login for the given machine failed. It could be a wrong login or password, wrong number, a very slow machine, or failure in getting through the Dialer-Token-Pairs script. |
|
The conversation failed after successful startup. This usually means that one side went down, the program aborted, or the line (link) was dropped. |
|
The remote machine never answered. It could be a bad dialer or the wrong phone number. |
|
The machine called us with a login/machine name that does not agree with the Permissions file. This could be an attempt to masquerade!. |
|
The calling device to be used is currently locked and in use by another process. |
|
An ASSERT error occurred. Check the /var/uucp/.Admin/errors file for the error message and refer to the section "UUCP Error Messages". |
|
The system is not in the Systems file. |
|
The device tried does not exist or the modes are wrong. Check the appropriate entries in the Systems and Devices files. |
|
The device could not be opened. |
|
The called machine is reporting a different name than expected. |
|
The called machine requires that it calls your machine. |
|
The remote machine has a LCK file for your machine. It could be trying to call your machine. If it has an older version of UUCP, the process that was talking to your machine might have failed, leaving the LCK file. If it has the new version of UUCP and is not communicating with your machine, then the process that has a LCK file is hung. |
|
The remote machine does not have the node name of your machine in its Systems file. |
|
The login used by your machine to login does not agree with what the remote machine was expecting. |
|
The remote machine rejected the communication with your machine for an unknown reason. The remote machine might not be running a standard version of UUCP. |
|
Login succeeded, but initial handshake failed. |
|
This is usually the same as DIAL FAILED. However, if it occurs often, suspect the caller script in the Dialers file. Use Uutry to check. |
Table 13-3 lists the exit code numbers of error status messages produced by the /usr/include/sysexits.h file. Not all are currently used by uucp.
Table 13-3 UUCP Error Messages by Number
Message Number |
Description |
Meaning |
---|---|---|
64 |
Base value for error messages |
Error messages begin at this value. |
64 |
Command Line Usage Error |
The command was used incorrectly, for example, with the wrong number of arguments, a bad flag, or a bad syntax. |
65 |
Data Format Error |
The input data was incorrect in some way. This should only be used for user's data and not system files. |
66 |
Cannot Open Input |
An input file (not a system file) did not exist, or was not readable. This could also include errors like "No message" to a mailer (if it cared to catch it). |
67 |
Address Unknown |
The user specified did not exist. This might be used for mail addresses or remote logins. |
68 |
Host Name Unknown |
The host did not exist. This is used in mail addresses or network requests. |
69 |
Service Unavailable |
A service is unavailable. This can occur if a support program or file does not exist. This message also can be a catchall message when something doesn't work and you don't know why. |
70 |
Internal Software Error |
An internal software error has been detected. This should be limited to non-operating system related errors if possible. |
71 |
System Error |
An operating system error has been detected. This is intended to be used for conditions like "cannot fork","cannot create pipe." For instance, it includes getuid returning a user that does not exist in the passwd file. |
72 |
Critical OS File Missing |
Some system file like /etc/passwd or /etc/utmp does not exist, cannot be opened, or has some error such as syntax error. |
73 |
Can't Create Output File |
A user specified output file cannot be created. |
74 |
Input/Output Error |
An error occurred while doing I/O on some file. |
75 |
Temporary Failure. User is invited to retry |
Temporary failure, indicating something that is not really an error. In sendmail, this means that a mailer, for example, could not create a connection, and the request should be reattempted later. |
76 |
Remote Error in Protocol |
The remote system returned something that was "not possible" during a protocol exchange. |
77 |
Permission Denied |
You do not have sufficient permission to perform the operation. This is not intended for file system problems, which should use NOINPUT or CANTCREAT, but rather for higher level permissions. For example, kre uses this to restrict students who can send mail to. |
78 |
Configuration Error |
There is an error in the configuration. |
79 |
Entry Not Found |
Entry not found. |
79 |
Maximum Listed Value |
Highest value for error messages. |