Joseph Huckaby
Joseph Huckaby
This is normal. Cronicle doesn't use a database, so it writes many files to disk. Every job consists of many different files, for keeping track of things like the event...
First, I have to point out, although I don't think it is relevant to this issue, you're running Node version 10.19. This is very old, and unsupported. I highly recommend...
Ah, very clever! I did not know `ulimit` could govern memory in that way. Nice solution!
Yup, this is a known issue / limitation with Cronicle v0. HTTPS/SSL isn't really supported, and especially not at the websocket (server-to-server) level. The whole system needs to be ripped...
I don't think there's a way to get what you want here. Cronicle does have a feature in the UI where it can interpret a cron expression, and convert it...
Alas, Cronicle doesn't support automatic adding of workers that it detects in the nearby LAN. They all have to be manually added. That highlighted `worker` item you see in your...
> Being a bit annoying, but just to confirm: in version 2.0 there will also be no support (at least nothing planned for now) for clustering of self-discovered and 'self-assigned'...
(Ugh, I need to stop saying "master". I meant primary! Sorry, old habits.)
See: https://github.com/jhuckaby/Cronicle/discussions/479
I've never heard of this happening before. I run a large Cronicle cluster of many servers on live production for months at a time, with no issues like this. It...