Hi Antun,
> This may definitely be a problem with glite-proxy-renewald, but it does not
> log anything else except for "Requested proxy is not registered" from time to
> time (28 such records for 26 June, and 49 records for 27 June, which is much
> less than the number of aborted jobs due to expired proxies for three users,
> each of which submitted yesterday 500 jobs). I also see some records of this type:
>
> ========
> Jun 27 03:34:43 wms glite-proxy-renewd[1905]: Error contacting MyProxy server
> for proxy ca8de204f972503496e9e2d0b2991a5e.30: ERROR from server: Credentials
> do not exist Unable to retrieve credential information
> Jun 27 03:34:43 wms glite-proxy-renewd[1904]: Remaining proxy lifetime fell
> below the value of the Condor limit!
> ========
>
> but this is OK since they are related to a user that really does not have
> credentials stored on MyProxy server. Around the time of massive abortion of
> jobs there are just several "Requested proxy is not registered" records in the
> log.
And those users do have proxies registered? Does their UI have this defined:
GT_PROXY_MODE=old
> So, this happens for all users. There is a cron job (configured by yaim) that
> checks each 5 minutes if glite daemons are working, which includes checking of
> glite-proxy-renewd. If glite-proxy-renewd is confused, can we somehow help it?
> Frequent restarts are probably not very good idea :-)
A daemon is only restarted when it is absent; its functionality is not tested.
|