I've spent several hours dealing with OSCAR/lam problems only to find the
cause was firewall issues, esp. pfilter. I turned pfilter off on all the
internal nodes of my cluster.
Is there any reason why it should have been on in the first place????
They're behind the master node.
-----Original Message-----
From: Krishnakanth Subramaniam [mailto:ksubramz_at_[hidden]]
Sent: Monday, July 21, 2003 6:21 PM
To: General LAM/MPI mailing list
Subject: Re: LAM: lamboot problem !
Hi all ,
Sorry for the late response !
Well ..as u said, there was a firewall running between the machines ! and
after I disabled it lamboot worked just fine ..Thanks :-)
architecture specific firewall disabling :
Redhat Linux 8.0
% /sbin/service iptables stop
Thanks
Krish
--
Krish Subramaniam
Grad Student-EECS-Systems
Univ of Michigan, Ann Arbor.
Quoting Jeff Squyres <jsquyres_at_[hidden]>:
> On Fri, 11 Jul 2003, Krishnakanth Subramaniam wrote:
> > > n0<23065> ssi:boot:base:server: connecting to lamd at
166.82.1.11:33456
> >
>
----------------------------------------------------------------------------
-
> > The lamboot agent failed to open a client socket to the newly-booted
> > process at IP address 166.82.1.11, port 33456.
> > [snipped]
> >
>
----------------------------------------------------------------------------
-
> >
> > Now the problem is not #1. and for no. 2 and 3, i did telnet to the
> > machine and it did give me a connection refused thing.
>
> Have you checked to see if there are any firewall/filtering software
> packages between .11 and .18? LAM/MPI requires the ability to open random
> TCP ports between machines.
>
> --
> {+} 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/
|
