Just to clarify, for us it wasn't dependent on the tool - it was
actually the version of samtools installed in the 'galaxy' user's
environment i.e. on the 'galaxy' user's PATH.
I set it explicitly by creating a file called "local_env.sh" in the
'config' directory of the Galaxy installation with the following content:
$ cat local_env.sh
# Prepend samtools 1.2
which is automatically picked up by 'run.sh' when Galaxy is started (I
don't know how that plays if you're using a uwsgi/supervisor setup).
On 24/05/16 11:46, Raymond Wan wrote:
On Tue, May 24, 2016 at 6:29 PM, Peter Briggs
One of my colleagues encountered a similar-sounding error on our local test
instance, where an unsorted BAM file seemed to crash the Galaxy handler
processes and prevented them from restarting.
In our case the default samtools version in the Galaxy environment was
0.1.18; we found that updating this to samtools 1.2 fixed the crash problem.
Ah! That does sound familiar. As I just replied in another message,
we seem to have at least 5 versions of samtools in the system. I'm
not sure if that is normal or not for a Galaxy instance...
Let me see if I can figure out (through logs, but most likely by
asking the user) what tool he was using and figure out which samtools
executable was being run. If it is 0.1.18, I'll look into update
it...thank you for sharing your colleague's experience!
Peter Briggs peter.bri...@manchester.ac.uk
Bioinformatics Core Facility University of Manchester
B.1083 Michael Smith Bldg Tel: (0161) 2751482
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:
To search Galaxy mailing lists use the unified search at: