Hi I am on the enterprise edition of Eramba.
I have never bothered to post about this before, but for the past couple of years, EVERY time I install an Eramba update, I always immediately get System Health warnings when I log back in. It’s rather alarming, but it always just turns out to be that one of more of the cron jobs hasn’t restarted yet (Worker, Hourly, Daily, Yearly…) If I wait a while (minutes, hours, an afternoon…) they always eventually restart and System Health stops complaining.
Is there no way for the update progress to make sure these crons restart, as part of the update? So we don’t get these spurious error messages every time?
Hello David,
The reason for this is that after an update, the crons are terminated, and the system waits for the new crons to start running with the updated image (files). This process can, of course, take some time.
At the moment, there are no plans to address this further. Apologies for any inconvenience.
Regards
Sam