I doubt there is a config option somewhere that is going to fix this.
Can your compute nodes download external data outside of Galaxy? (One
could submit a test script to the cluster with a download and see if
it succeeds.) If you give me the URL and let me know what kind of
cluster you are running I could help you formulate that test.
If we can confirm that the cluster nodes cannot download external
files - it might be worth running `upload1` jobs with a local job
runner instead of on the cluster - frequently login servers and web
servers have more external access than compute nodes in cluster
environments. Let me know if you need help configuring that.
On Wed, Oct 1, 2014 at 3:41 AM, Elizabeth Chia <elc...@gmail.com> wrote:
> Dear *
> I have a local galaxy instance installed on a cluster.
> I've been trying to upload data by URL but kept getting this error: "unable
> to fetch <url of data> [Errno socket error] [Errno 110] connection timed
> out". I've tried with and without file compression format and still gives me
> that error.
> Am I suppose to modify/edit any particular config file?
> Can't seem to find a similar thread or answer to this but perhaps I may have
> missed. Apologies if I have missed. Would appreciate if anyone can please
> Best regards
> Please keep all replies on the list by using "reply all"
> in your mail client. To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
> To search Galaxy mailing lists use the unified search at:
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: