Dear Peter,

up to our galaxy admin, we make use of the  Data Manager, so this seems not to be the issue here?:

Mit freundlichen Grüßen

Matthias Enders

-----------------------------------------------------------------------

GERMAN SEED ALLIANCE GmbH

c/o Norddeutsche Pflanzenzucht

Hans-Georg Lembke KG

Hohenlieth, 24363 Holtsee

Tel.: +49 (0)4351/ 736-189

Fax: + 49 (0)4351/ 736-271

Mobil: +49 (0)151/ 14247360

Email: m.enders@german-seed-alliance.de

Firmensitz Köln

Amtsgericht Köln, HRB 73844

-----Ursprüngliche Nachricht-----
Von: Peter Cock <p.j.a.cock@googlemail.com>
Gesendet: Dienstag, 10. Juli 2018 13:27
An: Matthias Enders <m.enders@german-seed-alliance.de>
Cc: Björn Grüning <bjoern.gruening@gmail.com>; galaxy-dev@lists.galaxyproject.org
Betreff: Re: [galaxy-dev] Expose Command Line in Galaxy
Priorität: Hoch

Thanks for getting back to us - this was actually my guess from the original email - that it was not a blastn error message, but a Galaxy message before ever calling BLAST.

My guess is you are seeing this issue, or something like it, with having to restart Galaxy to reload the *.loc files?

https://github.com/galaxyproject/galaxy/issues/3171

Peter

On Tue, Jul 10, 2018 at 12:22 PM, Matthias Enders <m.enders@german-seed-alliance.de> wrote:

> Dear all,

>

> finally a restart of the container solved the issue with the database/blast.

>

> Regarding the problem with the command line:

> For other tools, the command line showed up, but not for blastn, as the wrapper encountered the error before creating the command line (this is my interpretation).

>

> So the error: "An invalid option was selected for database, 'myCoolDatabaseName', please verify." Was produced by the wrapper, which did not find the new database before restarting the galaxy container.

>

> So the real issue here is perhaps more on "How could blast+ be made aware of new integrated databases, without restarting"?

>

> Mit freundlichen Grüßen

>

> Matthias Enders