Hello all Galaxy devs,

I’ve come across (what seems to be) a Galaxy bug (or rather, tool-shed bug) 
when I run the data manager data_manager_gatk_picard_index_builder (rev. 
a15709ad26ea) from the Galaxy main tool shed repo on a clean Galaxy install.

Installation goes fine - when I install this data manager, all dependencies are 
correctly installed: package_picard_1_56_0 (rev. 99a28567c3a3) and 
package_samtools_0_1_18 (rev. 171cd8bc208d).

After installation, I go to Admin -> Manage local data (beta) -> Run Data 
Manager Tools, click “Generate GATK-sorted Picard indexes” and the data manager 
form is displayed. I select the reference genome (either hg19 or hg38 - 
installed with data_manager_fetch_genome_dbkeys_all_fasta from the main tool 
shed, rev. bca4c608408c - working fine with other tools including bowtie2 and 
trackster), enter “hg19” both “Name of sequence” and “ID for sequence” fields, 
and click “Execute”.

The indexing job is added to the queue, but when I go to view data manager jobs 
for this data manager, I see it stopped with the following error:

Traceback (most recent call last):
 line 179, in <module>
    if __name__ == "__main__": main()
 line 162, in main
    raise Exception( '"%s" is not a valid dbkey. You must specify a valid 
dbkey.' % ( options.fasta_dbkey ) )
Exception: "None" is not a valid dbkey. You must specify a valid dbkey.

Inspecting galaxy.log doesn’t reveal anything relevant (at least for me - which 
is why I need your help!):

galaxy.jobs DEBUG 2015-04-17 11:13:23,031 (63) Working directory for job is: 
galaxy.jobs.handler DEBUG 2015-04-17 11:13:23,044 (63) Dispatching to local 
runner - - [17/Apr/2015:11:13:22 +0100] "POST /api/tools HTTP/1.1" 200 - 
 "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/600.4.10 (KHTML, 
like Gecko) Version/8.0.4 Safari/600.4.10"
galaxy.jobs DEBUG 2015-04-17 11:13:23,168 (63) Persisting job destination 
(destination id: local)
galaxy.jobs.handler INFO 2015-04-17 11:13:23,212 (63) Job dispatched
galaxy.tools.deps DEBUG 2015-04-17 11:13:23,393 Building dependency shell 
command for dependency 'samtools'
galaxy.tools.deps DEBUG 2015-04-17 11:13:23,395 Building dependency shell 
command for dependency 'picard'
galaxy.jobs.runners DEBUG 2015-04-17 11:13:23,475 (63) command is: 
 export PACKAGE_BASE; . 
 export PACKAGE_BASE; . 
 "/home/galaxy/galaxy-dist/database/files/000/dataset_70.dat" \ --jar 
"$JAVA_JAR_PATH/CreateSequenceDictionary.jar" \ --fasta_filename 
"/home/galaxy/galaxy-dist/tool-data/hg19/seq/hg19.fa" \ --fasta_dbkey "hg19" \ 
--fasta_description "Human, Feb. 2009, GRCh37/hg19" \ --data_table_name 
"gatk_picard_indexes"; return_code=$?; python 
 sh -c "exit $return_code"
galaxy.jobs.runners.local DEBUG 2015-04-17 11:13:23,476 (63) executing job 
galaxy.jobs DEBUG 2015-04-17 11:13:23,526 (63) Persisting job destination 
(destination id: local)
galaxy.jobs.runners.local DEBUG 2015-04-17 11:13:24,976 execution finished: 
galaxy.jobs DEBUG 2015-04-17 11:13:25,054 setting dataset state to ERROR
galaxy.jobs DEBUG 2015-04-17 11:13:25,122 job 63 ended
galaxy.datatypes.metadata DEBUG 2015-04-17 11:13:25,123 Cleaning up external 
metadata files

Some more system details:

Galaxy version: latest_15.03, running on Ubuntu 14.04.2 LTS
Java: 1.8.0_45-b14 from the webupd8 Ubuntu repo.
Using Postresql locally, everything else local too. Cloned from the Bitbucket 
repo (in case this matters).

Can anyone shed some light on this? In the traceback log above it seems 
options.fasta_dbkey is being set to “None” rather than “hg19” but I am not sure 
how to solve this, or if this is indeed the problem.

Thank you in advance!

All the best,
-- Paulo


Paulo Filipe Silva | PhD, Biology | MSc, Bioinformatics
Bioinformatician @ CGPP - Centre for Predictive and Preventive Genetics
http://www.cgpp.eu <http://www.cgpp.eu/>

IBMC - Institute for Molecular and Cell Biology
Rua do Campo Alegre, 823
4150-180 Porto, Portugal
E-mail: paulo.si...@ibmc.up.pt <mailto:paulo.si...@ibmc.up.pt>
Telephone: +351 22 607 49 42 ext 2811
Fax: +351 22 600 29 23

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:

Reply via email to