Jobs running permanently according to engine

[bertfrees]

According to @josteinaj this has been an issue in the past and he thought it had been resolved already. But on our test server we still have a bunch of jobs that are in the running state forever. I think this is almost always the result of a reboot of the engine while a job was running.

[capitancambio]

Hum, we could do a clean up at start time...

[bertfrees]

Yes maybe that is needed.

[bertfrees]

Same problem with queued jobs (I think. At least the web UI shows them as queued forever).

[capitancambio]

In a second thought I think it would be better to have a force delete than doing an automatic clean-up. It should be safer. I'm going to create an issue in pipeline-issues and close this one
daisy/pipeline#474

[bertfrees]

@egli Can you try the org.daisy.pipeline.ws.cleanuponstartup setting and see if we still get supposedly permanently running jobs in the web UI jobs overview?