> I edited /etc/hosts on both systems to make them aware of the other's > hostname and while retrieving I get new error messages as follows.
Yes, that is progress. > maverik titu # myproxy-retrieve -v -s fool.man.machine -k Maverick -l titu > MyProxy v5.4 22 Apr 2011 PAM OCSP > Attempting to connect to 192.168.1.2:7512 > Successfully connected to fool.man.machine:7512 > using trusted certificates directory /etc/grid-security/certificates > no valid credentials found -- performing anonymous authentication > Error authenticating: GSS Major Status: Authentication Failed > GSS Minor Status Error Chain: > globus_gss_assist: Error during context initialization > OpenSSL Error: s3_clnt.c:1059: in library: SSL routines, function > SSL3_GET_SERVER_CERTIFICATE: certificate verify failed > globus_gsi_callback_module: Could not verify credential > globus_gsi_callback_module: Can't get the local trusted CA certificate: > Untrusted self-signed certificate in chain with hash 93fd916c In the quickstart guide http://www.globus.org/toolkit/docs/latest-stable/admin/quickstart/#q-second there's a step to copy your $GLOBUS_LOCATION/share/certificates directory from the first machine to the second machine where the CA certificate with hash 93fd916c should be found. However, on maverik it appears you have an /etc/grid-security/certificates directory that is overriding your $GLOBUS_LOCATION/share/certificates directory, so you need to copy the 93fd916c.* files from fool to your /etc/grid-security/certificates directory on maverik for the CA certificate to be trusted. You can ignore the "WARNING: cert_dir not specified" and "Error initializing one or more Usage Stat target(s)" messages from the myproxy-server. I don't think they'll cause you any problems. -Jim
