Re: [Pacemaker] Daemon Start attempt on wrong Server

2014-11-11 Thread Alexandre
Hi Hauke, I can't find any reference in the crm manual to your command. I don't either understand what is an unclean location. A cli-* location? Can you clarify? Again your setup seems to be opt-in based (sorry I miss used the term in previous post). Documentation states: *6.2. Deciding Which Node

Re: [Pacemaker] Daemon Start attempt on wrong Server

2014-11-11 Thread Hauke Homburg
Am 11.11.2014 16:25, schrieb Andrei Borzenkov: В Tue, 11 Nov 2014 16:19:56 +0100 Hauke Homburg пишет: Am 11.11.2014 13:34, schrieb Alexandre: You should use an opt out cluster. Set the cluster option symmetrical=false. This will tell corosync not to place a resource anywhere on the cluster, u

Re: [Pacemaker] Loosing corosync communication clusterwide

2014-11-11 Thread Andrew Beekhof
> On 11 Nov 2014, at 10:12 pm, Daniel Dehennin > wrote: > > Andrew Beekhof writes: > > > [...] > >>> I have fencing configured and working, modulo fencing VMs on dead host[1]. >> >> Are you saying that the host and the VMs running inside it are both part of >> the same cluster? > > Yes,

Re: [Pacemaker] DRBD with Pacemaker on CentOs 6.5

2014-11-11 Thread Vladislav Bogdanov
11.11.2014 07:27, Sihan Goi wrote: > Hi, > > DocumentRoot is still set to /var/www/html > ls -al /var/www/html shows different things on the 2 nodes > node01: > > total 28 > drwxr-xr-x. 3 root root 4096 Nov 11 12:25 . > drwxr-xr-x. 6 root root 4096 Jul 23 22:18 .. > -rw-r--r--. 1 root root5

[Pacemaker] Split Brain on DRBD Dual Primary

2014-11-11 Thread Ho, Alamsyah - ACE Life Indonesia
Hi All, On October archives, I saw the issue reported by Felix Zachlod on http://oss.clusterlabs.org/pipermail/pacemaker/2014-October/022653.html and the same is actually happens to me now on dual primary DRBD node. My current OS was RHEL 6.6 and software version that I used was pacemaker-1.1.1

Re: [Pacemaker] DRBD with Pacemaker on CentOs 6.5

2014-11-11 Thread Sihan Goi
Hi, I'm fluent in English so I doubt it's a language barrier. I have reasonable user experience in Linux, though not extensive experience in the various system commands, and I have zero experience in HA. I'm in fact trying to make things as simple as possible by simply following the "Clusters from

Re: [Pacemaker] Daemon Start attempt on wrong Server

2014-11-11 Thread Alexandre
I guess the short answer is, "because that's the way it works". I am just guessing here but scoring infinity on a location doesn't mean it's impossible to start the resource elsewhere. If the nodes involved in the locations defined are unavailable, the cluster will still try to place it somewhere.

Re: [Pacemaker] Daemon Start attempt on wrong Server

2014-11-11 Thread Hauke Homburg
Am 11.11.2014 16:25, schrieb Andrei Borzenkov: В Tue, 11 Nov 2014 16:19:56 +0100 Hauke Homburg пишет: Am 11.11.2014 13:34, schrieb Alexandre: You should use an opt out cluster. Set the cluster option symmetrical=false. This will tell corosync not to place a resource anywhere on the cluster, u

Re: [Pacemaker] Daemon Start attempt on wrong Server

2014-11-11 Thread Andrei Borzenkov
В Tue, 11 Nov 2014 16:19:56 +0100 Hauke Homburg пишет: > Am 11.11.2014 13:34, schrieb Alexandre: > > > > You should use an opt out cluster. Set the cluster option > > symmetrical=false. This will tell corosync not to place a resource > > anywhere on the cluster, unless a location rule explicit

Re: [Pacemaker] Daemon Start attempt on wrong Server

2014-11-11 Thread Hauke Homburg
Am 11.11.2014 13:34, schrieb Alexandre: You should use an opt out cluster. Set the cluster option symmetrical=false. This will tell corosync not to place a resource anywhere on the cluster, unless a location rule explicitly tell the cluster where it should run. Corosync will still monitor

Re: [Pacemaker] Daemon Start attempt on wrong Server

2014-11-11 Thread Alexandre
You should use an opt out cluster. Set the cluster option symmetrical=false. This will tell corosync not to place a resource anywhere on the cluster, unless a location rule explicitly tell the cluster where it should run. Corosync will still monitor sql resources on www hosts and return rc 5 but t

[Pacemaker] Daemon Start attempt on wrong Server

2014-11-11 Thread Hauke Homburg
Hello, I am installing a 6 Node pacemaker CLuster. 3 Nodes for Apache, 3 Nodes for Postgres. My Cluster Config is node kvm-node1 node sql-node1 node sql-node2 node sql-node3 node www-node1 node www-node2 node www-node3 primitive pri_kvm_ip ocf:heartbeat:IPaddr2 \ params ip="10.0.6.41"

Re: [Pacemaker] Loosing corosync communication clusterwide

2014-11-11 Thread Daniel Dehennin
Andrew Beekhof writes: [...] >> I have fencing configured and working, modulo fencing VMs on dead host[1]. > > Are you saying that the host and the VMs running inside it are both part of > the same cluster? Yes, one of the VM needs to access the GFS2 filesystem like the nodes, the other VM is

Re: [Pacemaker] DRBD with Pacemaker on CentOs 6.5

2014-11-11 Thread Lars Ellenberg
On Tue, Nov 11, 2014 at 12:27:23PM +0800, Sihan Goi wrote: > Hi, > > DocumentRoot is still set to /var/www/html > ls -al /var/www/html shows different things on the 2 nodes > node01: > > total 28 > drwxr-xr-x. 3 root root 4096 Nov 11 12:25 . > drwxr-xr-x. 6 root root 4096 Jul 23 22:18 .. > -rw-

Re: [Pacemaker] [ha-wg] [ha-wg-technical] [Linux-HA] [RFC] Organizing HA Summit 2015

2014-11-11 Thread Fabio M. Di Nitto
On 11/5/2014 4:16 PM, Lars Ellenberg wrote: > On Sat, Nov 01, 2014 at 01:19:35AM -0400, Digimer wrote: >> All the cool kids will be there. >> >> You want to be a cool kid, right? > > Well, no. ;-) > > But I'll still be there, > and a few other Linbit'ers as well. > > Fabio, let us know what we