I get this error occasionally:

"/bin/sh: 1: 
Text file busy"

When this occurs, the step fails outright. Resubmitting the step
resolves the issue and things run no problem. If this error appears
early in a long workflow, I have to manually resubmit ALL dependent
steps... what a pain!

Perhaps this is something the Galaxy job scheduler can look out for,
flush() the system, sleep() a second or two to let the file write and
close, and then rerun. A more fault-tolerant way of running workflows
without unnecessary human intervention.

-Evan Bollig
Research Associate | Application Developer | User Support Consultant
Minnesota Supercomputing Institute
599 Walter Library
612 624 1447
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:

To search Galaxy mailing lists use the unified search at:

Reply via email to