On 03/04/2016 04:51 AM, Martin Schlegel wrote:
> Hello all
>
> While our cluster seems to be working just fine I have noticed something in
> the
> crm_mon output that I don't quite understand and that is throwing off my
> monitoring a bit as stopped resources could mean something is wrong. I was
Hello all
While our cluster seems to be working just fine I have noticed something in the
crm_mon output that I don't quite understand and that is throwing off my
monitoring a bit as stopped resources could mean something is wrong. I was
hoping somebody could help me to understand what it means. I
I have tried it on my cluster, "crm node delete" just removes node from
the cib without updating of corosync.conf.
After restart of pacemaker service you will get something like this:
Online: [ node1 ]
OFFLINE: [ node2 ]
BTW, you will get the same state after "pacemaker restart", if you
remov
Hi,
On Thu, Mar 03, 2016 at 03:20:56PM +0300, Andrei Maruha wrote:
> Hi,
> Usually I use the following steps to delete node from the cluster:
> 1. #crm corosync del-node
> 2. #crm_node -R node --force
> 3. #crm corosync reload
I'd expect all this to be wrapped in "crm node delete". Isn't
that th
On 03/03/16 17:07 +0100, Martin Schlegel wrote:
> Hello everybody
Welcome Martin,
> This is my first post on this mailing list and I am only using Pacemaker since
> fall 2015 ... please be gentle :-) and I will do the same.
the list would really appreciate if you could make your email client
(be
