Question: 'waiting to run'
gravatar for simon.schiml
3.0 years ago by
simon.schiml10 wrote:


I have started a couple of lastz alignments on on sunday and since then, they are on 'waiting to run' status. I know that I have to be patient, and that installing galaxy locally can speed up jobs, but two days seem like an unusual long time to me, and I just wanted to make sure that everything is alright with these jobs on both ends. The jobs were not cancelled or re-run yet.

I did some test-alignments with smaller datasets just before i started these jobs on sunday and they ran directly.

Do you have any advice for me in this regard?




alignment • 724 views
ADD COMMENTlink modified 3.0 years ago by Jennifer Hillman Jackson25k • written 3.0 years ago by simon.schiml10
gravatar for Jennifer Hillman Jackson
3.0 years ago by
United States
Jennifer Hillman Jackson25k wrote:


The jobs look OK to me. The Lastz settings are on the permissive side, which may result in jobs that run out of resource (memory or time), but that cannot be accurately determined until these actually execute. For the wait a bit over 24 hrs, the explanation is that the cluster is very busy right now. More details about queued jobs is in this prior post: A: Galaxy "This job is waiting to run" - but it never runs!!

Thank you for your patience, Jen, Galaxy team

ADD COMMENTlink written 3.0 years ago by Jennifer Hillman Jackson25k


thank you for your answer. I did read older posts concerning this problem and I am aware that a busy cluster can cause delays. However, it's been almost 70 hours of waiting now, which just seems unusual to me. Is there any way to estimate when these jobs will start running?

ADD REPLYlink written 3.0 years ago by simon.schiml10
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 181 users visited in the last hour