[ClusterLabs] crm_mon change in behaviour PM 1.1.12 -> 1.1.14: crm_mon -XA filters #health.* node attributes

Hello everybodyThis 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.Our cluster is using multiple resource agents that update various node attributes (via RAs like sysinfo, healthcpu, etc.) in the form of #health.*

[ClusterLabs] Issues with crm_mon or ClusterMon resource agent

Hi, I wanted to configure ClusterMon resource agent so that I can get information about events in the pacemaker cluster. *Objective is to generate traps for some specific resource agents and/or conditions* My cluster installation details : pacemakerd --version Pacemaker 1.1.11 Written by Andrew

Re: [ClusterLabs] Removing node from pacemaker.

Thanx for this tip , Andrei . I was complete unaware of this functionality of crm command line tool. - Debabrata From: Andrei Maruha mailto:andrei_mar...@epam.com>> Reply-To: Cluster Labs - All topics related to open-source clustering welcomed mailto:users@clusterlabs.org>> Date: Thursday, 3 Mar

Re: [ClusterLabs] Removing node from pacemaker.

Thanx Ken, Regards, Debabrata On 03/03/16 22:18, "Ken Gaillot" wrote: >On 03/03/2016 06:04 AM, Debabrata Pani wrote: >> >>http://clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s >>-n >> ode-delete.html >> >> >> >> Are we missing the deletion of the nodes from the cib ? > >

Re: [ClusterLabs] crm_mon change in behaviour PM 1.1.12 -> 1.1.14: crm_mon -XA filters #health.* node attributes

On 03/03/2016 10:07 AM, Martin Schlegel wrote: > Hello everybody > > > 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. > > > Our cluster is using multiple resource agents that update various node >

Re: [ClusterLabs] Removing node from pacemaker.

On 03/03/2016 06:04 AM, Debabrata Pani wrote: > http://clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-n > ode-delete.html > > > > Are we missing the deletion of the nodes from the cib ? That documentation is old; crm_node -R does remove the node from the CIB. > Regards, > D

[ClusterLabs] crm_mon change in behaviour PM 1.1.12 -> 1.1.14: crm_mon -XA filters #health.* node attributes

Hello everybodyThis 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.Our cluster is using multiple resource agents that update various node attributes (via RAs like sysinfo, healthcpu, etc.) in the form of #health.*

Re: [ClusterLabs] Removing node from pacemaker.

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 Instead of steps 1 and 2you can delete certain node from the corosync config manually and run: #corosync-cfgtool -R On 03/03/2016 02:44 PM, Som

Re: [ClusterLabs] Removing node from pacemaker.

http://clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-n ode-delete.html Are we missing the deletion of the nodes from the cib ? Regards, Debabrata From: Somanath Jeeva Reply-To: Cluster Labs - All topics related to open-source clustering welcomed Date: Thursday, 3 Ma

[ClusterLabs] Removing node from pacemaker.

Hi, I am trying to remove a node from the pacemaker'/corosync cluster, using the command "crm_node -R dl360x4061 -force". Though this command removes the node from the cluster, it is appearing as offline after pacemaker/corosync restart in the nodes that are online. Is there any other command t

Re: [ClusterLabs] service network restart and corosync

Hi, In our deployment, due to some requirement, we need to do a : service network restart What is exact reason for doing network restart? Due to this corosync crashes and the associated pacemaker processes crash as well. As per the last comment on this issue, --- Corosync reacts oddly