Common UUCP log and status file messages

UUCP keeps track of activity in log and status files in the /usr/spool/uucp directory. The UUCP programs uucp, uux , uucico , and uuxqt write status information for each system to files in the /usr/spool/uucp/.Log directories. The uucico utility writes messages to the files in the /usr/spool/uucp/.Status directory. These messages describe the status of the transfer request, such as uucico failures, completions, and the time until the next allowable call for each remote system with which you communicate.

The following sections suggest responses to common error messages that UUCP programs write to these files.

DEVICE LOCKED

The uucico creates a lock file named LCK..sitename for the remote system in the /usr/spool/uucp directory. If a file for the system that you are trying to call exists, uucico assumes that the device is in use.

To use the device, enter the following command on the remote system, substituting the name of the remote system for sitename:

rm /usr/spool/uucp/LCK.sitename

LOGIN FAILED

If this error message appears, one of several things may be wrong:

1. Check the /usr/lib/uucp/Systems file on the local machine to verify that the information in this file, particularly the chat script, is current. Some information that may be out-of-date is the phone number, login, and password.

2. Verify that the modem setup on both ends is correct. Refer to ``Troubleshooting modems'' for more information.

3. Check the phone connection. Try a different phone line.

NO DEVICES AVAILABLE

If the system displays this message, one of several things may be wrong:

1. The system assumes that the modem is in use because there is a lock file for it. Enter the following from the local machine:
   
   rm /usr/spool/uucp/LCK

2. There may be no valid device for the calling system to use. Verify that the device named in the /usr/lib/uucp/Systems file corresponds to the entry in /usr/lib/uucp/Devices.

3. If the message persists, reboot the system. Enter the rm command again, and then invoke the uutry command again.

4. If the message persists after rebooting the system, the modem may be configured incorrectly. Verify that you can use cu to call out. Refer to ``Troubleshooting modems'' for more information.

REMOTE DOES NOT KNOW ME

If the system displays this message, the /usr/lib/uucp/Systems file on the machine that you are trying to call does not contain an entry for your machine. Check the Systems file on the remote machine.

REMOTE HAS a LCK FILE FOR ME

If your system displays this message, either the remote system is trying to call your system or there is a lock file for your system on the remote system.

1. Remove the lock file from the remote system by removing the appropriate lock file:
   
   rm /usr/spool/uucp/LCK.sitename

2. Invoke the uutry command again.

SYSTEM NOT IN Systems FILE

If the /usr/lib/uucp/Systems file on your system does not contain an entry for the system that you are trying to access, this error message is displayed. Use the uuname command to verify that the system name is in the Systems file.

RETRY TIME NOT REACHED

When UUCP requests fail, retries are not executed immediately. After an attempt to contact a remote system, a status file remains in /usr/spool/uucp/.Status/nodename (nodename is the name of the remote system that you are trying to reach). This file contains information about the last request and does not allow another request until the minimum retry period (specified in the /usr/lib/uucp/Systems file) is reached. If you try to use UUCP again, the system displays an error message like the following:

   RETRY TIME NOT REACHED

CANNOT ACCESS FILE

If the system displays this message, it cannot access the calling device port. Check the permissions and ownership on the device file:

l /dev/ttyxx

Where xx is the tty number. The ownership and permissions settings should look like the following:

   crw-r--r--  1 uucp  uucp  5,  0 Feb  14 12:00 /dev/ttyxx

WRONG TIME TO CALL

The /usr/lib/uucp/Systems file may restrict outgoing calls at this time.