Elastix reboot: cron job?
-
@g.jacobse said:
@thecreativeone91 said:
@g.jacobse said:
Thanks for the additional tags
As for e mail, it would be nice to get a health report on successful boot.
No report, something is wrong....
That's backwards you want emails when something fails. I'd get way too many if I got once when things worked I easily get 200+ per day already.
I rant that over in my mind, and it seemed that if the reboot failed, you would not get any type of email.
If you have the device itself send the emails. But normally you'd have something else checking status of the network services that would email you after X number of failed attempts to contact the device. We use OpManager for this but there are free tools to do it, spiceworks though bloated can do it. And there's a million and one linux based network monitoring tools.
-
@thecreativeone91 said:
@g.jacobse said:
@thecreativeone91 said:
@g.jacobse said:
Thanks for the additional tags
As for e mail, it would be nice to get a health report on successful boot.
No report, something is wrong....
That's backwards you want emails when something fails. I'd get way too many if I got once when things worked I easily get 200+ per day already.
I rant that over in my mind, and it seemed that if the reboot failed, you would not get any type of email.
If you have the device itself send the emails. But normally you'd have something else checking status of the network services that would email you after X number of failed attempts to contact the device. We use OpManager for this but there are free tools to do it, spiceworks though bloated can do it. And there's a million and one linux based network monitoring tools.
Icinga is really good. I've got a Nagios server deployed right now to do this type of thing, that works fairly well although I really haven't dug too deeply into it.
-
@thecreativeone91 said:
@g.jacobse said:
Thanks for the additional tags
As for e mail, it would be nice to get a health report on successful boot.
No report, something is wrong....
That's backwards you want emails when something fails. I'd get way too many if I got once when things worked I easily get 200+ per day already.
Exactly. Think of emails as an alert. Logging success (somewhere, not email) is good so that you can always have that worried feeling and go look it up. Or just show someone why and when the reboot happened with some definitive info. But don't log to the alert system, save it for alerting. Make your emails matter.
-
@g.jacobse said:
I rant that over in my mind, and it seemed that if the reboot failed, you would not get any type of email.
If the reboot failed to run completely (like the system was down, cron had crashed, things were frozen) you would get no email either. You are making the system report on itself with is not good.
That's why the system should reboot itself (no way around that) but the monitoring of whether it is up or not should be done externally.
