You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Debugging GCS can be a challenge, specifically when trying to understand, if a transfer is failing because of a Globus configuration error, a POSIX filesystem error, or a firewall or network error. This issue is meant consolidate a bunch of the errors seen in Globus transfers with explanations of the potential problem. Globus's official troubleshooting guide provides some contexts. https://docs.globus.org/globus-connect-server/v5/troubleshooting-guide/
Globus Error Msg
Possible Problem
Details: 500-Command failed. : globus_xio: The GSI XIO driver failed to establish a secure connection. The failure occurred during a handshake read.\r\n500-globus_xio: System error in recv: Connection reset by peer\r\n500-globus_xio: A system call failed: Connection reset by peer\r\n500 End.\r\n
Firewall rule or policy (ssl and tcp traffic distinction)
Details: 500-Command failed. : globus_xio: The GSI XIO driver failed to establish a secure connection. The failure occurred during a handshake read.\r\n500-globus_xio: System error in recv: Unknown error\r\n500-globus_xio: A system call failed: An existing connection was forcibly closed by the remote host. \r\r\n500-\r\n500 End.\r\n
Firewall rule or policy (ssl and tcp traffic distinction)
Details: 500-Command failed. : globus_gridftp_server_file.c:globus_l_gfs_file_server_write_cb:3163: \r\n500-callback failed.\r\n500-globus_xio_tcp_driver.c:globus_l_xio_tcp_system_connect_cb:2022: \r\n500-Unable to connect to 198.51.100.10:50672\r\n500-globus_xio_system_select.c: globus_l_xio_system_handle_write:1108:\r\n500-System error in connect: Connection timed out \r\n500-globus_xio: A system call failed: Connection timed out\r\n500 End.\r\n
Firewall rule or policty (around data port range)
Details: 500-Command failed. : globus_xio: The GSI XIO driver failed to establish a connection via the underlying protocol.\r\n500-globus_xio: Unable to connect to 198.51.100.10:50778 \r\n500-globus_xio: System error in connect: Connection timed out\r\n500-globus_xio: A system call failed: Connection timed out\r\n500 End.\r\n
Firewall rule or policty (around data port range)
Details: 500-Command failed. : globus_xio: The GSI XIO driver failed to establish a connection via the underlying protocol.\r\n500-globus_xio: Unable to connect to 134.174.159.37:50004\r\n500-globus_xio: System error in connect: Unknown error\r\n500-globus_xio: A system call failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.\r\r\n500-\r\n500 End.\r\n
Firewall rule or policy - (blocking in this case connection on port 50004)
Details: globus_xio: The GSI XIO driver failed to establish a connection via the underlying protocol.\nglobus_xio: Unable to connect to 128.212.182.171:443\nglobus_xio: System error in connect: Connection refused\nglobus_xio: A system call failed: Connection refused\n
Firewall rule or policty (port 443)
Details: an end-of-file was reached\nglobus_xio: An end of file occurred\n
A busy endpoint
The text was updated successfully, but these errors were encountered:
Description
Debugging GCS can be a challenge, specifically when trying to understand, if a transfer is failing because of a Globus configuration error, a POSIX filesystem error, or a firewall or network error. This issue is meant consolidate a bunch of the errors seen in Globus transfers with explanations of the potential problem. Globus's official troubleshooting guide provides some contexts. https://docs.globus.org/globus-connect-server/v5/troubleshooting-guide/
The text was updated successfully, but these errors were encountered: