Hi, Can you check the commit of galaxy that you are using and post the logs that you see when you install a tool that doesn't work ? Does this happen for all tools that you install ? Best, Marius On 19 September 2017 at 15:40, RMSe17 <rmse17@gmail.com> wrote:
Hi Bjoern,
I upgraded to 17.05, but am still getting the same error when trying to run an installed tool without Galaxy restart.
Any idea on where the issue could be?
Thanks!
On 9/13/17, Björn Grüning <bjoern.gruening@gmail.com> wrote:
Hi,
afaik Marius fixed a few bugs in 17.05 and I know that 17.05 should work as described not sure 17.01 can be exprected to work this way.
Can you try 17.05? Thanks, Bjoern
On 14.09.2017 03:51, RMSe17 wrote:
Hello, I have a fresh 17.01 Galaxy installed and set up with uWSGI. After installing a new tool, I can't run it without first restarting Galaxy. This is odd, because I know in 17.01 that should no longer be happening.
The error I get is "This tool was disabled before job completed. Please contact your Galaxy administrator.
In the logs I see "Tool (... tool name) removed from tool config, unable to run job Cleaning up external metadata files Error checking job readiness"
After Galaxy restarts, the tool runs fine.
Is there anything typical that could cause this? Any place I should start looking?
Thanks! ___________________________________________________________ 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/
___________________________________________________________ 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/