Great, glad it worked for you!
And, once we release a new AMI, it'll be fixed retroactively. That is, you'll
be able to use your existing cloud setup with the new AMI and it should just
work.
-Dannon
On Jan 23, 2012, at 5:35 AM, Greg Edwards wrote:
> Dannon,
>
> Cool, that seems to have wo
Dannon,
Cool, that seems to have worked. I set
server {
listen 80;
client_max_body_size 500m;
in /opt/galaxy/pkg/nginx/conf/nginx.conf
and issued sudo kill -HUP `cat /opt/galaxy/pkg/nginx/logs/nginx.pid`
and it's uploading my test files of 2mb to 25mb ok.
I think
It's the other nginx.conf at /opt/galaxy/pkg/nginx/conf/nginx.conf, I don't
think that one you found is used. And it isn't explicitly set at all
currently, so the default 1m gets applied.
And, to reload with the modified config, I think this should do the trick (as
the ubuntu user)-
sudo kill
Hi Dannon,
I found nginx.conf at /opt/galaxy/pkg/nginx_upload_module-2.0.12/nginx.conf
It contains ..
client_max_body_size 100m;
That looks like 100 Megabyte ?? but seems to result in 1 Megabyte. Can I
set it to 1m, or 1g ?
Can't see how to restart nginx yet.
Thanks,
Greg E
Dannon,
Thanks. Glad it's not my error !
Could ypu let me know where nginx.conf is, and how to "restart the nginx
process" ? This is a prototype proof-of-concept implementation, and I think
a once-per-instance custom fix which preserves the simple ability to use
Get Data / Upload Files From Your
Hi Greg,
This is a problem with the default client_max_body_size option in nginx being
set far too small in the nginx.conf on the cloud AMI. It'll be fixed with our
next AMI update, but to fix it you have to edit the nginx.conf on your cloud
node to change the client_max_body_size to something
Hi,
I'm building a Galaxy Cloud implementation, and running into a problem
uploading data files > 1 Mbyte, or 1,048,576 bytes.
I've started Galaxy Cloudman and a single server, all according to to the
Wiki. I can upload fasta format files < 1048756 bytes, and general CSV
format peptide files, and
7 matches
Mail list logo
