Dear Galaxy Dev List,
we currently facing a problem with integrating new Blast Databases in our Galaxy instance.
We added a the new DB to the file:
/galaxy-central/tool-data/blastdb.loc
But the new Database didn’t show up in the respective tools, this situation remains also after restarting the galaxy instance and reloading the tool config (blasn for example).
As we included several databases before (which worked fine) we tried to find the error an excluded (out-commented) an existing Db, but this database stayed in the tools. So the blastdb.loc file seems to be ignored by
galaxy.
(This is consistent for multiple users and browser, so we are sure this is not a client-sided Browser-Cache issue)
So my questions are: Is there any kind of internal Cache in Galaxy which could explain this behavior? How can we track down / solve the issue?
Our Galaxy Version is 17.05
Thanks a lot in advance!
Mit freundlichen Grüßen
i.A. Matthias Enders
**********************************
NPZ Innovation GmbH
Hohenlieth-Hof, D-24363 Holtsee
Tel.
+49-4351-736 189
Fax
+49-4351-736 271
Mobil:
+49-151-14247360
Mail:
m.enders@npz-innovation.de
Firmensitz Hohenlieth, Holtsee
Amtsgericht Kiel, HRB 15342 Kl
Geschäftsführer: Dr. Gunhild Leckband, Thorsten Pommer