Question: Jobs stuck in limbo
gravatar for rr14049
3.3 years ago by
United Kingdom
rr140490 wrote:


I am trying to execute a concatenation of two sets of paired-end reads and although it tells me the job is running it has not reached completion in over 72 hours - none of the files are especially large and the usage of my allocated data quotient is at 94%. Does anyone know what might be holding this up? Many thanks.

Best Wishes

software error • 673 views
ADD COMMENTlink modified 3.3 years ago by Jennifer Hillman Jackson25k • written 3.3 years ago by rr140490
gravatar for Jennifer Hillman Jackson
3.3 years ago by
United States
Jennifer Hillman Jackson25k wrote:


It sounds like the dataset is queued. Do you have other jobs queued or running that were started first? Job run in the order launched and there are quotas on concurrent jobs (dependent on which cluster each is sent to). Also check the input datasets - open them up and note if they any issues (metadata or similar).

I am making the assumption that you are working at (I did not see an account for you there, but it is perhaps under a different name). If you are working somewhere else, this is a local (a brand new local and this is the very first job?), or there is another situation, we can follow up from there.

Best, Jen, Galaxy team

ADD COMMENTlink written 3.3 years ago by Jennifer Hillman Jackson25k
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: 171 users visited in the last hour