On Tue, 2017-05-16 at 10:31 +0200, Thomas Lamprecht wrote:
> Honestly, I would just stop the HA services (this marks the VMs
> currently under
> HA) and then do a clean restart of the pve-cluster corosync services,
> I'd do this for all nodes but not all at the same time :) This is as
> safe as
Hi,
On 05/09/2017 08:48 AM, Mark Schouten wrote:
> On Fri, 2017-05-05 at 18:14 +0200, Thomas Lamprecht wrote:
>> Hi,
>>
>> It looks like the PVE cluster filesystem is out of sync or has a
>> problematic connection to corosync.
>> From corosyncs stand point the node addition worked, and is
>>
Hi,
It looks like the PVE cluster filesystem is out of sync or has a
problematic connection to corosync.
From corosyncs stand point the node addition worked, and is consistent
on all nodes, which is good.
Now, some log from `proxmox03`- the problematic node - would be nice:
# journalctl -u
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
> >
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
Hi,
I recently added a new node to a cluster which is also running with HA. The
fourth node seems to be working fine, but one of the other nodes is confused.
pvecm nodes shows the full hostname for the new node, and the short one for the
existing nodes. So probably a result of a imperfect
