Please use the new documentation url https://docs.rc.uab.edu/ for all Research Computing documentation needs.
As a result of this move, we have deprecated use of this wiki for documentation. We are providing read-only access to the content to facilitate migration of bookmarks and to serve as an historical record. All content updates should be made at the new documentation site. The original wiki will not receive further updates.
The Research Computing Team
FAQ for 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. In Unix/Linux systems, normal users can open ports starting from 1025 to 65535. However, some Unix/Linux systems have Ephemeral port range from 1025-5000. So, its safer to use a port number above 5000.