LAM/MPI logo

LAM/MPI General User's Mailing List Archives

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

From: Ramon Diaz-Uriarte (rdiaz02_at_[hidden])
Date: 2006-11-04 13:32:00


Dear Gui-Bin,

On 11/4/06, Áõ¹ó±ó <goodluck_1982_at_[hidden]> wrote:

(...)

> But I cannot boot up lam on two CPUs.
> My machine is a server , 16 CPUs, memory shared.

This is a _very nice_ machine; just out of curiosity, what is the
motherboard? (Iff I get some grant money, I'd like purchasing one of
these, if they work smoothly with Linux).

> I write a hostfile which contains two lines of localhost and run
> "lamboot -v hostfile", the output is :

But how does your hostfile look like? I think something like

127.0.0.1 cpu=16

should be enough for you to have a lam universe over 8 CPUs.

> By the way, I config rsh correctly. When I run " rsh localhost ", I can
> login correctly.
> rsh localhost
> connect to address 127.0.0.1 port 543: Connection refused
> Trying krb4 rlogin...
> connect to address 127.0.0.1 port 543: Connection refused
> trying normal rlogin (/usr/bin/rlogin)
> Last login: Sat Nov 4 05:13:25 from n0

I think the real problme is your "hostfile", because you are able to
do lamboot and get a universe up, but notice that you get a whole
bunch of messages, with failed connection attempts, and I think lam
often does not like those things.

Try fixing the lamb-host.def file (your hostfile) and doing:

lamboot -v hostfile

and see what is happening and where it fails.

HTH,

R.

>
> How can I boot up a lam on two CPUs and how can I run lamtests correctly?
> Who can help me? Thanks in advance!
>
>
> Yours sincerely
> Gui-Bin Liu
>
>
> laminfo:
> LAM/MPI: 7.1.2
> Prefix: /usr/local/lam-pgi
> Architecture: x86_64-unknown-linux-gnu
> Configured by: root
> Configured on: Sat Nov 4 01:29:15 CST 2006
> Configure host: localhost.localdomain
> Memory manager: ptmalloc2
> C bindings: yes
> C++ bindings: yes
> Fortran bindings: yes
> C compiler: pgcc
> C++ compiler: pgCC
> Fortran compiler: pgf90
> Fortran symbols: underscore
> C profiling: yes
> C++ profiling: yes
> Fortran profiling: yes
> C++ exceptions: no
> Thread support: yes
> ROMIO support: yes
> IMPI support: no
> Debug support: no
> Purify clean: no
> SSI boot: globus (API v1.1, Module v0.6)
> SSI boot: rsh (API v1.1, Module v1.1)
> SSI boot: slurm (API v1.1, Module v1.0)
> SSI coll: lam_basic (API v1.1, Module v7.1)
> SSI coll: shmem (API v1.1, Module v1.0)
> SSI coll: smp (API v1.1, Module v1.2)
> SSI rpi: crtcp (API v1.1, Module v1.1)
> SSI rpi: lamd (API v1.0, Module v7.1)
> SSI rpi: sysv (API v1.0, Module v7.1)
> SSI rpi: tcp (API v1.0, Module v7.1)
> SSI rpi: usysv (API v1.0, Module v7.1)
> SSI cr: self (API v1.0, Module v1.0)
>
>
>
>
>
>
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
>

-- 
Ramon Diaz-Uriarte
Statistical Computing Team
Structural Biology and Biocomputing Programme
Spanish National Cancer Centre (CNIO)
http://ligarto.org/rdiaz