Hi <br><br><br>In my galaxy instance, whatever jobs i am submitting it goes into queued state. <br>If I restart the server then  the previous submitted jobs state changes to running. but the newly submitted jobs again goes to queued state.<br>
<br>I am at a loss to understand this behaviour of galaxy and unable to debug it. The job submission uses a customized runner. <br>How is it actually goes into the queued state automatically when all the workers thread are free?<br>
Does galaxy_session table is_valid attribute makes jobs state true?<br>Or what all places in tables the queued states are getting stored. I can only see that the jobs table state attribute only stores the state.<br><br>The server logs points error here: <br>
<br><a href="http://galaxy.jobs">galaxy.jobs</a> ERROR 2011-07-29 11:01:28,098 failure running job 2243<br>Traceback (most recent call last):<br>  File &quot;/home/gwadmin/galaxy-central/lib/galaxy/jobs/__init__.py&quot;, line 202, in __monitor_step<br>
    self.dispatcher.put( JobWrapper( job, self ) )<br>  File &quot;/home/gwadmin/galaxy-central/lib/galaxy/jobs/__init__.py&quot;, line 856, in put<br>    self.job_runners[runner_name].put( job_wrapper )<br>  File &quot;/home/gwadmin/galaxy-central/lib/galaxy/jobs/runners/gw.py&quot;, line 375, in put<br>
    job_wrapper.change_state( model.Job.states.QUEUED )<br>  File &quot;/home/gwadmin/galaxy-central/lib/galaxy/jobs/__init__.py&quot;, line 437, in change_state<br>    self.sa_session.flush()<br><br><br>Regards<br>Karuna<br>
<br>