I submitted a workflow that in turn submits a drm job to sun grid engine.

The queue had an error (probably due to a problem with automount). 

Traceback (most recent call last):
  File "/inside/depot4/galaxy/lib/galaxy/jobs/runners/__init__.py", line 60, in 
  File "/inside/depot4/galaxy/lib/galaxy/jobs/runners/drmaa.py", line 169, in 
    external_job_id = self.ds.runJob(jt)
  File "/inside/depot4/galaxy/eggs/drmaa-0.4b3-py2.7.egg/drmaa/__init__.py", 
line 331, in runJob
    _h.c(_w.drmaa_run_job, jid, _ct.sizeof(jid), jobTemplate)
  File "/inside/depot4/galaxy/eggs/drmaa-0.4b3-py2.7.egg/drmaa/helpers.py", 
line 213, in c
    return f(*(args + (error_buffer, sizeof(error_buffer))))
  File "/inside/depot4/galaxy/eggs/drmaa-0.4b3-py2.7.egg/drmaa/errors.py", line 
90, in error_check
    raise _ERRORS[code-1]("code %s: %s" % (code, error_buffer.value))
DeniedByDrmException: code 17: error: no suitable queues

When the sysadmin cleared the error, the job started running normally after 
being in an error state for 10 minutes.

The cool thing is that galaxy kept running without a problem.

galaxy.jobs.runners.drmaa DEBUG 2013-06-27 14:51:22,968 (10481/4767487) state 
change: job is running
galaxy.jobs.runners.drmaa DEBUG 2013-06-27 15:00:23,628 (10481/4767487) state 
change: job is queued and active
galaxy.jobs.runners.drmaa DEBUG 2013-06-27 15:00:27,751 (10481/4767487) state 
change: job is running

However in the history panel, the job shows as queued but not running, even if 
I refresh the history panel.

Is this normal or should the status change to running?

I'm using this version of straight galaxy:

changeset:   10162:f295092476c7
branch:      stable
parent:      10160:2efb1083676b
user:        Dannon Baker <dannonba...@me.com>
date:        Sat Jun 15 09:08:09 2013 -0400
summary:     Fix reports import issue reported by Lance, 

-Robert Baertsch
UC Santa Cruz

Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

To search Galaxy mailing lists use the unified search at:

Reply via email to