Re: [galaxy-dev] setting metadata externally failed for HistoryDatasetAssociation

Thanks Peter and John - this was exactly the issue- problem solved. Not very intuitive but an easy fix :) On 3 June 2016 at 23:13:34, Peter Cock (p.j.a.c...@googlemail.com) wrote: Hi Anthony, The line numbers for binary.py don't match the current latest sour

Re: [galaxy-dev] setting metadata externally failed for HistoryDatasetAssociation

Hi Anthony, The line numbers for binary.py don't match the current latest source, but I would bet this is due to the samtools binary not being on the path of the cluster nodes. Note Galaxy itself needs samtools for dealing with BAM files and this is expected to be on the $PATH (and it not currentl

Re: [galaxy-dev] setting metadata externally failed for HistoryDatasetAssociation

I think newer versions of Galaxy give a better error message - I am pretty sure the problem is you are missing samtools. It needs to be available on the PATH for Galaxy if you use bam data. -John On Fri, Jun 3, 2016 at 1:00 PM, Anthony Underwood wrote: > > > Jobs that I run on a local Galaxy ins

[galaxy-dev] setting metadata externally failed for HistoryDatasetAssociation

Jobs that I run on a local Galaxy install on a Fedora 23 machine are completing but are erroring with the message below. Any idea why the metadata can not be written? Thanks galaxy.jobs.runners.local DEBUG 2016-06-03 17:30:02,044 execution finished: /home/anthony.underwood/galaxy/database/jo