Hi Sérgio,
the VOMS extention of the proxy is limited by the VOMS server, 48h in your case what is the default.
If you have access to the VOMS server you can it change here:
/opt/glite/etc/voms/hone/voms.conf
the important line is the one "--timeout=NNNNN", where NNNNN is the maximum VOMS lifetime of the VOMS.
Note that the VOMS service needs to be restarted, if I remember correctly.
The voms-proxy-init command has an option -vomslife HH:MM, which steers the lifetime of the VOMS on client side. But of course the user cannot exceed the maximum time offered by the server.
Good luck,
Christoph
On Tue, 24 Jul 2007 16:30:01 +0100
Sérgio Afonso <[log in to unmask]> wrote:
>
>
> Hello all,
>
> We have a user that is trying to perform a 48 hour computation in
> one of our clusters but his proxy expires before the end of the job
> and he gets this message:
>
> *************************************************************
> BOOKKEEPING INFORMATION:
>
> Status info for the Job : https://rb02.lip.pt:9000/J7jeVFVQ4Wr5GxRZpW9y8A
> Current Status: Aborted
> Status Reason: Job proxy is expired.
> Destination: grid001.fc.up.pt:2119/jobmanager-lcgsge-swetest
> reached on: Fri Jul 20 04:04:09 2007
> *************************************************************
>
> If he tries to increase the life-time of the proxy with the command:
>
> voms-proxy-init --voms swetest -valid 96:00
>
> He gets this warning:
>
> Warning: swevo.ific.uv.es:14000: validity shortened to 86400 seconds!
>
> Any idea on how to overcome this problem?
>
> Thanks in advance,
>
> Sérgio Afonso
>
>
>
--
+-----------------------------------+
| Christoph Wissing DESY - IT |
| E-Mail: [log in to unmask] |
| Phone: +49(0)40/8998-4122 |
+-----------------------------------+
|