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 any file that Galaxy appears to be writing to
outside of <galaxy-home>? What about watching the job output file/export file
to see if that's increasingly in size and causing the out-of-space error?
On Mar 19, 2013, at 10:56 AM, Joachim Jacob | VIB | wrote:
> Hi all,
> Exporting histories fails on our server: " Reason: *Error reading from remote
> *When looking at the logs and the system:
> tail /var/log/messages
> Mar 19 15:52:47 galaxy abrt: Write error: No space left on device
> Mar 19 15:52:49 galaxy abrt: Error writing
> So I watched my system when I repeated the export, and saw that Galaxy fills
> up the root directory (/), instead of any temporary directory.
> Somebody has an idea where to adjust this setting, so the export function
> uses any temporary directory?
> Joachim Jacob
> Rijvisschestraat 120, 9052 Zwijnaarde
> Tel: +32 9 244.66.34
> Bioinformatics Training and Services (BITS)
> 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:
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: