Sorry for double posting. I've did'nt noticed your link to my
old email. :-(
Sorry for overlooking your earlier post. The solution is to disable
'filter-with = gzip' in the config, as it turns out it's incompatible
with the way we stream templates like the history (streaming is enabled
when debug is disabled). I have updated this information on the
ProductionServer wiki page.
Note this does not mean you can't use on-the-fly compression - but it
should be done in the proxy server instead (where it would probably be
more efficient anyway).
Am 10/21/2010 03:34 AM, schrieb Nate Coraor:
>Could you send your config file off-list (directly to me at
>nate(a)bx.psu.edu) with any identifying or secure information removed
>(like the database user and password, the id_secret, and your
>Also, are you able to load the same history with debug = True?
>Isabelle Phan wrote:
>>are there plans to address this issue or is this not affecting others besides
Michael and myself?
>>This is currently a complete blocker for me:
>>- downloading large files from Galaxy fails with an out of memory error
>>- trying to fix that by setting
>>debug = False
>>causes galaxy to be unusable. The application starts up, but the History panel
shows 'internal server error' and the app throws a RuntimeError:
>>Traceback (most recent call last):
1053, in process_request_in_thread
>> self.finish_request(request, client_address)
>> File "/usr/lib/python2.6/SocketServer.py", line 320, in
>> self.RequestHandlerClass(request, client_address, self)
>> File "/usr/lib/python2.6/SocketServer.py", line 615, in __init__
432, in handle
>> File "/usr/lib/python2.6/BaseHTTPServer.py", line 329, in handle
427, in handle_one_request
290, in wsgi_execute
125, in wsgi_write_chunk
>> "Content returned before start_response called")
>>RuntimeError: Content returned before start_response called
>>I did an update of galaxy, migrated the database to version 58, and am still
unable to switch off debugging. Galaxy is not running behind apache at present.
>>Without the ability to download large-ish files, I am losing support to have
Galaxy in production *sob*.
>>Any help greatly appreciated.
>galaxy-dev mailing list
galaxy-dev mailing list