It looks like port range is not configured correctly on go.hpcs.lbl.gov. This simply means that go.hpcs.lbl.gov is listening on these ports for data channel connections and providing these port values to GO and thus to the Globus Connect. Thats why Globus Connect is attempting to connect to these ports.
Raj On Jul 25, 2013, at 12:16 PM, Karen M. Fernsler wrote: > Hi, > > Thanks for your response. > > We're seeing things like this pushing to our endpoint. Originally, I > took this to be a pointer to a port. What does this indicate? : > > 07/25/2013 10:13:15 AM CONNECT_FAILED Could not connect > Error (transfer) Server: fernsler#lurch (Globus Connect) File: /~/test.html > Command: RETR ~/test.html Message: Fatal FTP response --- 500-Command failed. > : callback failed. 500-globus_xio: Unable to connect to 131.243.60.14:56987 > 500-globus_xio: System error in connect: Operation timed out 500-globus_xio: > A system call failed: Operation timed out 500 End. > > 07/25/2013 10:11:23 AM CONNECT_FAILED Could not connect > Error (transfer) Server: me#host (Globus Connect) File: /~/test.html Command: > RETR ~/test.html Message: Fatal FTP response --- 500-Command failed. : > callback failed. 500-globus_xio: Unable to connect to 131.243.60.14:49058 > 500-globus_xio: System error in connect: Operation timed out 500-globus_xio: > A system call failed: Operation timed out 500 End. > > 07/25/2013 10:09:32 AM CONNECT_FAILED Could not connect > Error (transfer) Server: me#host (Globus Connect) File: /~/test.html Command: > RETR ~/test.html Message: Fatal FTP response --- 500-Command failed. : > callback failed. 500-globus_xio: Unable to connect to 131.243.60.14:36913 > 500-globus_xio: System error in connect: Operation timed out 500-globus_xio: > A system call failed: Operation timed out 500 End. > > (we also see this with globus-url-copy). > > -k > > > On Thu, Jul 25, 2013 at 12:00:31AM -0500, Raj Kettimuthu wrote: >> Karen, >> GridFTP server does not do any polling. Your server will listen on a port in >> the port range you have specified and tell the client the IP address and the >> exact port on which it is listening, the client in turn will pass that >> information to the server on the other end and that server will connect to >> this specific IP address and port. >> >> Raj >> >> On Jul 24, 2013, at 5:42 PM, Karen M. Fernsler wrote: >> >>> Hi, >>> >>> We have a gridftp server behind a firewall, but the default ports >>> are open (50000-51000), and this port range is specified in the >>> gridftp.conf file. >>> >>> When we try to do a transfer from it from another site, we find >>> the remote site appears to be polling port ranges from 30000-80000+. >>> Needless to say, it takes some time before the poll hits a port >>> that's actually open >>> >>> Is there something we can configure something on the local gridftp >>> server to tell the remote host to only poll in the default range? >>> >>> thanks, >>> -k >>
