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 ********************************** [cid:image002.png@01CF9B54.EBA59810]
NPZ Innovation GmbH Hohenlieth-Hof, D-24363 Holtsee Tel. +49-4351-736 189tel:%2B49-4351-736%20189 Fax +49-4351-736 271tel:%2B49-4351-736%20271 Mobil: +49-151-14247360tel:%2B49-0151-14247360 Mail: m.enders@npz-innovation.demailto:m.enders@npz-innovation.de Web: www.npz-innovation.dehttp://www.npz-innovation.de/
Firmensitz Hohenlieth, Holtsee Amtsgericht Kiel, HRB 15342 Kl Geschäftsführer: Dr. Gunhild Leckband, Thorsten Pommer
