Hi Sascha,
Can you see these jobs in "manage jobs", under the admin menu? Maybe you can kill them from there.
David
From: s.kastens@gatc-biotech.com To: galaxy-dev@lists.bx.psu.edu Date: Tue, 7 Aug 2012 11:08:21 +0200 Subject: [galaxy-dev] Job recovery of non existing job
Hi all,
I’m running a local instance of Galaxy and every time I start it, Galaxy tries to recover some jobs. These jobs are not running anymore and I get the following information:
galaxy.jobs DEBUG 2012-08-07 10:58:08,056 (418) Working directory for job is: /mnt/sec1/bioit/galaxy_working_dir/000/418 galaxy.jobs.handler DEBUG 2012-08-07 10:58:08,089 recovering job 418 in drmaa runner galaxy.jobs.runners.drmaa DEBUG 2012-08-07 10:58:08,090 (418/277560) is still in running state, adding to the DRM queue
Is there a way to clean the job handler queue? I tried to start Galaxy with ’enable_job_recovery = False’ but that did not solve the problem.
Cheers, Sascha
___________________________________________________________ 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: