This section lists the error messages that are associated with UUCP.
The following list describes the most common ASSERT error messages.
Cause: A bad line is in the Devices file. Not enough arguments on one or more lines.
Cause: The user ID is not in the password database. Check name service configuration.
Description: Same as BAD LOGIN_UID description.
Cause: A bad line or option is in the Permissions file. This error must be fixed immediately.
Cause: A bad line speed appears in the Devices or Systems file (Class or Speed field).
Cause: A dynamic allocation failed.
Cause: A chdir() call failed.
Cause: A chmod() call failed.
Cause: A close() or fclose() call failed.
Cause: A creat() call failed.
Cause: An attempt to make a fork and exec failed. The current job should not be lost but will be attempted later (uuxqt). No action is needed.
Cause: A link() call failed.
Cause: An attempt to make a LCK (lock) file failed. In some situations, this error is fatal.
CAN'T MOVE TO
Cause: An attempt to move some bad C. or X. files to the /var/spool/uucp/.Corrupt directory failed. The directory is probably missing or has wrong modes or owner.
Cause: An open() or fopen() failed.
Cause: A read(), fgets(), or similar command failed.
Cause: A stat() call failed.
Cause: An unlink() call failed.
Cause: A write(), fwrite(), fprint(), or similar command, failed.
Cause: The creation of a C. or D. file is attempted, but the file exists. This error occurs when a problem arises with the sequence file access, which usually indicates a software error.
NO uucp SERVICE NUMBER
Cause: A TCP/IP call is attempted, but no entry is in /etc/services for UUCP.
Cause: The remote system probably hung up. No action is needed.
Cause: The remote system terminated in a nonrecoverable way. This error can usually be ignored.
RETURN FROM fixline ioctl
Cause: An ioctl system call, which should never fail, failed. A system driver problem has occurred.
Cause: An internal table in gename.c overflowed. A single job attempted to talk to more than 30 systems.
TOO MANY LOCKS
Cause: An internal problem occurred. Contact your system vendor.
TOO MANY SAVED C FILES
Cause: Same as SYSLST OVERFLOW description
Cause: An internal logic problem occurred.
Cause: A problem with some file or directory occurred. The spool directory is the probable cause, as the modes of the destinations were supposed to be checked before this process was attempted.
The following list describes the most common STATUS error messages.
Description: Status is acceptable.
Description: An ASSERT error occurred. Check the /var/uucp/.Admin/errors file for the error message and refer to the section UUCP ASSERT Error Messages.
BAD LOGIN/MACHINE COMBINATION
Description: The system called with a login/system name that does not agree with the Permissions file. This error could be an attempt to masquerade.
Description: The called system requires that it call your system.
CALLER SCRIPT FAILED
Description: This error is usually the same as DIAL FAILED. However, if this error occurs often, suspect the caller script in the Dialers file. Use Uutry to check.
CAN'T ACCESS DEVICE
Description: The device tried does not exist or the modes are wrong. Check the appropriate entries in the Systems and Devices files.
Description: The conversation failed after successful startup. This error usually means that one side went down, the program terminated, or the line (link) was dropped.
Description: The device could not be opened.
Description: The calling device to be used is currently locked and in use by another process.
Description: The remote system never answered. The cause could be a bad dialer or the wrong phone number.
Description: The login for the particular system failed. The cause could be a wrong login or password, wrong number, a slow system, or failure in running the Dialer-Token-Pairs script.
NO DEVICES AVAILABLE
Description: Currently no device is available for the call. Check whether a valid device is in the Devices file for the particular system. Check the Systems file for the device to be used to call the system.
REMOTE DOES NOT KNOW ME
Description: The remote system does not have the node name of your system in its Systems file.
REMOTE HAS A LCK FILE FOR ME
Description: The remote system has a LCK file for your system. The remote system could be trying to call your system. If the remote system has an older version of UUCP, the process that was talking to your system might have failed, leaving the LCK file. If the remote system has the new version of UUCP and is not communicating with your system, the process that has a LCK file is hung.
REMOTE REJECT AFTER LOGIN
Description: The login that was used by your system to log in does not agree with what the remote system was expecting.
REMOTE REJECT, UNKNOWN MESSAGE
Description: The remote system rejected the communication with your system for an unknown reason. The remote system might not be running a standard version of UUCP.
Description: Login succeeded but initial handshake failed.
SYSTEM NOT IN Systems FILE
Description: The system is not in the Systems file.
WRONG MACHINE NAME
Description: The called system is reporting a different name than expected.
WRONG TIME TO CALL
Description: A call was placed to the system at a time other than what is specified in the Systems file.
The /usr/include/sysexits.h file produces the exit code numbers of error status messages.UUCP error messages begin at the number 64.Not all are currently used by uucp.
Description: Command-Line Usage Error The command was used incorrectly, for example, with the wrong number of arguments, a bad flag, or a bad syntax.
Description: Data Format Error. The input data was incorrect in some way. This data format should only be used for user's data and not system files.
Description: Cannot Open Input. An input file, not a system file, did not exist, or was not readable. This problem could also include errors like "No message" to a mailer.
Description: Address Unknown The user that was specified did not exist. This error might be used for mail addresses or remote logins.
Description: Host Name Unknown. The host did not exist. This error is used in mail addresses or network requests.
Description: Service Unavailable. A service is unavailable. This error can occur if a support program or file does not exist. This message also can simply indicate that something does not work and the cause currently is not identifiable.
Description: Internal Software Error. An internal software error has been detected. This error should be limited to non-operating system-related errors, if possible.
Description: System Error. An operating system error has been detected. This error is intended to be used for conditions like "cannot fork", "cannot create pipe". For instance, this error includes a getuid() return of a user who does not exist in the passwd file.
Description: Critical OS File Missing. A system file such as /etc/passwd or /var/admin/utmpx does not exist, cannot be opened, or has an error, such as a syntax error.
Description: Can't Create Output File. A user-specified output file cannot be created.
Description: Input/Output Error. An error occurred while doing I/O on some file.
Description: Temporary Failure. User is invited to retry. Temporary failure 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.
Description: Remote Error in Protocol. The remote system returned something that was "not possible" during a protocol exchange.
Description: Permission Denied. You do not have sufficient permission to perform the operation. This message is not intended for file system problems, which should use –NOINPUT or –CANTCREAT, but rather for higher-level permissions. For example, kre uses this message to restrict students who can send mail to.
Description: Configuration Error The system detected an error in the configuration.
Description: Entry Not Found
Description: Maximum Listed Value. Highest value for error messages.