Cronicle icon indicating copy to clipboard operation
Cronicle copied to clipboard

How to properly restart all cronicle servers

Open asyslinux opened this issue 6 years ago • 2 comments

Hello, i have a question about properly restart cronicle servers.

This is need for reload new SSL certificate/key in all cronicle servers(master,backup,slaves). But when I use bin/control.sh restart some of my tasks report about "shutdown unexpectedly"

May be have a solution by api for waiting task, then restart, or change all currently running tasks to uninterruptable mode?

Thank You.

asyslinux avatar Nov 01 '19 07:11 asyslinux

Hey there,

I'm sorry to report that there is currently no way to do this. Cronicle is designed to abort all jobs on shutdown, unless they are detached events. There's also no way to convert a running job to detached either, sorry.

Apologies for this. I will try to come up with something better in the big v2.0 rewrite (coming next year). In the meantime, I will leave this issue open.

jhuckaby avatar Nov 02 '19 02:11 jhuckaby

@jhuckaby Since this issue has been open over a year now, would it be reasonable to ask for a graceful shutdown option that lets all jobs complete, and any continuous/chain reaction jobs not execute their chains, and not start any scheduled jobs that would have started after the graceful shutdown has been initiated?

Edited to add: Looks like #243 is asking for exactly this.

dossy avatar Mar 03 '21 22:03 dossy