Hi,
I'm having a problem successfully running lamboot, from lam 7.1.1, on a
bproc system running version 4.0p8. What I see from lamboot is:
lamboot hosts
LAM 7.1.1/MPI 2 C++/bproc - Indiana University
lamd kernel: problem with socket(): Address family not supported by protocol
...
I was able to do a little strace of this, and see errors like:
getxattr("/bpfs/-1", "bproc.addr", 0xbfffeff4, 16) = 16
socket(PF_FILE, SOCK_STREAM, 0) = 3
connect(3, {sa_family=AF_FILE, path="/var/run/.nscd_socket"}, 110) = -1
ENOENT (No such file or directory)
close(3) = 0
But that doesn't make much sense to me, looks like it trying to resolve
a name, perhaps. I assume this is a symptom, but not a cause.
Here's my laminfo:
LAM/MPI: 7.1.1
Prefix: /usr/local/lam-7.1.1
Architecture: i686-pc-linux-gnu
Configured by: root
Configured on: Fri Jan 14 18:28:27 EST 2005
Configure host: circe198
Memory manager: ptmalloc2
C bindings: yes
C++ bindings: yes
Fortran bindings: yes
C compiler: gcc
C++ compiler: g++
Fortran compiler: g77
Fortran symbols: double_underscore
C profiling: yes
C++ profiling: yes
Fortran profiling: yes
C++ exceptions: no
Thread support: yes
ROMIO support: no
IMPI support: no
Debug support: no
Purify clean: no
SSI boot: bproc (API v1.1, Module v1.1)
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: gm (API v1.1, Module v1.2)
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)
Any help or insight would be appreciated. My config.log and output from
lamboot -d are attached.
--
Dale Harris
rodmur_at_[hidden]
/.-)
|
