Thanks Peter, that's good enough to check:
edg-gridftp-ls --proxy $X509_USER_PROXY.1
gsiftp://fal-pygrid-03.lancs.ac.uk/mnt
cdrom
floppy
works where the proxy chain length is only 1:
voms-proxy-info -identity -file $X509_USER_PROXY.1
/C=UK/O=eScience/OU=CLRC/L=RAL/CN=chris dteam brew/CN=proxy
but with a longer chain length it fails:
voms-proxy-info -identity -file $X509_USER_PROXY.2
/C=UK/O=eScience/OU=CLRC/L=RAL/CN=chris dteam brew/CN=proxy/CN=proxy
edg-gridftp-ls --proxy $X509_USER_PROXY.2
gsiftp://fal-pygrid-03.lancs.ac.uk/mnt
error the server sent an error response: 425 425 Can't open data
connection. data_connect_failed() failed: an authentication operation
failed.
error the server sent an error response: 425 425 Can't open data
connection. data_connect_failed() failed: an authentication operation
failed.
Unfortunatly the proxies you get back from the myproxy server have
longer chains:
heplnx101 - ~ $ myproxy-init -l chrsibrew -r "chris dteam brew"
Your identity: /C=UK/O=eScience/OU=CLRC/L=RAL/CN=chris dteam brew
Enter GRID pass phrase for this identity:
Creating proxy .....................................................
Done
Proxy Verify OK
Your proxy is valid until: Tue Oct 10 12:56:08 2006
Enter MyProxy pass phrase:
Verifying password - Enter MyProxy pass phrase:
A proxy valid for 168 hours (7.0 days) for user chrsibrew now exists on
lcgrbp01.gridpp.rl.ac.uk.
heplnx101 - ~ $ voms-proxy-info -subject
/C=UK/O=eScience/OU=CLRC/L=RAL/CN=chris dteam brew/CN=proxy
heplnx106 - ~ $ myproxy-get-delegation -l chrsibrew ; voms-proxy-init
--voms dteam: --key $X509_USER_PROXY --cert $X509_USER_PROXY
Enter MyProxy pass phrase:
A proxy has been received for user chrsibrew in /tmp/x509up_u24431
Your identity: /C=UK/O=eScience/OU=CLRC/L=RAL/CN=chris dteam
brew/CN=proxy/CN=proxy/CN=proxy
Creating temporary proxy
........................................................ Done
Contacting voms.cern.ch:15004
[/C=CH/O=CERN/OU=GRID/CN=host/voms.cern.ch] "dteam" Done
Creating proxy ................................ Done
Warning: your certificate and proxy will expire Wed Oct 4 00:56:38 2006
which is within the requested lifetime of the proxy
heplnx106 - ~ $ voms-proxy-info -identity
/C=UK/O=eScience/OU=CLRC/L=RAL/CN=chris dteam
brew/CN=proxy/CN=proxy/CN=proxy
Which means you cannot use them to submit jobs!
Thanks,
Chris.
> -----Original Message-----
> From: Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of Peter Love
> Sent: 03 October 2006 12:46
> To: [log in to unmask]
> Subject: Re: Any classic SEs left running?
>
> fal-pygrid-03.lancs.ac.uk is still running but may disappear
> without notice :)
>
> Brew, CAJ (Chris) ([log in to unmask]) wrote:
> > Hi,
> >
> > Is anyone still running a "Classic" SE? I've got a problem
> submitting
> > jobs using delegated VOMS proxies that I'm pretty convinced
> boils down
> > to the edg-gridftpd service running on the RB and CE not accepting
> > VOMS proxies with a proxy chain length above about 2.
> >
> > If I recall correctly the classic SE also ran edg-gridftpd so if
> > anyones still running one I can test my theory against that.
> >
> > Thanks,
> > Chris.
>
|