On Wed, Jul 23, 2008 at 11:51 AM, Charles Bacon <[EMAIL PROTECTED]> wrote: > On Jul 23, 2008, at 10:47 AM, I8abyte wrote: > >>>> I'm setting up 4.2.0 toolkit installation to use gridftp along with >>>> the myproxy service and I always get a "path length contraint >>>> execeeded" error when I try to use globus-url-copy. The myproxy >>>> issued proxy cert file is bigger in size and number of certificates it >>>> holds versus a grid-proxy-init issued one (which works fine, btw). >>>> Only the myproxy service gives me this trouble. >>> >>> How many more certificates? That is, how many "BEGIN CERTIFICATE" lines >>> are >>> there in the proxy? >> >> There are 4 total BEGIN CERTIFICATE lines in the myproxy proxy cert as >> opposed to only 2 in the grid-proxy-init issued cert. I have just a >> root- and second-level CAs if it makes any difference. This affects >> all systems. > > I don't see how that few would give you that problem. What does the myproxy > command output with -verbose? Can we see the exact text of the error you're > getting? Does it affect any of the other client tools?
I don't get any errors from myproxy, it works fine as far as I can tell. It appears to be something with the proxy certificate it generates, what's with the extra information in the certificate? And I do not know about any of the other client tools, right now I'm focusing on a standalone gridftp setup. When I try to use globus-url-copy after I get this: ... error: globus_ftp_client: the server responded with an error 530 530-globus_xio: Authentication Error 530-OpenSSL Error: s3_srvr.c:2004 in library: SSL routines, function SSL3_GET_CLIENT_CERTIFICATE: no certificate returned 530-globus_gsi_callback_module: Could not verify credential 530-globus_gsi_callback_module: Could not verify credential: path length constraint exceeded 530 End. > >> The install was/is originally built from source but I also tried >> suse-ia64 binary installer to no effect. These ia64 systems are >> running RHEL4 update 4. I noticed earlier that ia64-to-ia64 transfers >> commence but then quickly bog down and appear to hang (I can still >> Ctrl-C out of it). > > And what's running on the x86_64 side, in case it makes a difference? Sorry, same ... RHEL4 update 4. > > > Charles >
