Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions
Privacy Policy

  




 

 

System Administration Guide: Network Services
Previous Next

UUCP Error Messages

This section lists the error messages that are associated with UUCP.

UUCP ASSERT Error Messages

The following table lists ASSERT error messages.

Table 26-7 ASSERT Error Messages

Error Message

Description or Action

CAN'T OPEN

An open() or fopen() failed.

CAN'T WRITE

A write(), fwrite(), fprint(), or similar command, failed.

CAN'T READ

A read(), fgets(), or similar command failed.

CAN'T CREATE

A creat() call failed.

CAN'T ALLOCATE

A dynamic allocation failed.

CAN'T LOCK

An attempt to make a LCK (lock) file failed. In some situations, this error is fatal.

CAN'T STAT

A stat() call failed.

CAN'T CHMOD

A chmod() call failed.

CAN'T LINK

A link() call failed.

CAN'T CHDIR

A chdir() call failed.

CAN'T UNLINK

An unlink() call failed.

WRONG ROLE

This is an internal logic problem.

CAN'T MOVE TO CORRUPTDIR

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.

CAN'T CLOSE

A close() or fclose() call failed.

FILE EXISTS

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

A TCP/IP call is attempted, but no entry is in /etc/services for UUCP.

BAD UID

The user ID is not in the password database. Check name service configuration.

BAD LOGIN_UID

Same as previous description.

BAD LINE

A bad line is in the Devices file. Not enough arguments on one or more lines.

SYSLST OVERFLOW

An internal table in gename.c overflowed. A single job attempted to talk to more than 30 systems.

TOO MANY SAVED C FILES

Same as previous description.

RETURN FROM fixline ioctl

An ioctl(2), which should never fail, failed. A system driver problem has occurred.

BAD SPEED

A bad line speed appears in the Devices or Systems file (Class or Speed field).

BAD OPTION

A bad line or option is in the Permissions file. This error must be fixed immediately.

PKCGET READ

The remote machine probably hung up. No action is needed.

PKXSTART

The remote machine aborted in a nonrecoverable way. This error can usually be ignored.

TOO MANY LOCKS

An internal problem has occurred. Contact your system vendor.

XMV ERROR

A problem with some file or directory has occurred. The spool directory is the probable cause, as the modes of the destinations were supposed to be checked before this process was attempted.

CAN'T FORK

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.

UUCP STATUS Error Messages

The following table is a list of the most common STATUS error messages.

Table 26-8 UUCP STATUS Messages

Error Message

Description/Action

OK

Status is acceptable.

NO DEVICES AVAILABLE

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.

WRONG TIME TO CALL

A call was placed to the system at a time other than what is specified in the Systems file.

TALKING

Self-explanatory.

LOGIN FAILED

The login for the particular machine failed. The cause could be a wrong login or password, wrong number, a slow machine, or failure in executing the Dialer-Token-Pairs script.

CONVERSATION FAILED

The conversation failed after successful startup. This error usually means that one side went down, the program aborted, or the line (link) was dropped.

DIAL FAILED

The remote machine never answered. The cause could be a bad dialer or the wrong phone number.

BAD LOGIN/MACHINE COMBINATION

The machine called with a login/machine name that does not agree with the Permissions file. This error could be an attempt to masquerade.

DEVICE LOCKED

The calling device to be used is currently locked and in use by another process.

ASSERT ERROR

An ASSERT error occurred. Check the /var/uucp/.Admin/errors file for the error message and refer to the section UUCP ASSERT Error Messages.

SYSTEM NOT IN Systems FILE

The system is not in the Systems file.

CAN'T ACCESS DEVICE

The device tried does not exist or the modes are wrong. Check the appropriate entries in the Systems and Devices files.

DEVICE FAILED

The device could not be opened.

WRONG MACHINE NAME

The called machine is reporting a different name than expected.

CALLBACK REQUIRED

The called machine requires that it call your machine.

REMOTE HAS A LCK FILE FOR ME

The remote machine has a LCK file for your machine. The remote machine could be trying to call your machine. If the remote machine has an older version of UUCP, the process that was talking to your machine might have failed, leaving the LCK file. If the remote machine has the new version of UUCP and is not communicating with your machine, the process that has a LCK file is hung.

REMOTE DOES NOT KNOW ME

The remote machine does not have the node name of your machine in its Systems file.

REMOTE REJECT AFTER LOGIN

The login that was used by your machine to log in does not agree with what the remote machine was expecting.

REMOTE REJECT, UNKNOWN MESSAGE

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.

STARTUP FAILED

Login succeeded, but initial handshake failed.

CALLER SCRIPT FAILED

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.

UUCP Numerical Error Messages

The following table lists the exit code numbers of error status messages that are produced by the /usr/include/sysexits.h file. Not all are currently used by uucp.

Table 26-9 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 data format 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 problem could also include errors like “No message” to a mailer.

67

Address Unknown

The user that was specified did not exist. This error might be used for mail addresses or remote logins.

68

Host Name Unknown

The host did not exist. This error is used in mail addresses or network requests.

69

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.

70

Internal Software Error

An internal software error has been detected. This error should be limited to non-operating system-related errors, if possible.

71

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.

72

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.

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 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 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.

78

Configuration Error

The system detected an error in the configuration.

79

Entry Not Found

Entry not found.

79

Maximum Listed Value

Highest value for error messages.

Previous Next

 
 
  Published under the terms fo the Public Documentation License Version 1.01. Design by Interspire