LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: ¤£¥Î¼z¦Ó (buyong.huier_at_[hidden])
Date: 2006-04-20 22:03:05


Thank Andrew, and thank Bogdan for your helps. The operating system on each
cluster computer is Red Hat Enterprise Linux AS release 3 (Taroon Update 2),
Kernel 2.4.21-15.EL on an x86_64.
I found /etc/hosts.allow, /etc/hosts.deny, and /etc/iproute*/* are all empty
except comments.
I can 'info iptables' but no command 'iptables'. When I create or modify a
file on one node, it
happens automatically on all other nodes, i.e. all the nodes automatically
keep the same files.
I'm a common user not 'root'. But I can contact the person who is 'root' (
he is not professional, also not familiar with Linux). I beg your
help. Thanks a lot!

 ---------- Forwarded message ----------
> From: Andrew Friedley <afriedle_at_[hidden]>
> To: General LAM/MPI mailing list <lam_at_[hidden]>
> Date: Thu, 20 Apr 2006 10:12:30 -0400
> Subject: Re: LAM: lamboot error ( append )
> $BITMQ7E<)(B wrote:
> > In the previous mail posted by me, I forgot to tell the fact that
> > when I follow the instructions of lam, 'telnet 192.168.1.1 33973' the
> shell
> > output
> > 'Trying 192.168.1.1...
> > telnet: Unable to connect to remote host: Connection refused'
> >
> > so it is not a common case. I've no idea how to check whether network
> > filters exist
>
> This is what I was about to suggest - looks like ports are being
> filtered. rsh appears to be able to run commands on remote hosts, which
> indicates you have at least some connectivity.
>
> Unfortunately, I can't tell you how exactly to check for packet filters
> - it depends on your operating system and configuration. Some proper
> googling should turn up how to do this. Otherwise, if you could provide
> some details on your operating system and its version, I might be able
> to help you figure it out.
>
> Andrew
>
>
>
>
> ---------- Forwarded message ----------
> From: Brian Barrett <brbarret_at_[hidden]>
> To: General LAM/MPI mailing list <lam_at_[hidden]>
> Date: Thu, 20 Apr 2006 08:07:24 -0700
> Subject: Re: LAM: Error installing LAM-7.1.2 in Cygwin
> On Apr 19, 2006, at 8:15 PM, raja wrote:
>
> > Thanks for your reply. Sorry for late reply to your posting due to
> > lack
> > of internet connection for last two days in my working place.
> > I already installed LAM-7.1.1 successfully in cygwin without any
> > single
> > error encountered. In order to upgrade it , I opted for
> > latetest version. Is there any major difference in LAM-7.1.1 and
> > LAM-7.1.2 ? The application which I am going to use LAM is GROMACS(a
> > Bioinformatics software). More The gromacs webpage stated that GROMACS
> > is not sensitive to LAM version.
>
> I can't say as to whether you can use 7.1.1 with your application.
> We generally recommend that everyone upgrade to 7.1.2, but if you
> can't update, then you can't update. You can see the entire list of
> bug fixes / new features in the HISTORY file contained in the LAM/MPI
> 7.1.2 tarball.
>
>
> Hope this helps,
>
> Brian
>
> --
> Brian Barrett
> LAM/MPI developer and all around nice guy
> Have a LAM/MPI day: http://www.lam-mpi.org/
>
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Bogdan Costescu <Bogdan.Costescu_at_[hidden]>
> To: General LAM/MPI mailing list <lam_at_[hidden]>
> Date: Thu, 20 Apr 2006 16:22:17 +0200 (CEST)
> Subject: Re: LAM: lamboot error ( append )
> On Thu, 20 Apr 2006, Andrew Friedley wrote:
>
> > >'telnet 192.168.1.1 33973' ...
> > > telnet: Unable to connect to remote host: Connection refused'
> > This is what I was about to suggest - looks like ports are being
> > filtered. rsh appears to be able to run commands on remote hosts, which
> > indicates you have at least some connectivity.
>
> I beg to disagree. Trying to telnet with a port specified would work
> only if there is some program listening on that port on the remote
> machine - this would happen only if the LAM application would still be
> running and waiting for connections. If the telnet is performed at a
> later time, there's nothing listening on that port and the "Connection
> refused" message is normal.
>
> However, the idea of ports being filtered is still valid and a
> probable explanation for the OP's problem.
>
> --
> Bogdan Costescu
>
> IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
> Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
> Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868
> E-mail: Bogdan.Costescu_at_[hidden]
>
>
>
>
>
>