Re: [ClusterLabs] DLM not working on my GFS2/pacemaker cluster

please share your cluster config and say if your fencing is working. 2016-01-19 3:47 GMT+01:00 : > One of my clusters is having a problem. It's no longer able to set up its > GFS2 mounts. I've narrowed the problem down a bit. Here's the output when I > try to start the DLM

Re: [ClusterLabs] DLM not working on my GFS2/pacemaker cluster

On 18/01/16 21:47 -0500, dan...@benoy.name wrote: > Here's the exact same command run twice. First, on a very similarly > configured cluster (which is currently running): > # cat /sys/kernel/config/dlm/cluster/comms/169446438/addrcat > cat: /sys/kernel/config/dlm/cluster/comms/169446438/addr:

Re: [ClusterLabs] Pacemaker shows false status of a resource and doesn't react on OCF_NOT_RUNNING rc.

On 01/19/2016 10:30 AM, Kostiantyn Ponomarenko wrote: > The resource that wasn't running, but was reported as running, is > "adminServer". > > Here are a brief chronological description: > > [Jan 19 23:42:16] The first time Pacemaker triggers its monitor function at > line #1107. (those lines

Re: [ClusterLabs] DLM not working on my GFS2/pacemaker cluster

I've figured out the problem. Thank you everyone for the help. It was the McAfee anti-virus that was recently installed that caused the issue. On 2016-01-19 10:20, dan...@benoy.name wrote: http://pastebin.com/qaeEAFWz On 2016-01-19 09:49, emmanuel segura wrote: dlm_tool dump ? 2016-01-19

Re: [ClusterLabs] Pacemaker shows false status of a resource and doesn't react on OCF_NOT_RUNNING rc.

On 01/19/2016 11:02 AM, Kostiantyn Ponomarenko wrote: > Just in case, this is the monitor function from the resource agent: > ra_monitor() { > # ocf_log info "$RA: [monitor]" > systemctl status ${service} > rc=$? > if [ "$rc" -eq "0" ]; then > return $OCF_SUCCESS > fi >

Re: [ClusterLabs] Pacemaker shows false status of a resource and doesn't react on OCF_NOT_RUNNING rc.

On 01/19/2016 12:20 PM, Kostiantyn Ponomarenko wrote: > I've put the wrong entry from "journalctl --since="2016-01-19" > --until="2016-01-20"". > The correct one is: > > Jan 19 23:42:24 A2-2U12-302-LS ntpd[2204]: 0.0.0.0 c61c 0c clock_step > -43194.111405 s > Jan 19 11:42:29 A2-2U12-302-LS

Re: [ClusterLabs] Wait until resource is really ready before moving clusterip

On 14/01/16 14:46 +0100, Kristoffer Grönlund wrote: > Joakim Hansson writes: >> When adding the Delay RA it starts throwing a bunch of errors and the >> cluster starts fencing the nodes one by one. >> >> The error's I get with "pcs status": >> >> Failed Actions: >> *

[ClusterLabs] Pacemaker shows false status of a resource and doesn't react on OCF_NOT_RUNNING rc.

One of resources in my cluster is not actually running, but "crm_mon" shows it with the "Started" status. Its resource agent's monitor function returns "$OCF_NOT_RUNNING", but Pacemaker doesn't react on this anyhow - crm_mon show the resource as Started. I couldn't find an explanation to this

Re: [ClusterLabs] Pacemaker shows false status of a resource and doesn't react on OCF_NOT_RUNNING rc.

On 19.01.2016 13:49, Kostiantyn Ponomarenko wrote: > One of resources in my cluster is not actually running, but "crm_mon" > shows it with the "Started" status. > Its resource agent's monitor function returns "$OCF_NOT_RUNNING", but > Pacemaker doesn't react on this anyhow - crm_mon show the

Re: [ClusterLabs] Pacemaker shows false status of a resource and doesn't react on OCF_NOT_RUNNING rc.

On 19.01.2016 16:13, Ken Gaillot wrote: > On 01/19/2016 06:49 AM, Kostiantyn Ponomarenko wrote: >> One of resources in my cluster is not actually running, but "crm_mon" shows >> it with the "Started" status. >> Its resource agent's monitor function returns "$OCF_NOT_RUNNING", but >> Pacemaker

Re: [ClusterLabs] GFS2 with Pacemaker, Corosync on Ubuntu 14.04

19.01.2016 18:14, Momcilo Medic wrote: Dear all, I am trying to setup GFS2 on two Ubuntu 14.04 servers. Every guide I can find online is for 12.04 by using cman package which was abandoned in 13.10 So, I tried using Pacemaker with Corosync as instructed on your guide [1]. In this guide pcs is

Re: [ClusterLabs] DLM not working on my GFS2/pacemaker cluster

http://pastebin.com/qaeEAFWz On 2016-01-19 09:49, emmanuel segura wrote: dlm_tool dump ? 2016-01-19 15:25 GMT+01:00 : Yes, fencing is working, and SELinux is disabled. What configuration details do you require? Here's my corosync.conf: http://pastebin.com/SD1Gbdj0 Here's

Re: [ClusterLabs] DLM not working on my GFS2/pacemaker cluster

dlm_tool dump ? 2016-01-19 15:25 GMT+01:00 : > Yes, fencing is working, and SELinux is disabled. > > What configuration details do you require? > > Here's my corosync.conf: http://pastebin.com/SD1Gbdj0 > Here's my output from 'crm configure show': http://pastebin.com/eAiq2yJ9

[ClusterLabs] GFS2 with Pacemaker, Corosync on Ubuntu 14.04

Dear all, I am trying to setup GFS2 on two Ubuntu 14.04 servers. Every guide I can find online is for 12.04 by using cman package which was abandoned in 13.10 So, I tried using Pacemaker with Corosync as instructed on your guide [1]. In this guide pcs is used which is not available in Ubuntu so

Re: [ClusterLabs] Pacemaker shows false status of a resource and doesn't react on OCF_NOT_RUNNING rc.

Just in case, this is the monitor function from the resource agent: ra_monitor() { # ocf_log info "$RA: [monitor]" systemctl status ${service} rc=$? if [ "$rc" -eq "0" ]; then return $OCF_SUCCESS fi ocf_log warn "$RA: [monitor] : got rc=$rc" return

Re: [ClusterLabs] Pacemaker license

On 12/01/16 11:27 +1100, Andrew Beekhof wrote: >> On 6 Oct 2015, at 9:39 AM, santosh_bidara...@dell.com wrote: >> As per the given link http://clusterlabs.org/wiki/License, it is >> mentioned that “Pacemaker programs are licensed under the GPLv2+ >> (version 2 or later of the GPL) and its headers