Indeed, that is really whacky.
That is really whacky. Looking at your output, that just doesn't make
sense -- laminfo finds the module, but then we don't find it at run
time (i.e., it's not opened and then not selected for usage -- it's not
found at all).
This usually means that the module was unable to be loaded (loading and
initializing modules are different steps in LAM).
Is your libgm a dynamic library, perchance? If so, is your
LD_LIBRARY_PATH set properly to find it (particularly on remote nodes
-- note that this means that it must be set properly for
*noninteractive* logins)? You can look at the lamd's LD_LIBRARY_PATH
by:
lamexec n1 env | grep LD_LIBRARY_PATH
(where n1 is any node that is not your localhost -- assumedly n1 is not
where you ran lamboot).
On Jun 28, 2005, at 5:29 PM, Jeff Polasek wrote:
> Hi again...about two months ago, I posted about a problem I was having
> with lammpi on a Mac G5 cluster with myrinet.
>
> http://www.lam-mpi.org/MailArchives/lam/2005/04/10350.php
>
> There were several good suggestions, I tried them all, let it sit for
> afew weeks, started up again and am at my wits end. I have cut the
> path down to bare minimum, recompiled 7.1.1 many times with different
> options, compiled the cpi.c many times and just can not get the
> blankety blank blank beeep gm module to be recognized.
>
> I can start lam with lamboot manually with no errors.
>
> But every time I try to use runmpi it can not find the gm module.
>
> Does anyone have a compiled lam for OS 10.3.9 that works with GM
> that I can test on my systems?
>
> Thanks
>
> Jeff
> --
> Jeff Polasek
> Computer Systems Manager
> Chemical Engineering Department
> Texas A&M University
> 979-845-3398
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
