Asif Osman wrote:
> Hi Maarten,
>
> 1) The user certificate works, if job submition is not restricted to CE.pakgrid.org.pk. So, this might not be a problem.
Can the user do this (use the "-dbg" flag to get more details, if desired):
globus-url-copy gsiftp://CE.pakgrid.org.pk/etc/hosts -
If not, look at the generic authentication problems discussed in the Wiki entry
quoted below.
Can the user do this (from a UI with inbound connectivity, e.g. lxplus.cern.ch):
globus-job-run CE.pakgrid.org.pk /bin/hostname
If not, look at the job submission authentication problems (e.g. LCAS/LCMAPS).
> 2) /var/log/globus-gatekeeper.log file does not give more info than displayed with edg-job-status command:
>
>
>>>Status Reason: 7 authentication failed: GSS Major Status:
>>>Authentication Failed GSS Minor Status Error Chain: init.c:499:
>>>globus_gss_assist_init_sec_context_async: Error during context
>>>initialization init_sec_context
>>
>
>
> Cheers,
> Asif Osman
>
>
>
>
> -----Original Message-----
> From: LHC Computer Grid - Rollout on behalf of Maarten Litmaath
> Sent: Thu 3/17/2005 10:50 AM
> To: [log in to unmask]
> Cc:
> Subject: Re: [LCG-ROLLOUT] Error while executing jobs on PAKGRID-LCG2!
>
> Maarten Litmaath wrote:
>
>
>>Asif Osman wrote:
>>
>>
>>>Hi,
>>>
>>>We are getting following error while executing jobs on our
>>>CE.pakgrid.org.pk.
>>>
>>>[lxplus062] ~/grid > edg-job-status
>>>https://lxn1177.cern.ch:9000/OTDN64Qo58vzgn2BJfPj2Q
>>>
>>>
>>>*************************************************************
>>>BOOKKEEPING INFORMATION:
>>>
>>>Status info for the Job :
>>>https://lxn1177.cern.ch:9000/OTDN64Qo58vzgn2BJfPj2Q
>>>Current Status: Ready
>>>Status Reason: 7 authentication failed: GSS Major Status:
>>>Authentication Failed GSS Minor Status Error Chain: init.c:499:
>>>globus_gss_assist_init_sec_context_async: Error during context
>>>initialization init_sec_context
>>>Destination: CE.pakgrid.org.pk:2119/jobmanager-torque-cms
>>>reached on: Thu Mar 17 09:22:05 2005
>>>*************************************************************
>>>
>>>Is it related to HOST certificates? If so how can I check the validity
>>>of Host certificates? Just like for User certificates, I can check its
>>>validity via globus-url-copy etc.
>>
>>
>>The host cert is fine, because this works for me:
>>
>>--------------------------------------------------------
>>$ globus-url-copy gsiftp://CE.pakgrid.org.pk/etc/hosts -
>># Do not remove the following line, or various programs
>># that require network functionality will fail.
>>127.0.0.1 localhost.localdomain localhost
>>203.135.53.244 CE.pakgrid.org.pk CE
>>--------------------------------------------------------
>>
>>So, it would mean that the proxy of the user who submitted the job is not
>>accepted by the CE, e.g. because the DN does not appear in the gridmap
>>file,
>>or the pool account is absent, or the CRL of the CA has expired, or the CA
>>is absent, ...
>
>
> The gatekeeper log file /var/log/globus-gatekeeper.log on the CE should show
> why the user is not allowed.
>
>
>>See the Wiki FAQ:
>>
>>
>>http://goc.grid.sinica.edu.tw/gocwiki/530_530_No_local_mapping_for_Globus_ID
>>
>
|