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.end...@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 ___________________________________________________________ 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: https://lists.galaxyproject.org/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/
