Intentionally left blank.
Visit free-pmx website for full-text search of all posts.
Intentionally left blank.
Visit free-pmx website for full-text search of all posts.
TL;DR The unexpected reboot you have encountered might have had nothing to do with any hardware problem. Details on specific Proxmox watchdog setup missing from official documentation.
ORIGINAL POST The Proxmox time bomb watchdog
Intentionally left blank.
Visit free-pmx website for full-text search of all posts.
TL;DR When considering a Quorum Device for small clusters, be aware of other valid alternatives that were taken off the list only due to High Availability stack concerns.
ORIGINAL POST Some lesser known quorum options
TL;DR Distinguish the role of Corosync in Proxmox clusters from the rest of the stack and appreciate the actual reasons behind unexpected reboots or failed quorums.
ORIGINAL POST The Proxmox Corosync fallacy
Intentionally left blank.
Visit free-pmx website for full-text search of all posts.
TL;DR Automate subscription notice suppression to avoid the need for manual intervention during periods of active UI development. No risky scripts with obscure regular expressions that might corrupt the system in the future.
ORIGINAL POST Proxmox VE nag removal, scripted
TL;DR Brief look at what exactly brings up the dreaded notice regarding no valid subscription. Eliminate bad UX that no user of free software should need to endure.
ORIGINAL POST Proxmox VE nag removal, manually
Intentionally left blank.
Visit free-pmx website for full-text search of all posts.
TL;DR Avoid unexpected non-suspect node reboot during maintenance in any High Availability cluster. No need to wait for any grace periods until it becomes inactive by itself, no uncertainties.
ORIGINAL POST How to disable HA for maintenance