I'm not sure what's causing the error, but one thing I notice: > [EMAIL PROTECTED]:/home/pcd/10238> myproxy-logon -v -s pc222771 > MyProxy v4.2 10 Jan 2008 > Attempting to connect to 10.6.3.209:7512 > using trusted certificates directory > /sandbox/globus/globus-4.2.0/share/certificates > Failed reading length 0 > Error authenticating: Connection closed.
I'd expect to see the following in the output above: "no valid credentials found -- performing anonymous authentication" It makes me think that perhaps pcd10238 already has a credential (from a previous GT installation?) and that credential isn't accepted by the myproxy-server for some reason. Unfortunately, the myproxy-server's error message isn't very helpful (at least to me). If pcd10238 does have an existing proxy credential, does it help to run grid-proxy-destroy before myproxy-logon? For example, here's the output I get: $ myproxy-logon -v MyProxy v4.2 10 Jan 2008 PAM Attempting to connect to 141.142.15.40:7512 using trusted certificates directory /etc/grid-security/certificates no valid credentials found -- performing anonymous authentication server name: /C=US/O=National Center for Supercomputing Applications/CN=myproxy.ncsa.uiuc.edu checking that server name is acceptable... server name does not match "[EMAIL PROTECTED]" server name matches "[EMAIL PROTECTED]" authenticated server name is acceptable Enter MyProxy pass phrase: A credential has been received for user jbasney in /tmp/x509up_u25555. The "no valid credentials found" message should appear before the start of the SSL handshake if there are no credentials available to the client, and the error seems to be happening during the SSL handshake, so I'd expect to see that message before the error. It's also odd that you get different output from myproxy-logon depending on whether you run the myproxy-server via xinetd or from the command-line. In the former case, it seems that xinetd is failing to start the myproxy-server, perhaps because LD_LIBRARY_PATH isn't set or some other problem with /etc/xinetd.d/myproxy, so the network connection is closed before the client can ready any bytes. Is there any useful syslog output for this case? Sorry all I can offer is guesses... -Jim
smime.p7s
Description: S/MIME Cryptographic Signature
