[ClusterLabs] Resources not monitored in SLES11 SP4 (1.1.12-f47ea56)

Hi! We just observed some strange effect we cannot explain in SLES 11 SP4 (pacemaker 1.1.12-f47ea56): We run about a dozen of Xen PVMs on a three-node cluster (plus some infrastructure and monitoring stuff). It worked all well so far, and there was no significant change recently. However when a

Re: [ClusterLabs] Upgrade corosync problem

Hi, Let me add here one important detail. I use Docker for my test with 5 containers deployed on my Mac. Basically the team that worked on this project installed the cluster on soft layer bare metal. The PostgreSQL cluster was hard to test and if a misconfiguration occurred recreate the cluster

Re: [ClusterLabs] pcs 0.9.165 released

On 25/06/18 12:08 +0200, Tomas Jelinek wrote: > I am happy to announce the latest release of pcs, version 0.9.165. What a mighty patch/micro version component ;-) With several pacemaker 2.0 release candidates out, it would be perhaps welcome to share details about versioning (branches) politics o

Re: [ClusterLabs] Upgrade corosync problem

On 25/06/18 19:06 +0200, Salvatore D'angelo wrote: > Thanks for reply. I scratched my cluster and created it again and > then migrated as before. This time I uninstalled pacemaker, > corosync, crmsh and resource agents with make uninstall > > then I installed new packages. The problem is the same,

Re: [ClusterLabs] Upgrade corosync problem

Hi,Thanks for reply. I scratched my cluster and created it again and then migrated as before. This time I uninstalled pacemaker, corosync, crmsh and resource agents withmake uninstallthen I installed new packages. The problem is the same, when I launch:corosync-quorumtool -psI got: Cannot initializ

Re: [ClusterLabs] VM failure during shutdown

On Mon, 2018-06-25 at 09:47 -0500, Ken Gaillot wrote: > On Mon, 2018-06-25 at 11:33 +0300, Vaggelis Papastavros wrote: > > Dear friends , > > > > We have the following configuration : > > > > CentOS7 , pacemaker 0.9.152 and Corosync 2.4.0, storage with DRBD > > and  > > stonith eanbled with APC P

Re: [ClusterLabs] VM failure during shutdown

On Mon, 2018-06-25 at 11:33 +0300, Vaggelis Papastavros wrote: > Dear friends , > > We have the following configuration : > > CentOS7 , pacemaker 0.9.152 and Corosync 2.4.0, storage with DRBD > and  > stonith eanbled with APC PDU devices. > > I have a windows VM configured as cluster resource wi

Re: [ClusterLabs] corosync doesn't start any resource

Hello Andrei, > Then you need to set symmetrical="false". yep, now it seems to work now, thank you very much! > I assume this would be "pcs constraint order set ... > symmetrical=false". yes almost: pcs constraint order set nfs-server vm_storage ha-ip action=start setoptions symmetrical=false

Re: [ClusterLabs] Questions about SBD behavior

On 06/25/2018 12:01 PM, 井上 和徳 wrote: >> -Original Message- >> From: Klaus Wenninger [mailto:kwenn...@redhat.com] >> Sent: Wednesday, June 13, 2018 6:40 PM >> To: Cluster Labs - All topics related to open-source clustering welcomed; 井上 >> 和 >> 徳 >> Subject: Re: [ClusterLabs] Questions about

[ClusterLabs] pcs 0.9.165 released

I am happy to announce the latest release of pcs, version 0.9.165. Source code is available at: https://github.com/ClusterLabs/pcs/archive/0.9.165.tar.gz or https://github.com/ClusterLabs/pcs/archive/0.9.165.zip Complete change log for this release: ## [0.9.165] - 2018-06-21 ### Added - Pcsd o

Re: [ClusterLabs] Questions about SBD behavior

> -Original Message- > From: Klaus Wenninger [mailto:kwenn...@redhat.com] > Sent: Wednesday, June 13, 2018 6:40 PM > To: Cluster Labs - All topics related to open-source clustering welcomed; 井上 和 > 徳 > Subject: Re: [ClusterLabs] Questions about SBD behavior > > On 06/13/2018 10:58 AM, 井上 和

[ClusterLabs] Fencing 2 Nodes

Hi, I have a 2 clustered nodes and it required to configure the fencing. i want to configure the fencing thru VM ESXI, what fencing agent do i need to use ? is it fence_virt, fence_xvm or fence_vmware_soap ? im so confused on this fencing. may you can also provide simple configuration of the best

[ClusterLabs] VM failure during shutdown

Dear friends , We have the following configuration : CentOS7 , pacemaker 0.9.152 and Corosync 2.4.0, storage with DRBD and stonith eanbled with APC PDU devices. I have a windows VM configured as cluster resource with the following attributes : Resource: WindowSentinelOne_res (class=ocf pro

Re: [ClusterLabs] Upgrade corosync problem

On 22/06/18 11:23, Salvatore D'angelo wrote: > Hi, > Here the log: > > > [17323] pg1 corosyncerror [QB] couldn't create circular mmap on /dev/shm/qb-cfg-event-17324-17334-23-data [17323] pg1 corosyncerror [QB] qb_rb_open:cfg-event-17324-17334-23: Resource temporarily unavailable (11)