Have you considered trying ssh with pregenerated keys (Eg. non-interactive
login)? I've had good luck using ssh across large numbers of nodes.
Do a google on ssh and authorized_keys, I'm sure there's a tutorial on it
somewhere.
Regards,
Peter McLachlan
I/T Specialist - Redhat Certified Engineer (RHCE)
Linux Solutions
IBM Global Services
Office: (905) 316-8646
e-mail: pmclachl_at_[hidden]
"Alex Krouglov" <alexkrouglov_at_[hidden]>
Sent by: lam-bounces_at_[hidden]
06/10/2003 10:14 AM
Please respond to General LAM/MPI mailing list
To: "General LAM/MPI mailing list" <lam_at_[hidden]>
cc:
Subject: RE: LAM: rsh fails
Jeff,
I checked all these files.
Another piece of information. ping works without problem. When I connect
"troubled" PC via 100-ethernet it worked well, but problem is with rsh via
Gigabit ethernet (D-Link DGE-550T). I reinstalled Linux OS on the
"troubled"
PC but without luck.
We think that xinetd doesn't communicate properly with rshd daemon but
can't
check it since rshd can't be run in the standalone mode.
Thanks.
Alex
-----Original Message-----
From: lam-bounces_at_[hidden] [mailto:lam-bounces_at_[hidden]]On Behalf
Of Jeff Squyres
Sent: Tuesday, June 10, 2003 7:01 AM
To: General LAM/MPI mailing list
Subject: RE: LAM: rsh fails
On Thu, 5 Jun 2003, Alex Krouglov wrote:
> Unfortunately the problem is not there. Looks like something is wrong
> with the ports.
I think you should really check for a firewall on your machines; some
linux distros install them by default. Also check /etc/hosts.allow and
hosts.deny (I believe that many linux distro rsh'es uses these by
default). The error messages that you're getting seem to indicate that
the rsh itself is failing to connect to the remote node, which usually
means one of the following:
1. rsh can't connect to the target rshd because some intermediate software
blocked the attempt (e.g., a firewall or hosts.allow/hosts.deny)
2. the rshd itself is not running on the target machine (see the previous
reply), and there was nothing for rsh to connect to
3. permissions prohibit the target rshd from running the specified command
(e.g., .rhosts and so on).
It sounds like you are having a problem with either #1 or #2.
> -----
> '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.
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|
