gt-user list, I'm using globus-url-copy 4.14 (gt4.2.1, RHEL 5.3 x86_64) and am running into two issues with third-party transfers. There are no firewalls present on my end and as far as I know no firewalls present on the remote end. I'm not certain what version the remote end is using or if they have some custom configuration settings. Please let me know if you need more information about the remote end -- I'm happy to ask them if necessary.
First, my invocation: globus-url-copy -dbg -bs 4M -p 4 -nodcau gsiftp://site1/path/file gsiftp://site2/path/file I've also found that this invocation also works: globus-url-copy -dbg -bs 4M -p 4 -no-third-party-transfers gsiftp://site1/path/file gsiftp://site2/path/file ** Question 1 - Is either of these methods more/less secure/better-performing than the other? The second issue I'm seeing is that the '-block-size' argument appears to be a "maximum" block size argument rather than a fixed one. During transfers where parellelism is greater than zero ("-p 1") the block size appears to drop to as low as 131072, which is not what we want. For example: Example A: globus-url-copy -dbg -bs 4M -p 0 -no-third-party-transfers gsiftp://site1/path/file gsiftp://site2/path/file In example A, the transmit block size is fixed at 4M. This is the preferred behavior for our site. Example B: globus-url-copy -dbg -bs 4M -p 1 -no-third-party-transfers gsiftp://site1/path/file gsiftp://site2/path/file In example B, the transmit block size is fixed at 131072 (bytes). This size will not work for our site (for reasons that I won't go into here). Example C: globus-url-copy -dbg -bs 4M -p 4 -nodcau gsiftp://site1/path/file gsiftp://site2/path/file In example C, the transmit block size varies between 131072 bytes and some upper limit (though I've not determined what this upper limit is). ** Question 2: My preferred behavior would be a fixed block size of 4M or at the very least a minimum block size of 4M. Is this possible and how? Finally, I've noticed that in my invocation either -nodcau or -no-third-party-transfers is required for the transfer to complete. If I don't include either of these arguments, the transfer will fail before starting with the following error: error: globus_ftp_client_state.c:globus_i_ftp_client_response_callback:4339: the server responded with an error 500 500-Command failed. : globus_xio_gsi: gss_accept_sec_context failed. 500-GSS Major Status: Communications Error 500-globus_gsi_gssapi: Error with GSS token 500-globus_gsi_gssapi: Error with GSS token: The input token has an invalid length of: 0 ** Question 3: Why are either of these two arguments required? Any assistance you can provide on the above is appreciated. I'm new to working with the Globus Toolkit, so let me know if there's something I'm missing. Thank you.
