I am having an issue killing jobs via Admin>Manage Jobs. When I try to submit kills I see this in the Galaxy log:
galaxy.jobs.runners.local WARNING 2015-04-19 15:55:03,089 stop_job(): 10374: no PID in database for job, unable to stop
I have updated my local Galaxy server (via hg) and am currently running 17052:28113eee212. I am scared the issue is a database issue, however everything else and communication with the PostgreSQL database seems functional.
Any help greatly appreciated :)
Update: this was a true bug and it is now resolved in the current (15.03) release, through the latest incorporated sub-release. Updating against the distribution will incorporate the correction.
Richard J Poole PhD
Wellcome Trust Fellow
Department of Cell and Developmental Biology
University College London
21 University Street, London WC1E 6DE
Office (518 Rockefeller): +44 20 7679 6577 (int. 46577)
Lab (529 Rockefeller): +44 20 7679 6133 (int. 46133)
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: