I am having a problem with the installation a local instance of Galaxy using htseq-count. The cloning took a long time to set up, more than with other things I have installed. With a hisat2 derived BAM file generated from primary sequencing data, genomes, and gff files that ran fine on the public Galaxy server I get the following message:
An error occured while running the tool toolshed.g2.bx.psu.edu/repos/lparsons/htseq_count/htseq_count/0.9.1.
Tool execution generated the following messages:
Fatal error: Exit code 127 (Unknown error occurred)
samtools: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
It seems that samtools is not configured to do something correctly. Not finding a genome index? The public Galaxy doesn’t require this be done manually. How is this different in the local instance?
I checked the dependency tool manager. Htseq-count dependencies htseq 0.9.1 and samtools 1.7 had green checks next to them. The previous step in the analysis, hisat2, had dependencies samtools 1.9 and seqtk 1.3 green checked and it worked fine on both the public Galaxy and my local instance.
This is a critical tool. Any help in getting this set up properly would be appreciated.