Hello,
I was able to submit and execute jobs with my certificate to the previous
version of TB without problems (LHCb VO).
With the current version (v1.2.1) I still can submit jobs, e.g.,
>> dg-job-submit Hello.jdl
produces the output:
Your identity: /O=Grid/O=UKHEP/OU=physics.ox.ac.uk/CN=Alexander Soroko
Enter GRID pass phrase for this identity:
Creating proxy ....................................... Done
Your proxy is valid until Tue Sep 3 00:35:06 2002
**** Success: UI_PROXY_CREATED ****
Proxy certificate has been successfully created
Connecting to host lxshare0382.cern.ch, port 7771
Logging to host lxshare0382.cern.ch, port 15830
****************************************************************************
****
*************************
JOB SUBMIT OUTCOME
The job has been successfully submitted to the Resource Broker.
Use dg-job-status command to check job current status. Your job identifier
(dg_jobId) is:
- https://lxshare0382.cern.ch:7846/163.1.244.23/113508135017058?
lxshare0382.cern.ch:7771
****************************************************************************
****
*************************
However, the dg-job-status command:
>> dg-job-status https://lxshare0382.cern.ch:7846/163.1.244.23/1135081350
17058'?'lxshare0382.cern.ch:7771
gives the output:
Retrieving Information from LB server https://lxshare0382.cern.ch:7846
Please wait: this operation could take some seconds.
*************************************************************
BOOKKEEPING INFORMATION:
Printing status info for the Job :
https://lxshare0382.cern.ch:7846/163.1.244.23
/113508135017058?lxshare0382.cern.ch:7771
---
dg_JobId =
https://lxshare0382.cern.ch:7846/163.1.244.23/11350
8135017058?lxshare0382.cern.ch:7771
Status = Aborted
Last Update Time (UTC) = Mon Sep 2 11:35:10 2002
Status Reason = No matching resource found
Warning : matchmaking process reported:
- Search on InformationIndex: no match while
authorizing
user
Job Owner
= /O=Grid/O=UKHEP/OU=physics.ox.ac.uk/CN=Alexander So
roko
Status Enter Time (UTC) = Mon Sep 2 11:35:10 2002
*************************************************************
As you can see the job is aborted because of the problem with authorization
at InformationIndex.
So, what is the reason and how can I resolve the problem?
With best regards,
Alexander
