Assaf Gordon wrote:
The same situation happened again on my Galaxy server. How do I check the jobs' ancestors ?
It's non-trivial, you have to query that job's input datasets and then query the state of the job that created those datasets.
Other than the jobs marked 'new', there are no other jobs (running or waiting).
What I currently do is stop the server, Manually reset the jobs, with the following SQL command: UPDATE job set state='error' where state='new' ;
And re-start Galaxy.
Can you try enabling the FIFO queue in universe_wsgi.ini?
There are some side-effects to this operation, as there are no running/waiting jobs but the history-list pane still shows running/waiting jobs.
These should go away if you refresh the history pane? If not, there is something Very Wrong here.
But without this manual intervention, new jobs queued by the users are no started.
'new' state jobs, in general, should not block the queue. This almost seems to indicate that something is killing the job queue thread. Any tracebacks in the log file? --nate