[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-arm
Subject:    =?utf-8?q?=5Bfedora-arm=5D?= Re: Watchdog and raspberrypi
From:       Gregory Carter <gjcarter2 () gmail ! com>
Date:       2023-01-08 23:55:18
Message-ID: CAE4jU7jo3_8k=O5qfO0gSbuYyrvW2djA7Kr7QD5=vCZJaGqkiw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


For best results I use a out of band network device to cut power to devices
and reboot them when they fail the watchdog criteria.

Normally they stop pinging or a service isn't responding after a NAGIOS
plugin attempt to restart.

I would have a look at webpowerswitch.com

I use this with PCS and a GFS2 cluster for enforcing and recovering
fencing.   Works well.

On Sat, Jan 7, 2023 at 3:12 PM Pierre-Francois Renard <pfrenard@gmail.com>
wrote:

> Hello guys,
>
>
> I am running 6 RPI4s with fedora 37. K3S is powering this cluster and it
> is working well :)
>
> But from time to time, 1 RPI is randomly hanging.
>
> I am thinking about implementing a watchdog :
>
>   - software based, using embeded linux kernel
>
>   - hardware based such as https://www.omzlo.com/articles/the-piwatcher
>
>
> Do you have any experience on one of theses two solutions ? Do you have
> alternatives ?
>
>
> By the way your job is fantastic and it is a great pleasure to be able
> to run F37 on aarch64 so easily !
>
>
> Thanks a lot
>
> _______________________________________________
> arm mailing list -- arm@lists.fedoraproject.org
> To unsubscribe send an email to arm-leave@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>

[Attachment #5 (text/html)]

<div dir="ltr"><div>For best results I use a out of band network device to cut power \
to devices and reboot them when they fail the watchdog \
criteria.</div><div><br></div><div>Normally they stop pinging or a service isn&#39;t \
responding after a NAGIOS plugin attempt to restart.</div><div><br></div><div>I would \
have a look at <a href="http://webpowerswitch.com">webpowerswitch.com</a></div><div><br></div><div>I \
use this with PCS and a GFS2 cluster for enforcing and recovering fencing.     Works \
well.<br></div></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Sat, Jan 7, 2023 at 3:12 PM Pierre-Francois Renard &lt;<a \
href="mailto:pfrenard@gmail.com">pfrenard@gmail.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello guys,<br> <br>
<br>
I am running 6 RPI4s with fedora 37. K3S is powering this cluster and it <br>
is working well :)<br>
<br>
But from time to time, 1 RPI is randomly hanging.<br>
<br>
I am thinking about implementing a watchdog :<br>
<br>
    - software based, using embeded linux kernel<br>
<br>
    - hardware based such as <a href="https://www.omzlo.com/articles/the-piwatcher" \
rel="noreferrer" target="_blank">https://www.omzlo.com/articles/the-piwatcher</a><br> \
<br> <br>
Do you have any experience on one of theses two solutions ? Do you have <br>
alternatives ?<br>
<br>
<br>
By the way your job is fantastic and it is a great pleasure to be able <br>
to run F37 on aarch64 so easily !<br>
<br>
<br>
Thanks a lot<br>
<br>
_______________________________________________<br>
arm mailing list -- <a href="mailto:arm@lists.fedoraproject.org" \
target="_blank">arm@lists.fedoraproject.org</a><br> To unsubscribe send an email to \
<a href="mailto:arm-leave@lists.fedoraproject.org" \
target="_blank">arm-leave@lists.fedoraproject.org</a><br> Fedora Code of Conduct: <a \
href="https://docs.fedoraproject.org/en-US/project/code-of-conduct/" rel="noreferrer" \
target="_blank">https://docs.fedoraproject.org/en-US/project/code-of-conduct/</a><br> \
List Guidelines: <a href="https://fedoraproject.org/wiki/Mailing_list_guidelines" \
rel="noreferrer" target="_blank">https://fedoraproject.org/wiki/Mailing_list_guidelines</a><br>
 List Archives: <a href="https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org" \
rel="noreferrer" target="_blank">https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org</a><br>
 Do not reply to spam, report it: <a \
href="https://pagure.io/fedora-infrastructure/new_issue" rel="noreferrer" \
target="_blank">https://pagure.io/fedora-infrastructure/new_issue</a><br> \
</blockquote></div>


[Attachment #6 (text/plain)]

_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


[prev in list] [next in list] [prev in thread] [next in thread]