Thon, 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 you could also SSH in to your instance, edit the nginx.conf to change the client_max_body_size to something more appropriate for your needs and restart the nginx process. If you'd rather not do that (you'd have to do it for every instance, unfortunately, since that volume is not persisted after shutdown), as a workaround the URL upload will work correctly with any size file if you're able to host the file you want to upload somewhere local. Thanks! Dannon On Dec 9, 2011, at 3:08 PM, Thon deBoer wrote:

I am trying to setup a instance of Galaxy on the EC2 cloud and everything seems to be going OK. Everything installs correctly and I can start Galaxy with no problems.

But when I try to upload a SMALL BAM file (~5 MB), it just hangs there and never completes...

When I look at the error.log I see the following error message:

2011/12/09 19:27:32 [error] 929#0: *1204 client intended to send too large body: 4719398 bytes, client: 173.195.189.92, server: localhost, request: "POST /tool_runner/index HTTP/1.1", host: "ec2-50-17-113-5.compute-1.amazonaws.com", referrer: "http://ec2-50-17-113-5.compute-1.amazonaws.com/tool_runner?tool_id=upload1"

It seems to have a problem with the size of the body...

Anyone have an idea how to fix this?

I am using ami-da58aab3

Regards,

Thon de Boer, Ph.D. Bioinformatics Guru +1-650-799-6839 thondeboer@me.com LinkedIn Profile

___________________________________________________________ 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:

http://lists.bx.psu.edu/