From: galaxy-dev-boun...@lists.bx.psu.edu
[mailto:galaxy-dev-boun...@lists.bx.psu.edu] On Behalf Of Aaron Petkau
Sent: Wednesday, October 01, 2014 5:32 PM
To: Lance Parsons
Cc: galaxy-dev@lists.bx.psu.edu
Subject: Re: [galaxy-dev] Jobs stuck in new state - Data Library datasets
to blame?
Are you
-boun...@lists.bx.psu.edu] On Behalf Of Aaron Petkau
Sent: Wednesday, October 01, 2014 5:32 PM
To: Lance Parsons
Cc: galaxy-dev@lists.bx.psu.edu
Subject: Re: [galaxy-dev] Jobs stuck in new state - Data Library datasets
to blame?
Are you attempting to upload datasets to a Data Library
Kandalaft
From: galaxy-dev-boun...@lists.bx.psu.edu
[mailto:galaxy-dev-boun...@lists.bx.psu.edu] On Behalf Of Aaron Petkau
Sent: Wednesday, October 01, 2014 5:32 PM
To: Lance Parsons
Cc: galaxy-dev@lists.bx.psu.edu
Subject: Re: [galaxy-dev] Jobs stuck in new state - Data Library datasets
:*galaxy-dev-boun...@lists.bx.psu.edu
[mailto:galaxy-dev-boun...@lists.bx.psu.edu] *On Behalf Of *Aaron Petkau
*Sent:* Wednesday, October 01, 2014 5:32 PM
*To:* Lance Parsons
*Cc:* galaxy-dev@lists.bx.psu.edu
*Subject:* Re: [galaxy-dev] Jobs stuck in new state - Data Library
datasets to blame
[mailto:galaxy-dev-boun...@lists.bx.psu.edu] *On Behalf Of *Aaron Petkau
*Sent:* Wednesday, October 01, 2014 5:32 PM
*To:* Lance Parsons
*Cc:* galaxy-dev@lists.bx.psu.edu
*Subject:* Re: [galaxy-dev] Jobs stuck in new state - Data Library
datasets to blame?
Are you attempting to upload datasets to a Data
: [galaxy-dev] jobs stuck in new state
Sent by:galaxy-dev-boun...@lists.bx.psu.edu
Hi David,
This is pretty common in the case of workflows. When a workflow step
fails, the next job in the workflow will be set to the paused state and
all jobs downstream of the paused job will remain
In my case it was uncompleted metadata in one of the input files.
(but maybe it was not new state but something else?)
HTH,
ido
On Mar 26, 2014, at 5:25 PM, David Hoover hoove...@helix.nih.gov wrote:
I have many jobs stuck in the 'new' state on our local Galaxy instance. The
jobs can't be
This turned out to be my own ignorance. After creating identical handlers in
both universe_wsgi.ini and job_conf.xml, and restarting Galaxy in daemon mode,
the jobs became resilient to Galaxy restarts. DOH!
Thanks Nate for pointing this out, as well as the limits collection.
David
On Mar
Hi David,
This is pretty common in the case of workflows. When a workflow step fails,
the next job in the workflow will be set to the paused state and all jobs
downstream of the paused job will remain in the new state until
corrective action is taken. The current query for finding
