From: dORSY via pve-user <pve-user@lists.proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Marco Gaiarin <gaio@lilliput.linux.it>
Cc: dORSY <dorsyka@yahoo.com>
Subject: Re: [PVE-User] Hardware watchdog for standalone server...
Date: Mon, 19 Aug 2024 19:10:48 +0000 (UTC) [thread overview]
Message-ID: <mailman.318.1724094668.302.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <ZsNoAsFPQ1xNiNhf@sv.lnf.it>
[-- Attachment #1: Type: message/rfc822, Size: 9329 bytes --]
From: dORSY <dorsyka@yahoo.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>, Marco Gaiarin <gaio@lilliput.linux.it>
Subject: Re: [PVE-User] Hardware watchdog for standalone server...
Date: Mon, 19 Aug 2024 19:10:48 +0000 (UTC)
Message-ID: <364231406.5096226.1724094648740@mail.yahoo.com>
don't really get what you want/need exactly, but for single hosts i'd start at
bmc-watchdog(8) - Linux man page
|
|
|
| | |
|
|
|
| |
bmc-watchdog(8) - Linux man page
bmc-watchdog controls a Baseboard Management Controller (BMC) watchdog timer. The bmc-watchdog tool typically executes as a cronjob or daemon to manage the ...
| |
|
|
it needs hw support to work (ipmi)i last used a daemon like this on freeBSD storage servers.hope this helps.
On Mon, Aug 19, 2024 at 17:45, Marco Gaiarin<gaio@lilliput.linux.it> wrote: Mandi! Alwin Antreich
In chel di` si favelave...
> Dow you want to make your VM/CT HA? That only works reliably with 3x nodes for
> quorum (or 2x nodes & qdevice) [0].
I know. No. I'm speaking about standalone servers.
> But if you want to reset a node if it doesn't spin up a watchdog (doesn't
> respond), then you could use systemd watchdog[1].
I'm saying EXACTLY that (also for dORSY): i need some sort of watchdog daemon,
or the HA watchdog daemon 'watchdog-mux' works even in standalone setup?
> Though I'd like to add that
> resetting nodes continuously (issue is reoccurring), increases the chances for
> data corruption.
If there's some hardware or other trouble that trigger watchdog, typically
the box is just TOFU and a reset cannot do more harm... at least this is my
experience.
--
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2024-08-19 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 13:39 Marco Gaiarin
2024-08-19 14:17 ` dORSY via pve-user
2024-08-19 14:47 ` Alwin Antreich via pve-user
[not found] ` <11e39814096a53c52422b9f2114719dd5ad73090@antreich.com>
2024-08-19 15:42 ` Marco Gaiarin
2024-08-19 19:10 ` dORSY via pve-user [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.318.1724094668.302.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=dorsyka@yahoo.com \
--cc=gaio@lilliput.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal