I would also assume that this is due to a bad install somehow. It sounds
like you installed LAM locally on both machines. Did you install via source
(ie., "make all install")? If so, was there anything obvious in the "make
install" output that indicated that something failed? There should be a
fairly obvious indication of when the lam-conf.lamd file is copied to the
installation location.
Another issue to be sure of is that you aren't inadvertantly mixing versions
of LAM -- many Linux distros ship with LAM/MPI these days. You might want
to ensure that a distro-installed version is not getting in your way, etc.
On 7/30/06 9:37 AM, "Rob Malpass" <r.malpass_at_[hidden]> wrote:
> Dear all
>
> I'm having a few problems adding to a known working (6.5.6) installation
> across several machines. There are several reasons (not the least of which
> is time) which prevent me from upgrading to the latest version and I don't
> think it's the age of the version that's giving me the problem.
> Essentially the working boxes have too little resources to compile anything
> later than 6.5 - I've tried before.
>
> Essentially I am trying to make two boxes (one Ubuntu as the master) and one
> Debian Woody as the slave boot. I'm encountering a problem I've never seen
> before:
>
> On lamboot, I'm getting an error to do with being unable to find
> lam-conf.lamd
>
> This is probably because that file doesn't exist on the slave node - not
> sure why - the install was fresh. I tried a bad fix (copy lam-conf.lamd
> from Master to slave) but that's giving me odd error messages like check
> network instability.
>
> I think this is something easy to fix - but not sure how.
>
> Cheers
> Rob
>
>
--
Jeff Squyres
Server Virtualization Business Unit
Cisco Systems
|
