I am fairly new at this, but have configured a 5 node cluster with HA
I was wondering why ha-manaager shows PVE26 "old timestamp - dead?" but pvecm shows as active?
Also ha-manager config shows ct300 state STARTED vs ha-manager status shows as FREEZE
I am guessing I misconfigured something somewhere, but not sure how to correct
TIA
I was wondering why ha-manaager shows PVE26 "old timestamp - dead?" but pvecm shows as active?
Code:
root@pve26:~# ha-manager status
master pve28 (active, Sat Feb 10 13:40:02 2024)
lrm pve22 (active, Sat Feb 10 13:39:54 2024)
lrm pve24 (active, Sat Feb 10 13:39:55 2024)
lrm pve26 (old timestamp - dead?, Thu Oct 19 08:19:58 2023)
lrm pve27 (idle, Sat Feb 10 13:40:02 2024)
lrm pve28 (idle, Sat Feb 10 13:40:03 2024)
service ct:300 (pve26, freeze)
service ct:303 (pve24, started)
service ct:320 (pve24, started)
service vm:105 (pve22, started)
service vm:150 (pve24, started)
Code:
root@pve26:~# pvecm status
Cluster information
-------------------
Name: HomeLab
Config Version: 27
Transport: knet
Secure auth: on
Quorum information
------------------
Date: Sat Feb 10 13:43:21 2024
Quorum provider: corosync_votequorum
Nodes: 5
Node ID: 0x00000002
Ring ID: 1.1328
Quorate: Yes
Votequorum information
----------------------
Expected votes: 5
Highest expected: 5
Total votes: 5
Quorum: 3
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 192.168.111.24
0x00000002 1 192.168.111.26 (local)
0x00000003 1 192.168.111.28
0x00000004 1 192.168.111.22
0x00000005 1 192.168.111.27
Also ha-manager config shows ct300 state STARTED vs ha-manager status shows as FREEZE
Code:
root@pve26:~# ha-manager config
ct:300
group Group26_28
state started
ct:303
group group24_28
state started
ct:320
group Group24_26
state started
vm:105
group Group22_24
state started
vm:150
group Group24_26_28
state started
I am guessing I misconfigured something somewhere, but not sure how to correct
TIA