387 lines
7.8 KiB
HTML
387 lines
7.8 KiB
HTML
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Troubleshooting</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"><LINK
|
|
REL="HOME"
|
|
TITLE="Linux Network Administrators Guide"
|
|
HREF="index.html"><LINK
|
|
REL="UP"
|
|
TITLE="ManagingTaylor UUCP"
|
|
HREF="x-087-2-uucp.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="UUCP Low-Level Protocols"
|
|
HREF="x-087-2-uucp.protocols.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Log Files and Debugging"
|
|
HREF="x13819.html"></HEAD
|
|
><BODY
|
|
CLASS="SECT1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>Linux Network Administrators Guide</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="x-087-2-uucp.protocols.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
>Chapter 16. ManagingTaylor UUCP</TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="x13819.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="SECT1"
|
|
><H1
|
|
CLASS="SECT1"
|
|
><A
|
|
NAME="X-087-2-UUCP.MISC.FAQ"
|
|
>16.6. Troubleshooting</A
|
|
></H1
|
|
><P
|
|
> This section describes what may go wrong with your UUCP connection and makes
|
|
location suggestions to fix the error. Although these problems are
|
|
encountered on a regular basis, there is much more that can go wrong
|
|
than what we have listed.</P
|
|
><P
|
|
> If you have a problem, enable debugging with <TT
|
|
CLASS="OPTION"
|
|
>–xall</TT
|
|
>,
|
|
and take a look at the output in <TT
|
|
CLASS="FILENAME"
|
|
>Debug</TT
|
|
> in the spool
|
|
directory. The file should help you to quickly recognize the problem. It is
|
|
often helpful to turn on the modem's speaker when it doesn't
|
|
connect. With Hayes-compatible modems, you can turn on the speaker by adding
|
|
<TT
|
|
CLASS="LITERAL"
|
|
>ATL1M1 OK</TT
|
|
> to the modem chat in the
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>dial</TT
|
|
> file.</P
|
|
><P
|
|
>The first check should always be whether all file permissions are set
|
|
correctly. <B
|
|
CLASS="COMMAND"
|
|
>uucico</B
|
|
> should be setuid <SPAN
|
|
CLASS="SYSTEMITEM"
|
|
>uucp</SPAN
|
|
>, and all files in
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>/usr/lib/uucp</TT
|
|
>,
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>/var/spool/uucp</TT
|
|
>, and
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>/var/spool/uucppublic</TT
|
|
> should be owned by
|
|
<SPAN
|
|
CLASS="SYSTEMITEM"
|
|
>uucp</SPAN
|
|
>. There are also some
|
|
hidden files in the spool directory which must be owned by <SPAN
|
|
CLASS="SYSTEMITEM"
|
|
>uucp</SPAN
|
|
> as well.<A
|
|
NAME="X-087-2-FNUU17"
|
|
HREF="#FTN.X-087-2-FNUU17"
|
|
>[1]</A
|
|
></P
|
|
><P
|
|
>When you're sure you have the permissions of all files set correctly, and
|
|
you're still experiencing problems, you can then begin to take error
|
|
messages more literally. We'll now look at some of the more common errors
|
|
and problems.</P
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN13783"
|
|
>16.6.1. uucico Keeps Saying “Wrong Time to Call”</A
|
|
></H2
|
|
><P
|
|
>This probably means that in the system entry in <TT
|
|
CLASS="FILENAME"
|
|
>sys</TT
|
|
>, you
|
|
didn't specify a <B
|
|
CLASS="COMMAND"
|
|
>time</B
|
|
> command that
|
|
details when the remote system may be called, or you gave one that actually
|
|
forbids calling at the current time. If no call schedule is given,
|
|
<B
|
|
CLASS="COMMAND"
|
|
>uucico</B
|
|
> assumes the system can never be called.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN13789"
|
|
>16.6.2. uucico Complains That the Site Is Already Locked</A
|
|
></H2
|
|
><P
|
|
>This means that <B
|
|
CLASS="COMMAND"
|
|
>uucico</B
|
|
> detects a lock file for the remote
|
|
system in <TT
|
|
CLASS="FILENAME"
|
|
>/var/spool/uucp</TT
|
|
>. The lock file may be from an
|
|
earlier call to the system that crashed or was killed. Another possible
|
|
explanation is that there's another <B
|
|
CLASS="COMMAND"
|
|
>uucico</B
|
|
> process
|
|
sitting around that is trying to dial the remote system and has gotten stuck
|
|
in a chat script, or stalled for some other reason.</P
|
|
><P
|
|
>To correct this error, kill all <B
|
|
CLASS="COMMAND"
|
|
>uucico</B
|
|
> processes
|
|
open for the site with a hangup signal, and remove all lock files that
|
|
they have left lying around.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN13797"
|
|
>16.6.3. You Can Connect to the Remote Site, but the Chat Script Fails</A
|
|
></H2
|
|
><P
|
|
>Look at the text you receive from the remote site. If it's garbled, you might
|
|
have a speed-related problem. Otherwise, confirm that it really agrees with what
|
|
your chat script expects. Remember, the chat script starts with an expect
|
|
string. If you receive the login prompt and send your name, but never get the
|
|
password prompt, insert some delays before sending it, or even in between the
|
|
letters. You might be too fast for your modem.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN13800"
|
|
>16.6.4. Your Modem Does Not Dial</A
|
|
></H2
|
|
><P
|
|
>If your modem doesn't indicate that the DTR line has been raised when
|
|
<B
|
|
CLASS="COMMAND"
|
|
>uucico</B
|
|
> calls out, you might not have given the
|
|
right device to <B
|
|
CLASS="COMMAND"
|
|
>uucico</B
|
|
>. If your modem recognizes
|
|
DTR, check with a terminal program that you can write to the modem. If
|
|
this works, turn on echoing with <SPAN
|
|
CLASS="SYSTEMITEM"
|
|
>\E</SPAN
|
|
> at the start of the modem chat. If the
|
|
modem doesn't echo your commands during the modem chat, check if your
|
|
line speed is too high or low. If you see the echo, check if you have
|
|
disabled modem responses or set them to number codes. Verify that the
|
|
chat script itself is correct. Remember that you have to write two
|
|
backslashes to send one to the modem.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN13806"
|
|
>16.6.5. Your Modem Tries to Dial but Doesn't Get Out</A
|
|
></H2
|
|
><P
|
|
>Insert a delay into the phone number, especially if you have to dial a
|
|
special sequence to gain an outside line from a corporate telephone network.
|
|
Make sure you are using the correct dial type, as some telephone networks
|
|
support only one type of dialing. Additionally, double check the telephone
|
|
number to make sure it's correct.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="AEN13809"
|
|
>16.6.6. Login Succeeds, but the Handshake Fails</A
|
|
></H2
|
|
><P
|
|
>Well, there can be a number of problems in this situation. The output in the
|
|
log file should tell you a lot. Look at what protocols the remote site
|
|
offers (it sends a string <TT
|
|
CLASS="LITERAL"
|
|
>P</TT
|
|
>
|
|
<TT
|
|
CLASS="REPLACEABLE"
|
|
><I
|
|
>protlist</I
|
|
></TT
|
|
> during the handshake). For the handshake
|
|
to succeed, both ends must support at least one common protocol, so check
|
|
that they do.</P
|
|
><P
|
|
>If the remote system sends <B
|
|
CLASS="COMMAND"
|
|
>RLCK</B
|
|
>, there is a stale lockfile
|
|
for you on the remote system already connected to the remote system on a
|
|
different line. Otherwise, ask the remote system administrator to remove the
|
|
file.</P
|
|
><P
|
|
>If the remote system sends <B
|
|
CLASS="COMMAND"
|
|
>RBADSEQ</B
|
|
>, it has conversation
|
|
count checks enabled for you, but the numbers didn't match. If it sends
|
|
<B
|
|
CLASS="COMMAND"
|
|
>RLOGIN</B
|
|
>, you were not permitted to log in under this ID.</P
|
|
></DIV
|
|
></DIV
|
|
><H3
|
|
CLASS="FOOTNOTES"
|
|
>Notes</H3
|
|
><TABLE
|
|
BORDER="0"
|
|
CLASS="FOOTNOTES"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
WIDTH="5%"
|
|
><A
|
|
NAME="FTN.X-087-2-FNUU17"
|
|
HREF="x-087-2-uucp.misc.faq.html#X-087-2-FNUU17"
|
|
>[1]</A
|
|
></TD
|
|
><TD
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
WIDTH="95%"
|
|
><P
|
|
> That is, files with names beginning with a
|
|
dot. Such files aren't normally displayed by the <B
|
|
CLASS="COMMAND"
|
|
>ls</B
|
|
>
|
|
command.</P
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="x-087-2-uucp.protocols.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="x13819.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>UUCP Low-Level Protocols</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="x-087-2-uucp.html"
|
|
>Up</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Log Files and Debugging</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |