I can confirm that the proxy settings are the reason for the failing
export. When I go to localhost:8080 directly, I can export large files
from the Data Library.
When going via the proxy using the URL, download of large files does not
work. Here is a hint on what the solution might be
Hi Assaf,
After all, the problem appears not to be total size of the history, but
the size of the individual datasets.
Now, histories which contain big datasets (1GB) imported from Data
Libraries causes the exporting process to crash. Can somebody confirm
if this is a bug? I uploaded the
OK, it seems to be a proxy error.
When the proxy does not receive data from the server, it times out, and
closes the connection.
I think the process that packs the datasets takes too long, so the
connection is closed before the packaging is finished? Just a gues...
From the httpd logs:
=
Hi Gordon,
Thanks for your assistance and the recommendations. Freezing postgres
sounds like hell to me :-)
abrt was filling the root directory indeed. So disabled it.
I have done some exporting tests, and the behaviour is not consistent.
1. *size*: in general, it worked out for smaller
Hello Joachim,
Joachim Jacob | VIB | wrote, On 03/26/2013 10:01 AM:
abrt was filling the root directory indeed. So disabled it.
I have done some exporting tests, and the behaviour is not consistent.
1. *size*: in general, it worked out for smaller datasets, and usually
crashed on
Please keep all replies on-list so that everyone can contribute.
Someone more knowledgeable about systems than me suggests that lsof(8) and/or
/proc/galaxy server pid/fd should yield some clues as to what file is being
written to.
Good luck,
J.
On Mar 25, 2013, at 10:01 AM, Joachim Jacob |
Hello Joachim,
Couple of things to check:
On Mar 25, 2013, at 10:01 AM, Joachim Jacob | VIB | wrote:
Hi,
About the exporting of history, which fails:
1. the preparation seems to work fine: meaning: choosing 'Export this
history' in the History menu leads to a URL that reports initially
Hi all,
Exporting histories fails on our server: Reason: *Error reading from
remote server.
*When looking at the logs and the system:
tail /var/log/messages
Mar 19 15:52:47 galaxy abrt[25605]: Write error: No space left on device
Mar 19 15:52:49 galaxy abrt[25605]: Error writing
I'm unable to reproduce this behavior using a clean version of galaxy-dist. The
code (export_history.py) doesn't create any temporary files and appears to
write directly to the output file, so it seems unlikely that Galaxy is writing
anything to the root directory.
Can you provide the name of
