-
|
Dear all, Could you please tell me which mechanism is responsible for the renewal of payload proxies, is it the ProxyRenewalAgent? At one site payload proxies get expired after 12 hours : PEM file has expired /tmp/tmpnmrlzdpo is not valid after 2025-10-29 21:43:00 while at another site they don't. So I guess that there is some different configuration at the 2 sites. Looking at the pilot logs I found that at one site (where proxies get expired) there is the following variable set: MYPROXY_SERVER while at the other is not. Could it be the cause of the renewal problem? As an additional information, but I don't know if it's relevant, we have the following configuration for the ProxyRenewalAgent: Thank you for your help, Luisa |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 9 replies
-
|
Hi, The Modify at will. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @fstagni Thank you for the explanations. I will try to change this value /Registry/DefaultProxyLifeTime. But I don't really understand how at one site there are successfull jobs lasting more than 12 hours while at another I see the PEM expired message after 12 hours.... Any idea? |
Beta Was this translation helpful? Give feedback.
-
|
I see. So let's see if my change in /Registry/DefaultProxyLifeTime is enough. I will let you know. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @fstagni I've set: /Registry/DefaultProxyLifeTime = 86400 but I still see proxy generated with 12 hours of lifetime, see below: Making again jobs fail. Any idea? Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @arrabito, here we are talking about the user proxy downloaded by the I see that the user proxy could be renewed in DIRAC/src/DIRAC/Resources/Computing/ComputingElement.py Lines 359 to 461 in 106cca5 Can you spot the logs in your pilot outputs to compare them? Such as: |
Beta Was this translation helpful? Give feedback.
-
|
I've forgot to mention that for the last testing job, as it was very short I don't know if it had worked well with a long job. timeleft : 11:59:57 in the Payload proxy information, despite the setting:
but I don't know if this is expected. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @fstagni @aldbr, after some investigations with the help of @aldbr we have discovered that there is a limit of 12 hours for the proxy duration imposed by our IAM server. That's why despite what we set for:
the max duration is 12 hours. Nevertheless the payload proxy should have been renewed by Now the strange thing is that I've submitted another set of jobs, after changing :
and only when using
and every 20 minutes (which corresponds to our
As PoolCE uses in turn InProcessCE, I don't really understand the reason why the proxy renewal didn't work in that case. Any idea? |
Beta Was this translation helpful? Give feedback.
-
|
Just to let you know that we managed to get an extension in the proxy duration from our IAM server.
configuration is effective and visible in the pilot log: Apart from the fact that I don't understand why the I cannot see logs concerning proxy renewal when using LocalCEType=Pool, I would consider this discussion as solved. Thanks for your help. |
Beta Was this translation helpful? Give feedback.
Just to let you know that we managed to get an extension in the proxy duration from our IAM server.
Now that the limitation is much higher (7 days) I confirm that the :
Registry/DefaultProxyLifeTimeconfiguration is effective and visible in the pilot log: