mikeTWC1984

I think running cronicle as root is not good idea. I also don't see out of the box option to run it as non-root. I think installation should create some...

@schnurlosdusche I think the problem with non-root is that you won't be able to spawn child job as different user. Over time I came to conclusion that it's better idea...

@schnurlosdusche If you don't share access to cronicle much I guess you can run it as non root. Root helps to control access to certain files, if its not an...

That error comes from UI, not from server. I guess your server is just overwhelmed when you see that error. Is it pulling get_history every 500 ms or you meant...

OK. 5 seconds is not that bad. Do you think that history polling is killing it, or it would happen regardless? do you set any limit to the history request?...

Did you add that backup to server list (in primary server UI?) If you are looping in "waiting for master" this means server name is not matching master group or...

Probably file with event history is missing. Check files under data/logs/events/. I guess there should be json files with eventid names.

I believe in actual cron */7 also means "every January and August", not "every 7 months". Cron is stateless (doesn't keep initial start time), so it can't really handle uneven...

No, it won't work on windows. It's using things like symlinks and linux style permissions/execution. As far as I remember it also uses ps utility to grab server stats. Probably...

@srgoogle23 Could be also network issue. Are those machines have static IPs? Anyway you can check logs/Cronicle.log file, see if cronicle was crashing/restarting, or maybe VM restarted itself. Doesn't sound...