Thomas, pretty please? :)
On Wed, 2017-05-03 at 09:45 +0200, Mark Schouten wrote: > 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. > > > _______________________________________________ > pve-user mailing list > pve-user@pve.proxmox.com > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user -- Kerio Operator in de Cloud? https://www.kerioindecloud.nl/ Mark Schouten | Tuxis Internet Engineering KvK: 61527076 | http://www.tuxis.nl/ T: 0318 200208 | i...@tuxis.nl _______________________________________________ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user