Hi Martin,

> > Ah, why to the easy route if there is a complicated one...
> > Somehow I was focused on your statement "... new LSF ..." and thought
> it used
> > to work with old LSF or Fork. So maybe this:

It works fine with Fork. The old LSF is not installed anymore so I cannot
test it. As both variants (Fork and LSF) use the same notification listener
(I guess?), network configuration problems may not be the reason... 

> > To verify that: submit a job in batch/non-interactive mode and store
> > the EPR of the job. Then poll for status.

With LSF the job status remains "unsubmitted":

-bash-3.1$ globusrun-ws -submit -b -o job.epr -F
https://nimrod.med.uni-goettingen.de -Ft LSF -c /bin/date
Submitting job...Done.
Job ID: uuid:7e99a622-a061-11df-9d58-00215af48192
Termination time: 08/06/2010 07:17 GMT
-bash-3.1$ globusrun-ws -status -j job.epr
Current job state: Unsubmitted

...but with Fork it is "done".

-bash-3.1$ globusrun-ws -submit -b -o job.epr -F
https://nimrod.med.uni-goettingen.de -Ft Fork -c /bin/date
Submitting job...Done.
Job ID: uuid:8b85d1b2-a061-11df-9fb3-00215af48192
Termination time: 08/06/2010 07:17 GMT
-bash-3.1$ globusrun-ws -status -j job.epr
Current job state: Done

Do you have an explanation for that strange behavior?

Regards,
Benjamin

--

Benjamin Löhnhardt

UNIVERSITÄTSMEDIZIN GÖTTINGEN
GEORG-AUGUST-UNIVERSITÄT 
Abteilung Medizinische Informatik
Robert-Koch-Straße 40
37075 Göttingen
Briefpost 37099 Göttingen
Telefon +49-551 / 39-22842
[email protected]
www.mi.med.uni-goettingen.de



Reply via email to