Re: [ClusterLabs] Clone Issue

I tried working with a few of these suggestions but the issue doesn't seem to be there. All of them were configured the same way for the status page. After rebooting all of the nodes, two of the ClusterIP resources wound up on the same node, and "relocate run ClusterIP-clone" would not

Re: [ClusterLabs] Triggered assert at xml.c:594

Replying to myself, This seems to be related to the latest drbd RA (8.9.4+). Still, is it something we should worry about ? Regards! -Original Message- From: Patrick Zwahlen [mailto:p...@navixia.com] Sent: samedi, 13 février 2016 15:47 To: Cluster Labs - All topics related to

[ClusterLabs] Pacemaker issue when ethernet interface is pulled down

Hi, We ran into some problems when we pull down the ethernet interface using “ifconfig eth0 down” Our cluster has the following configurations and resources * Two network interfaces : eth0 and lo(cal) * 3 nodes with one node put in maintenance mode * No-quorum-policy=stop *

Re: [ClusterLabs] Pacemaker issue when ethernet interface is pulled down

use fence and after you configured the fencing you need to use iptables for testing your cluster, with iptables you can block 5404 and 5405 ports 2016-02-14 14:09 GMT+01:00 Debabrata Pani : > Hi, > We ran into some problems when we pull down the ethernet interface

Re: [ClusterLabs] Clone Issue

On 02/13/2016 08:09 PM, Frank D. Engel, Jr. wrote: > Hi, > > I'm new to the software, and with the list - just started experimenting > with trying to get a cluster working using CentOS 7 and the pcs utility, > and I've made some progress, but I can't quite figure out why I'm seeing > this one