Re: [galaxy-dev] Some workflows not scheduled until handler restart

2016-01-08 Thread John Chilton
I've been swamped with release related things but my intention is to dig deeply into this. This is a very serious bug. A work around is just to disable beta workflow scheduling for now: switch force_beta_workflow_scheduled_min_steps=1 force_beta_workflow_scheduled_for_collections=True to force_

Re: [galaxy-dev] Some workflows not scheduled until handler restart

2016-01-08 Thread Charles Girardot
Hi all, I work with Jelle and want to add on the issue. Help would be *greatly* appreciated as this is a *major* stopper on our production server right now. In the database ‘workflow_invocation' table, one can see a ’state’ column with values like ’scheduled’ or ‘failed’. Before december 1

[galaxy-dev] Some workflows not scheduled until handler restart

2016-01-05 Thread Jelle Scholtalbers
Hi all, On our installation (v15.07) we suddenly see that one of two job handlers get stuck with a high cpu load (last message generally, `cleaning up external metadata files`) without new messages appearing. In addition, when running workflows in batch (>6x), only a few of them (~3) get their wor