Paszkiewicz, Konrad wrote:
Dear all,
I have worked out what caused this. Its down to the configuration of my cluster which has both an internal IP address and external IP address. Both of these resolve to the same hostname.
Using the external IP address with the API worked, whereas the hostname did not. If any other user has this program, you need to modify line 58 of scripts/galaxy_messaging/server/data_transfer.py to point to your external IP address rather than the host name.
Hi Konrad, There are a couple solutions which would also solve this without modifying source: 1. Use the IP address on which Galaxy is bound in the URL argument of display.py, instead of the hostname: ./display.py c43c7605ba60633a2ed60f46c12f354e http://144.173.143.28:4000/api/libraries 2. Instruct Galaxy to bind to all available IP addresses. In the [server:main] section of universe_wsgi.ini: host = 0.0.0.0 I hope this helps. --nate
All the best!
Konrad.
-----Original Message----- From: Nate Coraor [mailto:nate@bx.psu.edu] Sent: 19 January 2011 16:43 To: Paszkiewicz, Konrad Cc: galaxy-dev@lists.bx.psu.edu Subject: Re: [galaxy-dev] API connection error
Paszkiewicz, Konrad wrote:
Dear all,
I'm getting the following error when trying to follow the instructions in the API README file. Universe_wsgi.ini is pasted below.
[galaxy@zeus api]$ ./display.py c43c7605ba60633a2ed60f46c12f354e http://zeus.ex.ac.uk:4000/api/libraries <urlopen error (111, 'Connection refused')>
Hi Konrad,
This should only occur if the Galaxy server itself is down. Are you able to access it via a web browser?
--nate
Any suggestions would be very welcome.
All the very best,
Konrad.
Dr Konrad Paszkiewicz Exeter Sequencing Service & Exeter Bioinformatics Service Biosciences, College of Life and Environmental Sciences University of Exeter Exeter EX4 4QD.
http://biosciences.exeter.ac.uk/facilities/sequencing/illumina/ http://biosciences.exeter.ac.uk/facilities/exbiss/