My guess is that you have a situation where Workflow could not monitor the
job completion status of one of the distributed jobs and hence it is
waiting. One solution is to kill the pipeline and restart. Workflow most
likely will pick up the current state and continue. What version of
workflow are you running? Another option is for us to debug, but in my
experience it is hard to debug without a log file. Could you look for the
pipeline.xml.log and the iterator log file and send it if you want me to
debug.
Anup
On 10/27/11 7:29 PM, "Gary Xie" <
[hidden email]> wrote:
>Running bacterial genome on Ergatis pipeline locally, but it stuck at
>the tRNAscan step for 10 days. Following is error message, any insight?
>Thanks,
>Gary
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev_______________________________________________
Ergatis-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/ergatis-users