Re: [ClusterLabs] Antw: CentOS 7 - Pacemaker - Problem with nfs-server and system

Hi, thank you for your reply. It seems to be a problem with the systemd unit files for nfs-server - specifically a timing issue. [root@centos7-n1 ~]# systemctl list-unit-files --type=service | grep rpcbind rpcbind.service static rpcbind is set to static - shou

[ClusterLabs] pacemaker and drbd - different versions - different scores for drbd master/slave resource?

Dear Users, Stack: corosync Current DC: centos7-n1 (1) - partition with quorum Version: 1.1.12-a14efad shows Node Attributes: * Node centos7-n1:     + #cluster-name : storage-cluster     + #site-name    : storage-cluster     + master-p_drbd_sd  

Re: [ClusterLabs] pacemaker and drbd - different versions - different scores for drbd master/slave resource?

Please ignore my question - just noticed that there was a split-brain so the score dropped for the Primary node. Stefan -Ursprüngliche Nachricht- Von: Stefan Bauer  Gesendet: Mit 12 August 2015 11:13 An: Cluster Labs - All topics related to open-source clustering welcomed Betreff: [

[ClusterLabs] [Announce] clufter-0.50.2 released

I am happy to announce that clufter-0.50.2, a tool/library for transforming/analyzing cluster configuration formats, has been released and published (incl. signature using my 60BCBB4F5CD7F9EF key):

Re: [ClusterLabs] cib state is now lost

Thanks Ken, We're currently using Pacemaker 1.1.11 and at the moment its not an option to upgrade. I've spun up and down these boxes on AWS and even tried different sizes. I think a recent upgrade broke this deploy. This is the output from dmesg: cib[16656] general protection ip:7f45391e9545 sp:

[ClusterLabs] Delayed first monitoring

Hi, I have set up and CoroSync+CMAN+Pacemaker at CentOS 6.5 in order to provide high-availability of opennebula. However, I am facing to a strange problem which raises from my lack of knowleadge.. In the log I can see that when I create a resource based on an init script, typically: pcs re

Re: [ClusterLabs] Delayed first monitoring

1. Pacemaker will/may call a monitor before starting a resource, in which case it expects a NOT_RUNNING response. It's just checking assumptions at that point. 2. A resource::start must only return when resource::monitor is successful. Basically the logic of a start() must follow this: start()

Re: [ClusterLabs] Delayed first monitoring

Thank you for your answer, but. 1) This sounds ok, but in other words it means the first delayed check is not possible to be done. 2) Start of init script? I follow lsb scripts from distribution, so there is not way to change them (I can change them, but with packages upgade they will go voi

Re: [ClusterLabs] starting of resources

On 11/08/15 09:14 -0500, Ken Gaillot wrote: > On 08/11/2015 02:12 AM, Vijay Partha wrote: >> After you start pacemaker and then type pcs status, we get the output that >> there are nodes online and the list of resources are empty. We then add >> resources to the nodes. Now what i want is after star

Re: [ClusterLabs] Delayed first monitoring

Sorry, but from my point of view, the agent first check if the resource is running, for example you can check that from /usr/lib/ocf/resource.d/heartbeat/Filesystem The logic is Filesystem::start(parameter as parameter for the agent)->Filesystem_start(function called from start in the case which

Re: [ClusterLabs] Delayed first monitoring

I would rather agree with you. However, I dont have logs at hand to prove it... but that is what I saw in logs thus I formulated my question as I did :D Dne 12.8.2015 v 18:16 emmanuel segura napsal(a): Sorry, but from my point of view, the agent first check if the resource is running, for exam

Re: [ClusterLabs] Delayed first monitoring

On 08/12/2015 10:45 AM, Miloš Kozák wrote: > Thank you for your answer, but. > > 1) This sounds ok, but in other words it means the first delayed check > is not possible to be done. > > 2) Start of init script? I follow lsb scripts from distribution, so > there is not way to change them (I can ch

Re: [ClusterLabs] Antw: CentOS 7 - Pacemaker - Problem with nfs-server and system

On 08/12/2015 10:35 AM, Stefan Bauer wrote: > Hi, > > > > thank you for your reply. It seems to be a problem with the systemd unit > files for nfs-server - specifically a timing issue. > > > > [root@centos7-n1 ~]# systemctl list-unit-files --type=service | grep rpcbind > rpcbind.service

[ClusterLabs] Ordering constraint restart second resource group

​Hello, in my cluster configuration I have following situation: resource_group_A ip1 ip2 resource_group_B apache1 ordering constraint resource_group_A then resource_group_B symetrical=true When I add a new resource from group_A, resources from group_B are restarted. If I remove constrai

Re: [ClusterLabs] Antw: CentOS 7 - Pacemaker - Problem with nfs-server and system

Thanks Dennis for pointing that out. Will give it a try tomorrow. Cheers, Stefan -Ursprüngliche Nachricht- Von: Dennis Jacobfeuerborn  Gesendet: Mit 12 August 2015 18:24 An: users@clusterlabs.org Betreff: Re: [ClusterLabs] Antw: CentOS 7 - Pacemaker - Problem with nfs-server and

[ClusterLabs] circumstances under which resources become unmanaged

Hi All, I have a resource added to pacemaker called 'cmsd' whose state is getting to 'unmanaged FAILED' state. Apart from manually changing the resource to unmanaged using "pcs resource unmanage cmsd" , I'm trying to understand under what all circumstances a resource can become unmanaged.. ? I

Re: [ClusterLabs] cib state is now lost

On 08/12/2015 05:29 AM, David Neudorfer wrote: > Thanks Ken, > > We're currently using Pacemaker 1.1.11 and at the moment its not an option > to upgrade. > I've spun up and down these boxes on AWS and even tried different sizes. I > think a recent upgrade broke this deploy. What OS distribution/v

[ClusterLabs] [Question:pacemaker_remote] About limitation of the placement of the resource to remote node.

Hi All, We confirmed movement of pacemaker_remote.(version:pacemaker-ad1f397a8228a63949f86c96597da5cecc3ed977) It is the following cluster constitution.  * sl7-01(KVM host)  * snmp1(Guest on the sl7-01 host)  * snmp2(Guest on the sl7-01 host) We prepared for the next CLI file to confirm the res

Re: [ClusterLabs] circumstances under which resources become unmanaged

On 12.08.2015 20:46, N, Ravikiran wrote: Hi All, I have a resource added to pacemaker called 'cmsd' whose state is getting to 'unmanaged FAILED' state. Apart from manually changing the resource to unmanaged using "pcs resource unmanage cmsd" , I'm trying to understand under what all circums

Re: [ClusterLabs] Ordering constraint restart second resource group

On 12.08.2015 19:35, John Gogu wrote: ​Hello, in my cluster configuration I have following situation: resource_group_A ip1 ip2 resource_group_B apache1 ordering constraint resource_group_A then resource_group_B symetrical=true When I add a new resource from group_A, resources fro

Re: [ClusterLabs] circumstances under which resources become unmanaged

Thanks for reply Andrei. What happens to the resources added with a COLOCATION or an ORDER constraint with this resource (unmanaged FAILED resource).. ? will the constraint be removed.. ? Also please point me to any resource to understand this in detail. Regards Ravikiran -Original Message

[ClusterLabs] Antw: Delayed first monitoring

I think the start script has to be fixed to return success when httpd is actually running. >>> Miloš Kozák schrieb am 12.08.2015 um 16:03 in Nachricht <55cb521a.8090...@lejmr.com>: > Hi, > > I have set up and CoroSync+CMAN+Pacemaker at CentOS 6.5 in order to > provide high-availability of openn