proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-04-30 01:15:02 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

pvecm: describe new coldstart behaviour

Browse Source
This commit is contained in:
Dietmar Maurer 2016-09-09 11:58:45 +02:00
parent 08152ae6f2
commit 612417fdcf
1 changed files with 6 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
pvecm.adoc
View File

@ -311,18 +311,13 @@ NOTE: It is always a good idea to use an uninterruptible power supply
('UPS', also called 'battery backup') to avoid this state. Especially if ('UPS', also called 'battery backup') to avoid this state. Especially if
you want HA. you want HA.
On node startup, service 'pve-manager' waits up to 60 seconds to reach On node startup, service 'pve-manager' is started and waits for
quorum, and then starts all guests. If it fails to get quorum, that quorum. Once quorate, it starts all guests which have the 'onboot'
service simply aborts, and you need to start your guest manually once flag set.
you have quorum.
If you start all nodes at the same time (for example when power comes When you turn on nodes, or when power comes back after power failure,
back), it is likely that you reach quorum within above timeout. But it is likely that some nodes boots faster than others. Please keep in
startup can fail if some nodes starts much faster than others, so you mind that guest startup is delayed until you reach quorum.
need to start your guest manually after reaching quorum. You can do
that on the GUI, or on the command line with:
systemctl start pve-manager
ifdef::manvolnum[] ifdef::manvolnum[]