Question: HISAT Errors on Local Galaxy due to dependency issues
0
gravatar for jasonschultz
2.2 years ago by
jasonschultz10
jasonschultz10 wrote:

Hi,

I am getting the following message when running HISAT2. Do you know what the problem might be?

Fatal error: Exit code 1 () Usage: samtools sort [options...] [in.bam] Options: -l INT Set compression level, from 0 (uncompressed) to 9 (best) -m INT Set maximum memory per thread; suffix K/M/G recognized [768M] -n Sort by read name -o FILE Write final output to FILE rather than standard output -O FORMAT Write output as FORMAT ('sam'/'bam'/'cram') (either -O or -T PREFIX Write temporary files to PREFIX.nnnn.bam -T is required) -@ INT Set number of sorting and compression threads [1]

Legacy usage: samtools sort [options...] <in.bam> <out.prefix> Options: -f Use <out.prefix> as full final filename rather than prefix -o Write final output to stdout rather than <out.prefix>.bam -l,m,n,@ Similar to corresponding options above Error while flushing and closing output libc++abi.dylib: terminating with uncaught exception of type int (ERR): hisat2-align died with signal 6 (ABRT)

admin tool hisat local tool-shed • 804 views
ADD COMMENTlink modified 2.2 years ago by Jennifer Hillman Jackson25k • written 2.2 years ago by jasonschultz10

Are you getting this on Galaxy? This makes sense as an error on the command line, but less so on Galaxy where the version of samtools should be < 1.3.

ADD REPLYlink written 2.2 years ago by Devon Ryan1.9k
0
gravatar for jasonschultz
2.2 years ago by
jasonschultz10
jasonschultz10 wrote:

It is in Galaxy, yes. It a local instance where I have been struggling to do an alignment. In my local instance, I do have several versions of samtools, because each tool requires a slightly different version. But they are all < 1.3: 1.2, 0.18, 0.19.

I am missing something basic - the installed tools are not finding other installed tools. Do you know why that might be? I am getting a similar error for tophat2. It is saying bowtie2 is not installed, but I installed that through the toolshed in Galaxy also.

ADD COMMENTlink written 2.2 years ago by jasonschultz10
1

You might just try to "repair" the various broken tools in the admin section under "manage installed tools" (or whatever that's called). Somehow you have a bunch of incorrectly installed packages. If push comes to shove you can directly edit the env.sh files for each tool to fix things, but that's kind of a hassle.

ADD REPLYlink written 2.2 years ago by Devon Ryan1.9k

Did you ever figure out what was going wrong? I am having the exact same issues as you with both TopHat and HISAT2. Same error messages and I am also running a local instance of Galaxy.

ADD REPLYlink written 23 months ago by fkorkmaz0
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 171 users visited in the last hour