"paused job" still in "blue" - does it mean it's not "resumed" ?

Question: "paused job" still in "blue" - does it mean it's not "resumed" ?

3.9 years ago by

BC357 • 70

United States

BC357 • 70 wrote:

I was told today while running multiple jobs at usegalaxy that two of the them were paused (No explanation - is there supposed to be one?).

I followed the instruction, clicked on the history menu to resume one and was quickly prompted with the message "Your jobs have been resumed". However, after a few minutes of waiting and after refreshing the history, the job was still "blue" in the queue and showed no sign of being resumed.

Not sure if they are related but two other jobs yesterday were in gray for a long while (>1 hr) (while similar jobs (size-wise and task-wise) submitted around the same time went through fine). I killed the tasks later as I succeeded in using a different approach. Today another two jobs were also in gray - as of now - close to 30 min - while other similar jobs have been finished. Are all these "somehow related" - any issue regarding my account ? - or just a generally slow day in computation.

My account is only half full (using 46% as we speak).

Any suggestion? Thank you.

paused jobs • 1.1k views

ADD COMMENT • link •

modified 3.9 years ago by Jennifer Hillman Jackson ♦ 25k • written 3.9 years ago by BC357 • 70

3.9 years ago by

Jennifer Hillman Jackson ♦ 25k

United States

Jennifer Hillman Jackson ♦ 25k wrote:

Hello,

This indicates that one or more of the inputs has a problem. Are these the ones that you deleted?

Thanks, Jen, Galaxy team

ADD COMMENT • link written 3.9 years ago by Jennifer Hillman Jackson ♦ 25k

<original message cancelled> please see the new one

ADD REPLY • link modified 3.9 years ago • written 3.9 years ago by BC357 • 70

Just noticed that I got TWO jobs with the same "history number" (both labelled as 162). Both were running Varscan on the same pileup data. What's odd is one is done (in green), the other showed "tool error" (in pink). The paused job DID require output from the Varscan step so I assumed it was "paused" because of this "confusion". I will kill and purge all "paused" and "queued" jobs in my history and re-submit them. WIll report back if I should encounter issues. Thank you.

ADD REPLY • link written 3.9 years ago by BC357 • 70

Hi, We would like to check out your history if you have time. Submit one of the error datasets as a bug report (click on the green bug) and include a pasted in link to this post in the comments. If you don't have any error datasets, you can share the history (History panel -> Share or Publish -> use first button to generate a share link -> copy that into an email sent to galaxy-bugs at lists dot galaxyproject dot org) plus this post URL. Please include your Galaxy account email address if you send in mail direct. You do not need to send in your password (to anyone, ever). The list I shared is private to our team only. Thanks! Jen, Galaxy team

ADD REPLY • link modified 3.9 years ago • written 3.9 years ago by Jennifer Hillman Jackson ♦ 25k

One uninformative error dataset created today, which stated "

This job failed for reasons that could not be determined.
Please click the bug icon to report this problem if you need help."

So I will have the requested info emailed to the address above. Please let me know if more info is needed. Thank you.

ADD REPLY • link written 3.9 years ago by BC357 • 70

Great, I will watch for it. Thanks for reporting the problem, Jen, Galaxy team

ADD REPLY • link written 3.9 years ago by Jennifer Hillman Jackson ♦ 25k

Similar posts • Search »