Hi all, I've created Trello cards for both of these issues: https://trello.com/card/jobs-stop-jobs-on-history-deletion/506338ce32ae458f6... https://trello.com/card/jobs-stop-job-function-in-jobs-admin-interface-is-br... --nate On Feb 14, 2013, at 2:58 AM, Hans-Rudolf Hotz wrote:

Hi Thon

I can't help you killing the job on the cluster....but regarding the admin section (and the database):

On very rare occasions, we do have jobs (which are not running anymore) but are labelled as "running" on the "Manage jobs" page in the admin section. Using the "Stop Jobs" option does not work to remove them.

So I manually change the state to "error" in the 'job' table, eg:

update job set state='error' where id=12345;

As always, be very careful when you directly access the MySQL or PostgreSQL database!

Regards, Hans-Rudolf

On 02/13/2013 09:14 PM, Anthonius deBoer wrote:

...

Hi,

I am continue to struggle with the proccess of killing jobs that run on the SGE cluster when deleting histories. I would assume that jobs get removed from the queue when a history they are part of is deleted but in most cases, the jobs stay on the cluster and are not killed....

I also never have been able to get the kill jobs in the admin section to work (using the 8-Feb version)...It just sites there, returns and the jobs are still there on the cluster and still there in the database....

Is there anything in the database I can do to really kick out those jobs?

Thanks

Thon

___________________________________________________________ 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:

http://lists.bx.psu.edu/

___________________________________________________________ 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:

http://lists.bx.psu.edu/