Hahaha, clock skew :( Don't hold your breath, I need to resync the WNs...
I guess that could explain it now, I'll report back soon.
Szabolcs
On Thu, 30 Oct 2008, Hernath Szabolcs wrote:
> Dear List,
>
> I have a problem with the (supposedly) automatic proxyrenewal feature of our
> new glite-WMS service. Since I did not find any hints in GocWiki or
> elsewhere, I am posting here. The situation is as follows:
>
> 1. MyProxy is running fine. It recognizes the WMS as an authorized renewer.
>
> 2. WMS is running fine (including glite-proxy-renewd)
>
> 3. Longterm proxy is created with 'myproxy-init -d -n'
>
> 4. VOMS proxy is created with '-valid=1:30' option
>
> 5. Job is submitted with 'glite-wms-job-submit -a'. The JDL contains the
> MyProxyServer directive, and the job needs a lot more than 90 minutes to
> execute
>
> 6. The job fails sortly after the original VOMS proxy expires :(
>
>
> I can see in the MyProxy logs:
>
> -----------------------------------------------------------------
> Oct 29 12:09:07 grid153 myproxy-server[16118]: Authenticated client
> /C=HU/O=KFKI RMKI CA/OU=KFKI RMKI/CN=host/grid150.kfki.hu
> Oct 29 12:09:07 grid153 myproxy-server[16118]: applying
> trusted_retrievers policy
> Oct 29 12:09:07 grid153 myproxy-server[16118]: applying
> authorized_retrievers policy
> Oct 29 12:09:07 grid153 myproxy-server[16118]: applying authorized_renewers
> policy
> Oct 29 12:09:07 grid153 myproxy-server[16118]: sending
> MYPROXY_AUTHORIZATION_RESPONSE
> Oct 29 12:09:07 grid153 myproxy-server[16118]: client chose X509_certificate
> Oct 29 12:09:07 grid153 myproxy-server[16118]: renewal authentication
> succeeded
> Oct 29 12:09:07 grid153 myproxy-server[16118]: Received GET request from
> /C=HU/O=KFKI RMKI CA/OU=KFKI RMKI/CN=host/grid150.kfki.hu
> Oct 29 12:09:07 grid153 myproxy-server[16118]:
> Owner: /C=HU/O=KFKI RMKI CA/OU=KFKI RMKI/CN=Hernath Szabolcs HUNGRID
> Oct 29 12:09:07 grid153 myproxy-server[16118]:
> Username: /C=HU/O=KFKI RMKI CA/OU=KFKI RMKI/CN=Hernath Szabolcs HUNGRID
> Oct 29 12:09:07 grid153 myproxy-server[16118]: Location:
> /var/myproxy/e4f867e5831db0fc543bec66c5d23334.creds
> Oct 29 12:09:07 grid153 myproxy-server[16118]: Requested lifetime:
> 36000 seconds
> Oct 29 12:09:07 grid153 myproxy-server[16118]: Max. delegation lifetime:
> 43200 seconds
> Oct 29 12:09:07 grid153 myproxy-server[16118]: Sending OK response to client
> /C=HU/O=KFKI RMKI CA/OU=KFKI RMKI/CN=host/grid150.kfki.hu
> Oct 29 12:09:07 grid153 myproxy-server[16118]: retrieving proxy
> Oct 29 12:09:08 grid153 myproxy-server[16118]: Delegating credentials for
> /C=HU/O=KFKI RMKI CA/OU=KFKI RMKI/CN=Hernath Szabolcs HUNGRID lifetime=36000
> Oct 29 12:09:08 grid153 myproxy-server[16118]: Sending OK response to client
> /C=HU/O=KFKI RMKI CA/OU=KFKI RMKI/CN=host/grid150.kfki.hu
> Oct 29 12:09:08 grid153 myproxy-server[16118]: Client
> /C=HU/O=KFKI RMKI CA/OU=KFKI RMKI/CN=host/grid150.kfki.hu disconnected
> --------------------------------------------------------------------------
>
> every 5(!) minutes during the jobs lifecycle...
>
>> From the WMS logs I have (at corresponding times):
>
> --------------------------------------------------------------------------
> Oct 29 11:54:01 grid150 glite-proxy-renewd[15693]: VOMS_Contact() failed
> --------------------------------------------------------------------------
>
> And after 3 or 4 instances, this message extends to:
>
> --------------------------------------------------------------------------
> Oct 29 12:09:04 grid150 glite-proxy-renewd[13435]: VOMS_Contact() failed
> Oct 29 12:09:04 grid150 glite-proxy-renewd[15692]: Remaining proxy lifetime
> fell below the value of the Condor limit!
> --------------------------------------------------------------------------
>
> I assume, the renewal process runs OK from the MyProxy point of view, but
> somehow does not satisfy the WMS...
>
> What am I missing? Any help is appreciated,
> Cheers
>
> Szabolcs
>
|