Apologies for taking so long to answer this. :-(
Arf -- if you're right, we've got two problems in 7.1.1:
- globus boot SSI not working. Can you post the full output of
"lamboot -d" with the 7.1.1 installation?
- lamgrow failing. Can you post a repeatable sequence of events that
causes lamgrow to seg fault? That would be most helpful in helping us
identify the exact bug.
Thanks!
On Jan 18, 2005, at 4:30 PM, redirecting decoy wrote:
> Well, for the testing purposes I've uninstalled lam
> 7.1.1 and install Lam 7.0.6. Now everything works
> fine.
> So logic tells me that my globus problem must be a bug
> with Lam 7.1.1. It may be something with my system
> though. I don't know. Has anyone else made lam 7.1.1
> work with Globus ? Also, I with 7.1.1 I am getting
> segmentation faults when attempting to use lamgrow.
> It works the first few times, then it starts to seg
> fault.
>
> Anyone else have similar experiences ?
>
> -R.D.
>
> --- redirecting decoy <redirectingdecoy_at_[hidden]>
> wrote:
>
>> still having problems with this. The problem does
>> not
>> appear to be caused by globus I think. I have
>> checked
>> my globus install to correctness and did not see any
>> problems. Anyone have any ideas on this one ?
>>
>> -R.D.
>>
>>
>> --- redirecting decoy <redirectingdecoy_at_[hidden]>
>> wrote:
>>
>>> Hello all,
>>>
>>> I'm am having trouble booting lam using globus. I
>>> am
>>> using lam 7.1.1 and latest globus installed on 3
>>> different machines. I try and boot lam using the
>>> following command:
>>>
>>> lamboot -v -d -x -ssi boot globus machines.globus
>>>
>>> machines.globus looks like this:
>>>
>> ###################################################
>>> nest.public prefix=/usr/local/lam cpu=4
>> schedule=yes
>>> pa-wb-001.public prefix=/usr/local/lam cpu=2
>>> schedule=yes
>>> pa-wb-002.public prefix=/usr/local/lam cpu=2
>>> schedule=yes
>>>
>>> ################################################
>>>
>>> When I do that I get a wierd error message.
>> Lamboot
>>> tells me it was trying to run the command:
>>>
>>> /usr/local/globus/bin/globus-job-run nest.public
>>> /usr/local/lam/bin/hboot -t -c
>>> /usr/local/lam/etc/lam-conf.lamd -d -v -I "-x -H
>>> 192.168.10.100 -P 44621 -n 0 -o 0" -prefix
>>> /usr/local/lam
>>>
>>> which, when I try gives me the following error
>>>
>>>
>>
> -----------------------------------------------------------------------
> ------
>>> LAM encountered an error when invoking the library
>>> call "getenv".
>>>
>>> This is an unexpected error; we don't have much
>>> additional information
>>> here. Perhaps this Unix error message will help:
>>>
>>> Unix errno: 1268
>>> Unknown error 1268
>>>
>>>
>>
> -----------------------------------------------------------------------
> ------
>>>
>>> Does anyone know what is causing this? And how to
>>> make
>>> the error go away ?
>>>
>>> Any help would be much appreciated.
>>> Thanks much,
>>>
>>> -RD
>>>
>>>
>>> __________________________________________________
>>> Do You Yahoo!?
>>> Tired of spam? Yahoo! Mail has the best spam
>>> protection around
>>> http://mail.yahoo.com
>>> _______________________________________________
>>> This list is archived at
>>> http://www.lam-mpi.org/MailArchives/lam/
>>>
>>
>>
>>
>>
>> __________________________________
>> Do you Yahoo!?
>> Yahoo! Mail - 250MB free storage. Do more. Manage
>> less.
>> http://info.mail.yahoo.com/mail_250
>> _______________________________________________
>> This list is archived at
>> http://www.lam-mpi.org/MailArchives/lam/
>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
