[Swift-devel] persistent coaster service

[Mihael Hategan]

On Thu, 2010-08-26 at 15:00 -0600, wilde at mcs.anl.gov wrote:
> I have 2 questions on the persistent coaster service:
> 
> 1) is -nosec working right?

I haven't tested it, so I make no such claims.

>   I get this when I specify it:
> 
> bri$ coaster-service -port 55123 -nosec
> Error loading credential: [JGLOBUS-5] Proxy file (/tmp/x509up_u1031) not found.
> Error loading credential
> org.globus.gsi.GlobusCredentialException: [JGLOBUS-5] Proxy file (/tmp/x509up_u1031) not found.
> 	at org.globus.gsi.GlobusCredential.<init>(GlobusCredential.java:114)
> 	at org.globus.gsi.GlobusCredential.reloadDefaultCredential(GlobusCredential.java:590)
> 	at org.globus.gsi.GlobusCredential.getDefaultCredential(GlobusCredential.java:575)
> 	at org.globus.cog.abstraction.coaster.service.CoasterPersistentService.main(CoasterPersistentService.java:73)
> bri$
> 
> I would have expected it to fully eliminate the need for a proxy, no?

Yes. Something seems messed up indeed.

> 
> 2) Following up on Allan's last question, can you clarify:
> 
> When you start a persistent coaster service do you have the option of either:
> 
> (a) the Swift client starts workers per the sites.xml profile settings or
> 
> (b) the user starts the workers manually, connecting to the persisten server, when you specify workerManager passive in the Globus profile tag:
> 
>   <profile namespace="globus"> key="workerManager">passive</profile>

Yes. That looks correct.

Mihael