Steven Timm wrote:
> 
> I have seen this problem when trying to use GT 4.0.7 as distributed
> by the Open Science Grid VDT, against several different
> globus WS hosts, also GT4.0.7 as installed by the VDT.  I believe
> that it also occurs both earlier and later than that as well.
> 
> I execute the globus-credential-delegate command as such:
> 
> bash-3.00$ globus-credential-delegate -h fermigridosg1.fnal.gov -p 9443
> steve.epr.fg1
> EPR will be written to: steve.epr.fg1
> Delegated credential EPR:
> Address: https://131.225.107.165:9443/wsrf/services/DelegationService
> Reference property[0]:
> <ns1:DelegationKey
> xmlns:ns1="http://www.globus.org/08/2004/delegationService";>9cfb1200-fe0e-11dd-8a41-fce4ea9a9810</ns1:DelegationKey>
> 
> 
> -----------------
> The delegation succeeds, it writes the EPR file almost immediately, but
> then takes five minutes to come back and give me a command line prompt.
> Has anyone else seen this, and do they know the cause?

No, never saw that before. Do all other calls take so long too, or just the
delegation calls? Does the persisted credential show up on disk
quickly on the server-side (see below for location of persisted creds)
when you delegate?

> 
> A related question--if I had root on the remote site,
> which I do, where would the copy of the proxy thus delegated be
> stored on the remote server?  I have looked throughout the server
> and don't see any evidence of proxies thus delegated, although
> I do see other proxies come and go when
> I submit a job with
> globusrun-ws -submit -J
> from the command line.
> 

The delegation service persists the delegated credentials to disk in
the persistence directory of the container (default directory is
~<containerUser>/.globus/persisted/<hostname>-<portname>/DelegationResource/<credUUID>.ser)

Only in case of job delegation Gram also generates a proxy file from the
delegated credential on disk for use by the job, and stores it in
~<localUser>/.globus/gram_job_proxy_<credUUID>.
For staging delegation no proxy file is written.

Both the persisted delegated credential and the proxy file generated
by Gram in case of job delegation are removed, when the delegated credential
is destroyed.

Martin

> Steve Timm
> 
> 


Reply via email to