[PVE-User] Missing node in ha-manager
Mark Schouten
mark at tuxis.nl
Wed May 3 09:45:49 CEST 2017
On Tue, 2017-05-02 at 09:05 +0200, Thomas Lamprecht wrote:
> Can you control that the config looks the same on all nodes?
> Especially the difference between working and misbehaving nodes would
> be
> interesting.
Please see the attachment. That includes /etc/pve/.members and
/etc/pve/corosync.conf from all nodes. Only the .members file of the
misbehaving node is off.
> In general you could just restart CRM, but the CRM is capable of
> syncing
> in new nodes while running, so there shouldn't be any need for that,
> the
> patches you linked also do not change that, AFAIK.
I would like to do a sync without a restart as well, but what would
trigger this?
> As /etc/pve.members doesn't shows the new node on the misbehaving
> one
> the problem is another one.
> Who is the current master? Can you give me an output of:
> # ha-manager status
> # pvecm status
> # cat /etc/pve/corosync.conf
Output in the attachment. Because the misbehaving node also is the
master, output of ha-manager is identical on all nodes.
--
Kerio Operator in de Cloud? https://www.kerioindecloud.nl/
Mark Schouten | Tuxis Internet Engineering
KvK: 61527076 | http://www.tuxis.nl/
T: 0318 200208 | info at tuxis.nl
-------------- next part --------------
root at proxmox01:~# cat /etc/pve/.members
{
"nodename": "proxmox01",
"version": 23,
"cluster": { "name": "redacted01", "version": 4, "nodes": 4, "quorate": 1 },
"nodelist": {
"proxmox02": { "id": 2, "online": 1, "ip": "10.1.1.2"},
"proxmox01": { "id": 1, "online": 1, "ip": "10.1.1.1"},
"proxmox04": { "id": 4, "online": 1, "ip": "10.1.1.4"},
"proxmox03": { "id": 3, "online": 1, "ip": "10.1.1.3"}
}
}
root at proxmox02:~# cat /etc/pve/.members
{
"nodename": "proxmox02",
"version": 21,
"cluster": { "name": "redacted01", "version": 4, "nodes": 4, "quorate": 1 },
"nodelist": {
"proxmox02": { "id": 2, "online": 1, "ip": "10.1.1.2"},
"proxmox01": { "id": 1, "online": 1, "ip": "10.1.1.1"},
"proxmox04": { "id": 4, "online": 1, "ip": "10.1.1.4"},
"proxmox03": { "id": 3, "online": 1, "ip": "10.1.1.3"}
}
}
root at proxmox03:~# cat /etc/pve/.members
{
"nodename": "proxmox03",
"version": 24,
"cluster": { "name": "redacted01", "version": 3, "nodes": 3, "quorate": 1 },
"nodelist": {
"proxmox02": { "id": 2, "online": 1, "ip": "10.1.1.2"},
"proxmox03": { "id": 3, "online": 1, "ip": "10.1.1.3"},
"proxmox01": { "id": 1, "online": 1, "ip": "10.1.1.1"}
}
}
root at proxmox04:~# cat /etc/pve/.members
{
"nodename": "proxmox04",
"version": 6,
"cluster": { "name": "redacted01", "version": 4, "nodes": 4, "quorate": 1 },
"nodelist": {
"proxmox02": { "id": 2, "online": 1, "ip": "10.1.1.2"},
"proxmox01": { "id": 1, "online": 1, "ip": "10.1.1.1"},
"proxmox04": { "id": 4, "online": 1, "ip": "10.1.1.4"},
"proxmox03": { "id": 3, "online": 1, "ip": "10.1.1.3"}
}
}
root at proxmox01:~# cat /etc/pve/corosync.conf
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: proxmox02
nodeid: 2
quorum_votes: 1
ring0_addr: proxmox02
}
node {
name: proxmox04
nodeid: 4
quorum_votes: 1
ring0_addr: proxmox04
}
node {
name: proxmox01
nodeid: 1
quorum_votes: 1
ring0_addr: proxmox01
}
node {
name: proxmox03
nodeid: 3
quorum_votes: 1
ring0_addr: proxmox03
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: redacted01
config_version: 4
ip_version: ipv4
secauth: on
version: 2
interface {
bindnetaddr: 10.1.1.1
ringnumber: 0
}
}
root at proxmox02:~# cat /etc/pve/corosync.conf
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: proxmox02
nodeid: 2
quorum_votes: 1
ring0_addr: proxmox02
}
node {
name: proxmox04
nodeid: 4
quorum_votes: 1
ring0_addr: proxmox04
}
node {
name: proxmox01
nodeid: 1
quorum_votes: 1
ring0_addr: proxmox01
}
node {
name: proxmox03
nodeid: 3
quorum_votes: 1
ring0_addr: proxmox03
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: redacted01
config_version: 4
ip_version: ipv4
secauth: on
version: 2
interface {
bindnetaddr: 10.1.1.1
ringnumber: 0
}
}
root at proxmox03:~# cat /etc/pve/corosync.conf
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: proxmox02
nodeid: 2
quorum_votes: 1
ring0_addr: proxmox02
}
node {
name: proxmox04
nodeid: 4
quorum_votes: 1
ring0_addr: proxmox04
}
node {
name: proxmox01
nodeid: 1
quorum_votes: 1
ring0_addr: proxmox01
}
node {
name: proxmox03
nodeid: 3
quorum_votes: 1
ring0_addr: proxmox03
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: redacted01
config_version: 4
ip_version: ipv4
secauth: on
version: 2
interface {
bindnetaddr: 10.1.1.1
ringnumber: 0
}
}
root at proxmox04:~# cat /etc/pve/corosync.conf
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: proxmox02
nodeid: 2
quorum_votes: 1
ring0_addr: proxmox02
}
node {
name: proxmox04
nodeid: 4
quorum_votes: 1
ring0_addr: proxmox04
}
node {
name: proxmox01
nodeid: 1
quorum_votes: 1
ring0_addr: proxmox01
}
node {
name: proxmox03
nodeid: 3
quorum_votes: 1
ring0_addr: proxmox03
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: redacted01
config_version: 4
ip_version: ipv4
secauth: on
version: 2
interface {
bindnetaddr: 10.1.1.1
ringnumber: 0
}
}
root at proxmox03:~# pvecm status
Quorum information
------------------
Date: Wed May 3 09:40:49 2017
Quorum provider: corosync_votequorum
Nodes: 4
Node ID: 0x00000003
Ring ID: 1/2452
Quorate: Yes
Votequorum information
----------------------
Expected votes: 4
Highest expected: 4
Total votes: 4
Quorum: 3
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 10.1.1.1
0x00000002 1 10.1.1.2
0x00000003 1 10.1.1.3 (local)
0x00000004 1 10.1.1.4
root at proxmox03:~# ha-manager status
quorum OK
master proxmox03 (active, Wed May 3 09:44:26 2017)
lrm proxmox01 (active, Wed May 3 09:44:26 2017)
lrm proxmox02 (active, Wed May 3 09:44:22 2017)
lrm proxmox03 (active, Wed May 3 09:44:21 2017)
<services> <services>
More information about the pve-user
mailing list