Timeline for How to set up a basic heartbeat monitor
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 18, 2020 at 23:06 | comment | added | dimo414 |
Sure, but there are plenty of situations (again, such as a bad network config) that are not fixed by a reboot. I appreciate the pointer to watchdog, but it just doesn't seem appropriate for the goal of notifying when the device is in a bad state. watchdog can attempt to fix the problem, but if it's unable to do so you're no better off than if you hadn't set it up at all.
|
|
| Mar 18, 2020 at 10:18 | comment | added | Ingo | @dimo414 watchdog is supported by the kernel. It's not necessary that watchdog runs as long as the kernel itself runs. If watchdog fails it does not trigger the kernel and the kernel do what it can in the failing state, mostly just reboot. | |
| Mar 18, 2020 at 1:07 | comment | added | dimo414 | The problem with any sort of local monitoring utility is it's dependent of the system being in a healthy enough state to execute the watchdog in the first place. For example if the system loses its network connection no email notifications will be getting out :) | |
| Mar 17, 2020 at 19:51 | comment | added | Ingo | @goldilocks Then the problem with sending an email always persist, no matter what application do you use. It seems to be a general problem. | |
| Mar 17, 2020 at 17:17 | comment | added | goldilocks♦ |
Probably worth noting that "sending an email" this way is very far from trivial, unless it is to a user on the same machine. Beyond that you need the services of a bona fide email server. Which does not exist on the Pi by default, so you would need to make arrangements...nothing in the man page about that (man watchdog.conf is no more helpful), which implies it uses the system sendmail, which, again, making that work is going to be a lot of work.
|
|
| Mar 17, 2020 at 12:50 | history | answered | Ingo | CC BY-SA 4.0 |