Another possibility is to check /etc/hosts.equiv to
make sure it calls out all the hosts. We found on our system that we needed
entries in hosts.equiv for all the nodes or rsh gave us the "connection refused"
error message. Merely adding the hosts to .rhosts did not do the
trick.
Don
Jones
-----Original Message----- From: Peter McLachlan
[mailto:pmclachl@ca.ibm.com] Sent: Thursday, June 05, 2003 10:02
AM To: General LAM/MPI mailing list Subject: Re: LAM: rsh
fails
'Connection refused'
suggests to me that the rsh daemon is not running on one of the nodes.
Restarting the service depends on the OS/host. Under linux it is
most likely run through inetd or xinetd. So check /etc/inetd.conf or
/etc/xinetd.d/rsh and make sure its set to run in.rshd (the daemon for rsh).
Then you can try 'service inetd start' or 'service xinetd start'.
Alternately it could always
be a firewall rule problem.
If rsh is running standalone without inetd or xinetd try doing a 'ps aux
| grep in.rshd' or a 'ps -ef | grep in.rshd'. This will show you if
the daemon is running or not.
Hope
that helps,
Peter
McLachlan e-mail: pmclachl@ca.ibm.com
"Alex Krouglov"
<alexkrouglov@concordidea.com> Sent by: lam-bounces@lam-mpi.org
06/05/2003 12:39 PM Please respond to General LAM/MPI mailing
list
I can't setup my LAM system now (used to work
before).
When I use rsh command from the 1st computer to the 2nd one, I
receive a message "poll: protocol failure in circuit setup". When I use rsh
command from the 2nd computer to the 1st one, I receive a message
"Connection refused".
Home directories have 755 permissions. Files
.rhosts are present in home directories with 644 permissions.
Thanks a
lot in advance.
Alex Krouglov Concord Idea Corp. Email:
alexkrouglov@concordidea.com
_______________________________________________ This
list is archived at
http://www.lam-mpi.org/MailArchives/lam/