Hi John,
Thanks for the reply. I saw in the stack trace that there was a issue with
mercurial, which was recently installed in the system. After uninstalling it,
everything ran again. Not entirely sure what happened.
Thanks,
Miuki
On Mar 14, 2017, at 8:27 AM, John Chilton
Did you figure this out?
It looks like you jobs are not detecting Galaxy's virtualenv and so
they are getting a dependency (in this case mercurial) from Galaxy
root packages.
I'd review this document:
https://docs.galaxyproject.org/en/master/admin/framework_dependencies.html#galaxy-job-handlers
Hi all,
This afternoon, our local instance of Galaxy suddenly started producing errors
for all jobs. This is the trace that gets printed out. Not sure what is
happening because the error doesn’t give much information other than python not
being able to find a module.
Traceback (most recent
