Can you send the output of laminfo, the output from configure, and the
top-level config.log? (please compress everything) It looks like you
only had one module available (globus), which is quite odd. You should
also have the rsh module, too. Perhaps it failed to build for some
reason...?
On Aug 7, 2004, at 5:22 AM, Hemanth Nagaraja wrote:
> Hi,
> After installing Lam 7.0.6 on HP - UX, I did a recon with following
> result
> $ recon
> -----------------------------------------------------------------------
> ------
> No SSI boot modules said that they were available to run. This should
> not happen.
> -----------------------------------------------------------------------
> ------
> -----------------------------------------------------------------------
> ------
> I'm confused -- the boot SSI module said that it wasn't able to
> initialize properly. Aborting in despair.
> -----------------------------------------------------------------------
> ------
> $ lamboot -d
> n-1<9304> ssi:boot: Opening
> n-1<9304> ssi:boot: opening module globus
> n-1<9304> ssi:boot: initializing module globus
> n-1<9304> ssi:boot:globus: globus-job-run not found, globus boot will
> not run
> n-1<9304> ssi:boot: module not available: globus
> n-1<9304> ssi:boot: No boot moduless available!
> -----------------------------------------------------------------------
> ------
> No SSI boot modules said that they were available to run. This should
> not happen.
> -----------------------------------------------------------------------
> ------
> Can somebody help me out,
> Thanks,
> Hemanth
>
> Do you Yahoo!?
> Yahoo! Mail - 50x more storage than other
> providers!_______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
