#231 robot proxy for 48 hours

[Mahdi]

Hi,

We are using workflows with robot proxy, and would like to attach proxies of 48 hours long to submitted jobs. We configured the gLite pulgin of DCI-Bridge and set the life-time of the proxies to be 48 hours. We get the following error on the workflows:

Add VOMS - error. The remaining lifetime of the proxy in the submission time: 24:10:16
This error is cached. The cache is updated within 10 minutes.It was not possible to renew the proxy at the DCI-Bridge.

Add VOMS - error. The remaining lifetime of the proxy in the submission time: 24:10:16

It was not possible to query the status.
* Error: UI_PROXY_EXPIRED *
Proxy certificate validity expired.

Resuming the workflow results immediately in an error like this:

voms-proxy-init -ignorewarn -timeout 30 -valid 48:00 -voms vlemed: -noregen -out x509up
failed, exit code: 1
Your identity: /O=dutchgrid/O=robots/O=amc/CN=Robot: grid client - Silvia Olabarriaga (vlemed)/CN=proxy/CN=proxy/CN=proxy/CN=proxy
Contacting voms.grid.sara.nl:30003 [/O=dutchgrid/O=hosts/OU=sara.nl/CN=voms.grid.sara.nl] "vlemed" Done
Creating proxy .............................................. Done

Preparation of the proxy for VO vlemed failed.
Add VOMS - error. The remaining lifetime of the proxy in the submission time: 36:25:7

Regards
Mahdi
AMC, Amsterdam

[Gabor Hermann]

Dear Mahdi,
as well as I see the same technique can be used for the automatic proxy renewal in the robot certificate case as in the base one:

1. The DN identified account of the owner of the (robot) certificate must be placed in a MyProxy Server visible by the CE where the job runs.
   (See Chapter "10.2.1.1.2 Special case for the automatic proxy renewal" of the User manual )

2. The url of the MyProxy Server mentioned in (1) must be referenced in the "MyProxyServer" tag of the JDL of the job mentioned in (1)
   (See Chapter "3.2.3 The Concrete/Configure/JDL-RSL Tab" pages 161-162 ibid.)

[Mahdi]

Dear Gabor,

Thanks for your reply and your pointers to help our system to get back to
production. Let me clarify. Those settings are in place and the system has
been working properly. Since there was recently an issue on the myproxy
server regarding the renewal, we want to create a longer proxy from the
beginning that would (in most of the cases) take away the need for renewal.

By looking at the logs, we changed 48 to 24 and it is working now. Clearly
somewhere there is a number 24 hardcoded. So it is not that urgent for us
anymore. Anyway, I am just reporting a bug (or what looks to me like a bug
in the way gUSE creates a delegation of the robot proxy). It would be good
to look into it I suppose.

Regards
Mahdi

On Thu, Jun 12, 2014 at 6:57 AM, Gabor Hermann gaborhermann@users.sf.net
wrote:

Dear Mahdi,
is well as I see the same technique can be used for the automatic proxy
renewal in the robot certificate case as in the base one:

1.

The DN identified account of the owner of the (robot) certificate must
be placed in a MyProxy Server visible by the CE where the job runs.
(See Chapter "10.2.1.1.2 Special case for the automatic proxy renewal"
of the User manual )
2.

The url of the MyPoroxy Server mentioned in (1) must be referenced in
the "MyProxyServer" tag of the JDL of the job mentioned in (1)
(See Chapter "3.2.3 The Concrete/Configure/JDL-RSL Tab" pages 161-162
ibid.)

---

• [bugs:#231] http://sourceforge.net/p/guse/bugs/231/ robot proxy for 48
  hours*

Status: open
Group: 3.6.1
Created: Wed Jun 11, 2014 01:49 PM UTC by Mahdi
Last Updated: Wed Jun 11, 2014 01:49 PM UTC
Owner: nobody

Hi,

We are using workflows with robot proxy, and would like to attach proxies
of 48 hours long to submitted jobs. We configured the gLite pulgin of
DCI-Bridge and set the life-time of the proxies to be 48 hours. We get the
following error on the workflows:

Add VOMS - error. The remaining lifetime of the proxy in the submission
time: 24:10:16
This error is cached. The cache is updated within 10 minutes.It was not
possible to renew the proxy at the DCI-Bridge.

Add VOMS - error. The remaining lifetime of the proxy in the submission
time: 24:10:16

It was not possible to query the status.
** Error: UI_PROXY_EXPIRED **
Proxy certificate validity expired.

Resuming the workflow results immediately in an error like this:

voms-proxy-init -ignorewarn -timeout 30 -valid 48:00 -voms vlemed:
-noregen -out x509up
failed, exit code: 1
Your identity: /O=dutchgrid/O=robots/O=amc/CN=Robot: grid client - Silvia
Olabarriaga (vlemed)/CN=proxy/CN=proxy/CN=proxy/CN=proxy
Contacting voms.grid.sara.nl:30003 [/O=dutchgrid/O=hosts/OU=
sara.nl/CN=voms.grid.sara.nl] "vlemed" Done
Creating proxy .............................................. Done

Preparation of the proxy for VO vlemed failed.
Add VOMS - error. The remaining lifetime of the proxy in the submission
time: 36:25:7

Regards
Mahdi
AMC, Amsterdam

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/guse/bugs/231/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/