I usually see that when I've generated multiple host certificates on a
machine. I think myproxy is probably running with an older pair than
are currently on the filesystem. The two things I would try are:
1) stopping and restarting myproxy on grid6
and
2) regenerating the host credentials (container/host) for grid6.
Unfortunately, gt-server-ca.pl isn't very good at running a second
time. If you have to do that, you'll want to delete more things; all
of /etc/grid-security, everybody's ~/.globus directory (including
root), and $GLOBUS_LOCATION/share/certificates. That's the last
resort, though.
Charles
On Nov 18, 2008, at 10:23 PM, Alpesh Virani wrote:
Hi All,
First of all I wish to thank for a very good quick start guide. I
could install and submit job on my server from the server machine
itself, which is named as "grid6". I have also finished the
installation on the second machine, grid7. When I use myproxy-retrieve
on the second machine I get the following error. I have tried many
things for the last week but couldn't solve the problem. I would be
grateful if somebody could help me. Thank you in advance.
myproxy-retrieve -v -s grid6 -k grid7.i2it.ac.in -l grid7
MyProxy v4.2 10 Jan 2008 PAM
Attempting to connect to 10.1.9.7: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: a_verify.c:168: in library: asn1 encoding routines,
function ASN1_item_verify: EVP lib
OpenSSL Error: rsa_eay.c:708: in library: rsa routines, function
RSA_EAY_PUBLIC_DECRYPT: padding check failed
OpenSSL Error: rsa_pk1.c:100: in library: rsa routines, function
RSA_padding_check_PKCS1_type_1: block type is not 01
--
thanks & regards
Alpesh Virani
