Hmm... this is probably a script that works fine on your login node
but not on your worker nodes or vise versa? The fact that it is
writing to standard error and happens for each new shell is probably
what is causing Galaxy jobs to fail - Galaxy is thinking the
underlying applications are writing c
I simply removed the ulimit and the jobs complete successfully,
but I still wonder why it does not work and would like to put the ulimit again
in place.
It happens also with very simple jobs, like filter tool on a 7k region file for
“chr1”.
thank you very much,
ido
On 10 Nov 2014, at 11:34,
Hi,
I updated to the latest galaxy distribution (after one year). And now
every job fails with:
/home/imba/solexa/.profile.sh: line 118: ulimit: virtual memory: cannot modify
limit: Operation not permitted
The limit is ridiculously high:
ulimit -v 6000
Its just to prevent some badly program
