Our local galaxy production server is facing issue of downloading file larger than 1 GB.
Galaxy version is 20.01
we have tried downloading through wget | curl options and tried to change nginx parameters.
Please assist.
gbbio
March 6, 2021, 1:37pm
2
Did you also used the try x-accel-redirect option?
Also take a look at a solution I have posted earlier:
If I download a file, fasta or zip of lets say 3GB the downloaded file is always max 1GB. Where do I need to look to solve this?
I tried to add proxy_max_temp_file_size 0; to my nginx.conf but that is not working.
In my galaxy.log I get the following error:
uwsgi_response_write_body_do() TIMEOUT !!!
IOError: write error
EDIT:
I am still searching for a solution (and a cause) so here an update. My problem is not solved yet.
At the moment I have two galaxy servers running, both a different s…
Thanks for the help.
Change in x-accel-redirect option is not enough.
proxy_max_temp_file_size is also playin a role as said by dannon.
https://stackoverflow.com/questions/12232078/how-to-configure-server-to-allow-large-file-downloads
2 Likes
jennaj
March 17, 2021, 3:16pm
4
Hi all – this Q&A has some alternatives:
@KEELE Yes, the data is large. The connection dropped for me too.
I remembered that this has come up before. See this prior Q&A on how to “resume” downloads with curl and wget and see if one of those works for you.
Your other option is to create a History archive and download that. Once uncompressed, you’ll find your data inside of it. Tip: Copy just the data you need into a new history to make it smaller/faster to process this way. Copies of dataset you already have in your account do not c…
Also please see:
If I download a file, fasta or zip of lets say 3GB the downloaded file is always max 1GB. Where do I need to look to solve this?
I tried to add proxy_max_temp_file_size 0; to my nginx.conf but that is not working.
In my galaxy.log I get the following error:
uwsgi_response_write_body_do() TIMEOUT !!!
IOError: write error
EDIT:
I am still searching for a solution (and a cause) so here an update. My problem is not solved yet.
At the moment I have two galaxy servers running, both a different s…
ping @nate @mvdbeek – can you help out? We made changes on usegalaxy.org but this person is using a local install.