Hi,

	Sorry again for the late answers (multitasking) I just sent the tests  
that Gonçalo suggested:

 > LIP-LISBON

[espinal@ui07 GridTesting]$ edg-job-submit test.jdl

Selected Virtual Organisation name (from proxy certificate extension):  
atlas
Connecting to host rb01.pic.es, port 7772
Logging to host rb01.pic.es, port 9002


*********************************************************************************************
                                JOB SUBMIT OUTCOME
  The job has been successfully submitted to the Network Server.
  Use edg-job-status command to check job current status. Your job  
identifier (edg_jobId) is:

  - https://rb01.pic.es:9000/wNzJaLkxj_tpYX7XY0MbRA


*********************************************************************************************
with:

[espinal@ui07 GridTesting]$ cat test.jdl
Executable = "/bin/echo";
Arguments = "Hello";
StdOutput = "std.out";
StdError = "std.err";
OutputSandbox = {"std.out","std.err"};
Requirements = other.GlueCEUniqueId=="ce02.lip.pt:2119/jobmanager- 
lcgsge-atlasgrid";

*************************************************************
BOOKKEEPING INFORMATION:

Status info for the Job : https://rb01.pic.es:9000/wNzJaLkxj_tpYX7XY0MbRA
Current Status:     Scheduled
Status Reason:      Job successfully submitted to Globus
Destination:        ce02.lip.pt:2119/jobmanager-lcgsge-atlasgrid
reached on:         Thu Jan 17 11:54:25 2008
*************************************************************

Job terminated OK.

[espinal@ui07 GridTesting]$ edg-job-status https://rb01.pic.es:9000/wNzJaLkxj_tpYX7XY0MbRA


*************************************************************
BOOKKEEPING INFORMATION:

Status info for the Job : https://rb01.pic.es:9000/wNzJaLkxj_tpYX7XY0MbRA
Current Status:     Done (Success)
Exit code:          0
Status Reason:      Job terminated successfully
Destination:        ce02.lip.pt:2119/jobmanager-lcgsge-atlasgrid
reached on:         Thu Jan 17 12:15:36 2008
*************************************************************



 > CERN:

[espinal@ui07 GridTesting]$ edg-job-submit test2.jdl

Selected Virtual Organisation name (from proxy certificate extension):  
atlas
Connecting to host rb01.pic.es, port 7772
Logging to host rb01.pic.es, port 9002


*********************************************************************************************
                                JOB SUBMIT OUTCOME
  The job has been successfully submitted to the Network Server.
  Use edg-job-status command to check job current status. Your job  
identifier (edg_jobId) is:

  - https://rb01.pic.es:9000/kgYGo3Ucu85IadW2jQ_8BQ


*********************************************************************************************

with:

[espinal@ui07 GridTesting]$ cat test2.jdl
Executable = "/bin/echo";
Arguments = "Hello";
StdOutput = "std.out";
StdError = "std.err";
OutputSandbox = {"std.out","std.err"};
Requirements = other.GlueCEUniqueId=="ce101.cern.ch:2119/jobmanager- 
lcglsf-grid_2nh_atlas";

*************************************************************
BOOKKEEPING INFORMATION:

Status info for the Job : https://rb01.pic.es:9000/kgYGo3Ucu85IadW2jQ_8BQ
Current Status:     Scheduled
Status Reason:      Job successfully submitted to Globus
Destination:        ce101.cern.ch:2119/jobmanager-lcglsf-grid_2nh_atlas
reached on:         Thu Jan 17 11:55:45 2008
*************************************************************

Still scheduled:

*************************************************************
BOOKKEEPING INFORMATION:

Status info for the Job : https://rb01.pic.es:9000/kgYGo3Ucu85IadW2jQ_8BQ
Current Status:     Scheduled
Status Reason:      Job successfully submitted to Globus
Destination:        ce101.cern.ch:2119/jobmanager-lcglsf-grid_2nh_atlas
reached on:         Thu Jan 17 11:55:45 2008
*************************************************************


Then the problem seems to be the interaction of  the CONDOR layer  
(condor-6.9.3-1) I'm using for sending the pilots and the glite-CE  
3.1, right ?


Let me thank all of you once again and apologies for not following the  
thread in "real-ltime".

Cheers,
	Xavi.



On Jan 16, 2008, at 6:30 PM, Gonçalo Borges wrote:

> Hi Stephen and Xavier,
>
> For a final clarification...
>
> Xavier, can you submit a job using glite-wms-job-submit (or edg.job- 
> submit) via WMS (or RB) starting proxies and ACs from the standard  
> UI where globus-job-run is OK for ce02.lip.pt and ce101.cern.ch?
>
> You should use a Requirement expression in your JDL
> Requirements = (other.GlueCEInfoHostName == "ce02.lip.pt");
>
> Cheers
> Goncalo
>
> Burke, S (Stephen) wrote:
>> LHC Computer Grid - Rollout
>>> [mailto:[log in to unmask]] On Behalf Of Gonçalo Borges  
>>> said:
>>> Nevertheless, from Xavi tests, his jobs failed both at ce02.lip.pt  
>>> and ce101.cern.ch when submitted from the same UI as his pilot jobs.
>>> From standard UI everything is OK at both CEs. This points to  
>>> something incorrect in the pilot jobs UI which prevents things to  
>>> properly interact with lcg-CE gLite 3.1.
>>>
>>
>> I don't think so, I doubt the pilot jobs are being submitted with  
>> globus-job-run! I still think the most likely case is that you're  
>> seeing errors related to an old proxy with the expired AC and not  
>> the newly-created one. (If the jobs go through a WMS, is it using a  
>> single delegated proxy, and if so was it replaced?)
>>
>> Stephen
>>
>> PS I seem to remember that proxy renewal on the WMS only looked at  
>> the overal proxy lifetime and not the ACs, although I don't know if  
>> that's still true.
>>