On Oct 28, 2008, at 7:58 PM, Yoichi Takayama wrote:
[EMAIL PROTECTED] ~]# su - yoichi
[EMAIL PROTECTED] ~]$ myproxy-logon -s grid2
Enter MyProxy pass phrase:
A credential has been received for user yoichi in /tmp/x509up_u500.
[EMAIL PROTECTED] ~]$ globus-gass-server -r -w -p 40001
Error: Failed to initialize gass server library
(my-proxy credential does not seem to work.)
Wait, what? What's the output of grid-cert-diagnostics if you have a
myproxy cred instead of a g-p-i cred?
(I have set up the local certificate files in ~yoichi/.globus when I
tried the grid-proxy before)
Umm ... are there still certificates in there? Are there also
certificates in /etc/grid-security/certificates? It's cleaner if you
can do things entirely at the systems level and not in your ~/.globus
directory. Confusing security mixups can happen, especially if
they're not all sharing home directories.
(succeeded)
Well, so much for that theory.
(from the previous actions, both servers have valid grid-proxy
credentials)
I'm not sure what you mean from previous actions and proxy creds;
aren't the gatekeepers running on /etc/grid-security/hostcert/key.pem?
Anyway, let's see grid-cert-diagnostics from both grid1 and grid2 and
see if there's anything funny going on. I'd also like to see the
results of /usr/bin/env from your submission to jobmanager-fork.
Because you can't get the output files back, just submit a shell
script or something that runs /usr/bin/env > env.out, then send that.
Charles
