Dear Maarten,
>>>Hello everybody,
>>>
>>>I have a problem with submitting a job through the LCG API. Each time I
>>>get the following error message:
>>>
>>>
>>>JobOperationException: The Operation is not allowed: Unable to perform
>>>edg_wll_RegisterJobSync at: gridui.atlantis.ugent.be:9002
>>>Resource temporarily unavailable (Resource temporarily unavailable -
>>>from locallogger )Unable to perform edg_wll_RegisterJobSync at:
>>>gridui.atlantis.ugent.be:9002
>>>Resource temporarily unavailable (Resource temporarily unavailable -
>>>from locallogger )
>>> at Job.cpp Line: 671 Method: Job::nsSubmit()
>>> at Job.cpp Method: Job::nsSubmit()
>>> at Job.cpp Method: Job::submit(const string& , const string& )
>>>The Operation is not allowed: Unable to perform
>>>edg_wll_RegisterJobSync at: gridui.atlantis.ugent.be:9002
>>>Resource temporarily unavailable (Resource temporarily unavailable -
>>>from locallogger )Unable to perform edg_wll_RegisterJobSync at:
>>>gridui.atlantis.ugent.be:9002
>>>Resource temporarily unavailable (Resource temporarily unavailable -
>>>from locallogger )
>>>
>>>
>>>However if I just use the command line interface everything works fine.
>>>Has anybody ever had such a problem?
>>>
>>>
>>I suppose the API usage is incorrect: are you sure the code initializes
>>all the necessary variables properly? The command line utilities take
>>various definitions from /opt/edg/etc/edg_wl_ui_cmd_var.conf and
>>/opt/edg/etc/$VO/edg_wl_ui.conf; with the API you may have to do that
>>explicitly. Which API documentation are you using?
>>
>>
>
>For example, when I put the following in a local copy of edg_wl_ui.conf:
>
> LBAddresses = "localhost.localdomain:9000";
>
>I get a similar error using edg-job-submit:
>
>---------------------------------------------------------------------------
>Selected Virtual Organisation name (from --config-vo option): dteam
>Connecting to host lxb1911.cern.ch, port 7772
>Logging to host lxb1911.cern.ch, port 9002
>**** Error: API_NATIVE_ERROR ****
>Error while calling the "edg_wll_RegisterJobSync" native api
>Unable to Register the Job:
>https://localhost.localdomain:9000/WnQD-L2KmhWw6h2PYf9zpA
>to the LB logger at: lxb1911.cern.ch:9002
>Resource temporarily unavailable (Resource temporarily unavailable - from
>locallogger)
>---------------------------------------------------------------------------
>
>The WP1 manual says that "localhost:9000" is the default for LBAddresses;
>I found that putting an unknown host or unconnected port results in the
>same error message.
>
>
First of all thank you for your help! I found out that my LBAddress was
indeed specified incorrectly.
>>I would suggest also trying with a different RB, e.g. lxn1188.cern.ch,
>>but I notice your RB does not even enable the "dteam" VO, so I wonder
>>what status the University of Gent exactly has in EGEE or LCG?
>>This list is intended to provide support for LCG/EGEE sites only...
>>
>>
>
>To receive assistance from LCG/EGEE, a site must make some resources
>available to LCG/EGEE, even when it is only a CE with a single WN;
>LCG/EGEE must be able to put the site on the official map, such that
>we can show the EU where we spent our efforts.
>
Sorry, I wasn't aware of that.
A couple of months ago our university (UGent) and some other
universities in Belgium set up a hardware & software infrastructure for
running LCG middleware. The idea is first to test this "Belgian" grid
extensively and then to integrate it into a lager grid infrastructure
(EGEE?). However, I'm just a PhD student interested in grid technologies
as such, so I don't posses information about the exact plans around the
Belgian grid. But I know for sure that our grid infrastructure should be
tested very well before it can be integrated somewhere, and this is
sometimes difficult to do without any help...
Best regards,
Masha
|