I was able to solve this by setting job state in the database from queued and running to "failed" for two jobs that had a wrong state after galaxy-restart.
best,
geert
On 04/02/2013 05:27 PM, Geert Vandeweyer wrote:
Hi,
I'm getting errors in the handler logs after upgrading galaxy stable to today's release.
I specified the "dynamic" job runner as default, which returns a job for pbs.
These errors appear as soon as the server is up and running. What could be the issue here?
galaxy.jobs.runners ERROR 2013-04-02 17:24:23,411 Unhandled exception checking active jobs Traceback (most recent call last): File "/galaxy/galaxy-dist/lib/galaxy/jobs/runners/__init__.py", line 336, in monitor self.check_watched_items() File "/galaxy/galaxy-dist/lib/galaxy/jobs/runners/pbs.py", line 382, in check_watched_items ( failures, statuses ) = self.check_all_jobs() File "/galaxy/galaxy-dist/lib/galaxy/jobs/runners/pbs.py", line 463, in check_all_jobs pbs_server_name = self.__get_pbs_server(pbs_job_state.job_destination.params) File "/galaxy/galaxy-dist/lib/galaxy/jobs/runners/pbs.py", line 221, in __get_pbs_server return job_destination_params['destination'].split('@')[-1] KeyError: 'destination'