Re: [Pacemaker] Basic Clone IP configuration not starting automatically

Am Donnerstag, 5. Februar 2015, 14:33:52 schrieb Net Warrior: > Hi there guys. (...) > If I do an sshd to the VIP I can see the round robin is woking and it > switches bettween hosts and I can see of course the alias created on the > eth0 iface. > > My problem is that when I reboot a server to tes

Re: [Pacemaker] Two node cluster and no hardware device for stonith.

On 2015-02-05 17:08, Andrea wrote: Hi I test location constraint with ping resource to stop resource on disconnected node, but with stonith active, doesn't works I used dummy resource for test [ONE]pcs resource create mydummy ocf:pacemaker:Dummy op monitor interval=120s --clone Ping resource

[Pacemaker] Basic Clone IP configuration not starting automatically

Hi there guys. I'm new to pacemaker and I'm trying to accomplish an active/active cluster with a VIP ip address, I used the java frontend for the initial setup, I'm using LCMC-1.7.6.jar. This is what I've got: CentOS release 6.5 pacemaker-libs-1.1.10-14.el6_5.3.x86_64 pacemaker-cli-1.1.10-14.el6_

Re: [Pacemaker] Call cib_apply_diff failed (-205): Update was older than existing configuration

Here is a part of my /var/log/cluster/corosync.log: Feb 05 16:23:36 [3184] isis-seth943fcib: info: cib_process_ping:Reporting our current digest to node-1: 71d36e21c5df77a4e8b10b29f2a349e2 for 0.70.16 (0x2474c50 0) Feb 05 16:23:41 [3185] isis-seth943f stonithd: notice: remote

[Pacemaker] Call cib_apply_diff failed (-205): Update was older than existing configuration

Hi guys, I saw this during applying the configuration using a script with crmsh commands: + crm configure primitive STONITH_node-1 stonith:fence_avid_sbb_hw + crm configure primitive STONITH_node-0 stonith:fence_avid_sbb_hw params delay=10 + crm configure location dont_run_STONITH_node-1_on_node-

Re: [Pacemaker] Two node cluster and no hardware device for stonith.

> > On Wednesday, February 4, 2015, Andrea > > wrote: > > > > Digimer ...> writes: > > > > > > > > That fence failed until the network came back makes your fence method > > > less than ideal. Will it eventually fence with the network still > > failed? >

Re: [Pacemaker] authentication in the cluster

Chrissie, thank you! =) It helps! Thank you, Kostya On Thu, Feb 5, 2015 at 3:59 PM, Christine Caulfield wrote: > On 02/05/2015 01:47 PM, Kostiantyn Ponomarenko wrote: > > Chrissie, one more thing. > > > > And I also suppose that the key is read only one time at the start-up of > > the Corosync.

Re: [Pacemaker] authentication in the cluster

On 02/05/2015 01:47 PM, Kostiantyn Ponomarenko wrote: > Chrissie, one more thing. > > And I also suppose that the key is read only one time at the start-up of > the Corosync. > In other words there is no any check for the presence of the key or its > update, while Corosync is working. > Am I right

Re: [Pacemaker] authentication in the cluster

Chrissie, one more thing. And I also suppose that the key is read only one time at the start-up of the Corosync. In other words there is no any check for the presence of the key or its update, while Corosync is working. Am I right? Thank you, Kostya On Thu, Feb 5, 2015 at 2:42 PM, Kostiantyn Pon

Re: [Pacemaker] authentication in the cluster

Hi Chrissie, On Thu, Jan 29, 2015 at 11:44 AM, Christine Caulfield wrote: > as corosync rejects the messages > with the wrong authkey > And I suppose that it is enough just to use "crypto_hash" option. I am right? Thank you, Kostya ___ Pacemaker mail

Re: [Pacemaker] Two node cluster and no hardware device for stonith.

That is the problem that makes geo-clustering very hard to nearly impossible. You can look at the Booth option for pacemaker, but that requires two (or more) full clusters, plus an arbitrator 3rd location. Outside of this though, there really is no way to have geo/stretch clustering with automa