 |
 |
Ok, just to reiterate, here is the sequence of events as I understand it: source /vols/grid/glite/ui/3.2.10-1/external/etc/profile.d/grid-env.sh voms-proxy-init -valid 24:00 --voms vo.londongrid.ac.uk myproxy-init -n -d glite-wms-job-submit -a -o mastercodegrid.log glite-run.imperial.jdl yes ? The UI will default to lcgrbp01.gridpp.rl.ac.uk, but I just added MyProxyServer = "lcgrbp01.gridpp.rl.ac.uk"; (I assume this machine know how to deal with londongrid ?) in the jdl file for good measure. Can I just renew this proxy periodically ? Not a cron job, but let's say, I come in every morning , check out last nights crop and then run the above commands again ? Thanks, Daniela On 18 November 2011 10:10, Daniela Bauer <[log in to unmask]> wrote: > Hi Stuart, > > I tried the trick with the longer proxy before I posted this: > lx05:grid_mastercode_nov11 :~] voms-proxy-init -valid 48:00 --voms > vo.londongrid.ac.uk > Enter GRID pass phrase: > Your identity: /C=UK/O=eScience/OU=Imperial/L=Physics/CN=daniela bauer > Creating temporary proxy .................... Done > Contacting voms.gridpp.ac.uk:15021 > [[log in to unmask]] > "vo.londongrid.ac.uk" Done > > Warning: voms.gridpp.ac.uk:15021: The validity of this VOMS AC in your > proxy is shortened to 86400 seconds! > > Creating proxy ...................................... Done > Your proxy is valid until Sun Nov 20 10:05:58 2011 > > My life would be so much easier if I could just get 4 day voms proxies > and be done with it. > > Cheers, > Daniela > > On 17 November 2011 17:21, Stuart Purdie <[log in to unmask]> wrote: >> >> On 17 Nov 2011, at 17:02, Daniela Bauer wrote: >> >>> Currently they mostly get away with a 24 h proxy made like this: >>> voms-proxy-init -valid 24:00 --voms vo.londongrid.ac.uk >>> >>> Unfortunately some of the jobs need more time, either because they >>> queue for a while or because they've hit a particularly exciting bit >>> of phase space. >> >> Are you sure you can't just create a longer proxy? MyProxy is ok for what it does, but it's another layer of complications, and therefore more things that can go wrong. For a big VO, that's often a good trade off, but for a smaller VO, sometimes simplicity is better. Infrequent users don't really get much of a penalty for longer proxies too. >> >> If memory serves, at one point the default maximum VOMS attribute length was 4 days, so you might well find that you can have a VOMS proxy that long. Note that you'll need to examine the VOMS attributes separatly for the main proxy expiry, because they have a _separate_ lifetime set on them. >> >> Try asking for a long lived ( e.g. 7 days) voms proxy, and see what the voms-attributes length end up as. That's as long as it'll go. If it's 48 hours, that might just be enough, whilst keeping it simple. >> >> > > > > -- > ----------------------------------------------------------- > [log in to unmask] > HEP Group/Physics Dep > Imperial College > Tel: +44-(0)20-75947810 > http://www.hep.ph.ic.ac.uk/~dbauer/ > -- ----------------------------------------------------------- [log in to unmask] HEP Group/Physics Dep Imperial College Tel: +44-(0)20-75947810 http://www.hep.ph.ic.ac.uk/~dbauer/