GalaxyFAQ: Difference between revisions
Jump to navigation
Jump to search
(add 3 more questions) |
Jpr@uab.edu (talk | contribs) (→Error: channel 3: open failed: connect failed: Connection refused: Removed the emphemeral port comment. These ports are dynamically selected so shouldn't interfere.) |
||
| Line 6: | Line 6: | ||
=== Error: channel 3: open failed: connect failed: Connection refused === | === Error: channel 3: open failed: connect failed: Connection refused === | ||
This error shows up when attempting an ssh port forwarding from the galaxy server to the localhost. This error occurs due to port conflict on the server side. The port number mentioned during the execution of ''personalize.sh'' might already be taken up ie., a service might already be running at this port. Check the list of ports opened by doing a ''netstat -lpn |grep <port-number>''. If the result is not empty, run the ''personalize.sh'' script again with a higher port number and then ssh port forward with this new port number. | This error shows up when attempting an ssh port forwarding from the galaxy server to the localhost. This error occurs due to port conflict on the server side. The port number mentioned during the execution of ''personalize.sh'' might already be taken up ie., a service might already be running at this port. Check the list of ports opened by doing a ''netstat -lpn |grep <port-number>''. If the result is not empty, run the ''personalize.sh'' script again with a higher port number and then ssh port forward with this new port number. On Unix/Linux systems, normal users can open ports starting from 1025 to 65535. | ||
=== I've set up a Personal Galaxy, now what? === | === I've set up a Personal Galaxy, now what? === | ||
Revision as of 13:50, 8 June 2012
FAQ for Galaxy
Personal Galaxy
Error: channel 3: open failed: connect failed: Connection refused
This error shows up when attempting an ssh port forwarding from the galaxy server to the localhost. This error occurs due to port conflict on the server side. The port number mentioned during the execution of personalize.sh might already be taken up ie., a service might already be running at this port. Check the list of ports opened by doing a netstat -lpn |grep <port-number>. If the result is not empty, run the personalize.sh script again with a higher port number and then ssh port forward with this new port number. On Unix/Linux systems, normal users can open ports starting from 1025 to 65535.