1833523 Members
2959 Online
110061 Solutions
New Discussion

uucp fails

 
Christa Foley
Occasional Advisor

uucp fails

Trying to use a US Robotics modem to uucp a file to an AIX server. Getting the following errors: (Failed (Login Failed), Conn failed (login Failed)). Any ideas?
6 REPLIES 6
Christa Foley
Occasional Advisor

Re: uucp fails

Thanks for your help, but I can't get to these documents. It does the search, but it comes back saying no documents match search.
Uday_S_Ankolekar
Honored Contributor

Re: uucp fails

Hi,

There seems to be something wrong with this site since yesterday.. Try now..

-USA..
Good Luck..
Uday_S_Ankolekar
Honored Contributor

Re: uucp fails

How can I verify UUCP is working?
RESOLUTION
This testing is useful if the problem is known to be or suspected to be
involved with the communication between systems (as opposed to a problem
with, say, a UUCP user command).

To verify that the Systems, Devices and Dialers files are correct, type:

cu -d9 remote

This will cause cu to verify that the system name is correct, that the system
remote can be dialed and that a login prompt is received. If this fails, the
problem is narrowed down to these items; the device file, the modem, cable or
related items.

If cu works but uucico fails to do the same thing (based on uucico debug
output), then the following could be problems:

- RTS is turned on in the modem but not on the port
- Permissions of programs or files as cu runs suid root and uucico runs suid
uucp.
- A uucico problem


Login as the uucp user.

If uucico is failing to connect successfully with the remote system,
manually login in with the abovementioned cu using the login name and
password from the /etc/uucp/Systems file. This will verify that a user can
successfully login.

If the remote is set up to run its uucico program on login, it will provide

Shere=remotesystemname

and will hang. Any other response indicates modem problems or setup on the
remote end. Modem problems will usually be accompanied by something that
looks like the above but which is not quite right (such as Rhere=).


Good Luck..
Uday_S_Ankolekar
Honored Contributor

Re: uucp fails

PROBLEM
Testing the /etc/uucp/Permissions file with UUCP.
RESOLUTION
Typing uucheck -v will verify the Permissions file. It is very important
when suspecting Permissions problems that this file output be closely
examined as problems will be shown but may not be obvious. Check for what
the output says versus what information was expected.

Note the difference between a correct entry and an incorrect entry.

Correct entry

LOGNAME=uucp MACHINE=newton READ=/:/etc/ WRITE=/:/etc/ COMMANDS=ALL SENDFILES=yes REQUEST=yes

The output of uucheck -v looks ok.

Incorrect entry

LOGNAME=uucp MACHINE=newton READ=/:/etc/ WRITE=/:/etc/ COMMANDS=ALL SENDFILES=yes REQUEST=yes

The output of uucheck -v shows the problem

When we call system(s): (newtonREAD=/) (/etc/)
We DO allow them to request files.
They can send files to
/
/etc/
They can request files from
/var/spool/uucppublic (DEFAULT)
Myname for the conversation will be hercules.
PUBDIR for the conversation will be /var/spool/uucppublic.
Machine(s): (newtonREAD=/) (/etc/)
CAN execute the following commands:
command (ALL), fullname (ALL)

It may not be easy to detect, but a space is missing on the first line.
The line should read:
LOGNAME=uucp MACHINE=newton not:
LOGNAME=uucp MACHINE=newtonThe lack of the space caused the permissions file to interpret the system name
as newtonREAD, not newton!

Good Luck..
John Waller
Esteemed Contributor

Re: uucp fails

I don't know whether you have now got anywhere with this as I had problems posting yesterday.
After submitting the uucp request try typing:
/usr/lib/uucp/Uutry (note the first U is CAPITAL).
This is a tool whereby you can manually see what happens during the dialup attempt to the AIX system. You can +C out of Uutry but if the calling script has hund you may need to manualy kill any uucico processes left behind.