Replies: 5 comments 6 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.
Uh oh!
There was an error while loading. Please reload this page.
-
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.
All reactions