Re: [Pacemaker] cannot create gfs2 filesystem : can't open device /dev/drbd1: Read-only file system

ok, the split brain condition has been resolved. On Wed, Oct 17, 2012 at 12:16 PM, Digimer li...@alteeve.ca wrote: On 10/17/2012 12:58 AM, Soni Maula Harriz wrote: and when i restart drbd service on node 2, i found this message : [root@cluster2 ~]# service drbd restart Stopping all DRBD

Re: [Pacemaker] cannot create gfs2 filesystem : can't open device /dev/drbd1: Read-only file system

i succesfully created gfs2 filesystem on cluster1, the failure only happen to cluster2 On Wed, Oct 17, 2012 at 2:00 PM, Soni Maula Harriz soni.har...@sangkuriang.co.id wrote: ok, the split brain condition has been resolved. On Wed, Oct 17, 2012 at 12:16 PM, Digimer li...@alteeve.ca wrote:

Re: [Pacemaker] Announce: pcs-0.9.26

Please see here: https://github.com/feist/pcs/issues Andreas -Ursprüngliche Nachricht- Von: Chris Feist [mailto:cfe...@redhat.com] Gesendet: Mittwoch, 17. Oktober 2012 02:03 An: The Pacemaker cluster resource manager Cc: linux clustering Betreff: Re: [Pacemaker] Announce: pcs-0.9.26

[Pacemaker] lvm ra timeouts and vgdisplay hang

I've been having a problem with the lvm ra when used in conjunction with clvm when a node dies (eg when I destroy the vm to test this particular scenario) clvm re-organises itself just fine, and comes good well within the lvm ra timeout I set (60 seconds), but if the vgdisplay -v vg-drbd

Re: [Pacemaker] resource can not be started

Le 17/10/2012 11:56, Mia Lueng a écrit : group rg_apache2 res_apache res_ip_apache \ meta target-role=Started order rg_apache_order : res_ip_apache res_apache It seems not correct. A group is already a shortcut for an ordered collocation. Either use collocation+ordering, or a group,

Re: [Pacemaker] cannot create gfs2 filesystem : can't open device /dev/drbd1: Read-only file system

Please paste your cluster.conf file and the output from 'cat /proc/drbd'. Also, did you configure and test stonith/fencing? digimer On 10/17/2012 03:42 AM, Soni Maula Harriz wrote: ok, it's done. i can now create gfs2 filesystem in cluster2, by following configuration here

Re: [Pacemaker] resource can not be started

On 2012-10-17T14:03:16, Florian Crouzat gen...@floriancrouzat.net wrote: Le 17/10/2012 11:56, Mia Lueng a écrit : group rg_apache2 res_apache res_ip_apache \ meta target-role=Started order rg_apache_order : res_ip_apache res_apache It seems not correct. A group is already a shortcut

Re: [Pacemaker] Unable to add ping resource to pacemaker 1.0.12

- Original Message - From: Richard \Alan\ McAlexander alanmac1...@gmail.com To: The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org Sent: Tuesday, October 16, 2012 7:23:37 PM Subject: Re: [Pacemaker] Unable to add ping resource to pacemaker 1.0.12 Hi Jake,

[Pacemaker] will online node shoots the standby node when no cluster services?

Hi, A simple question for a simple 2-nodes cluster running pacemaker-1.0.9, corosync-1.2.1 (Debian/Squeeze): will the online node stonith the other standby node if I stop the cluster services on it? (I need to open the chassis) thanks! jf ___

Re: [Pacemaker] will online node shoots the standby node when no cluster services?

On 10/17/2012 02:10 PM, Jean-Francois Malouin wrote: Hi, A simple question for a simple 2-nodes cluster running pacemaker-1.0.9, corosync-1.2.1 (Debian/Squeeze): will the online node stonith the other standby node if I stop the cluster services on it? (I need to open the chassis)

Re: [Pacemaker] will online node shoots the standby node when no cluster services?

* Digimer li...@alteeve.ca [20121017 14:21]: On 10/17/2012 02:10 PM, Jean-Francois Malouin wrote: Hi, A simple question for a simple 2-nodes cluster running pacemaker-1.0.9, corosync-1.2.1 (Debian/Squeeze): will the online node stonith the other standby node if I stop the cluster

Re: [Pacemaker] Unable to add ping resource to pacemaker 1.0.12

That's gotten me a little closer. I'm a bit of a newb when it comes to Pacemaker, on that note, I put the first group of your post (and changed the options to match the network I'm working on, I put this first configuration on the line with the existing group that I have setup. That group has

Re: [Pacemaker] Announce: pcs-0.9.26

Great. Of course I will test it. We are especially interested in the gui. Thanks Andreas -Ursprüngliche Nachricht- Von: Chris Feist [mailto:cfe...@redhat.com] Gesendet: Mittwoch, 17. Oktober 2012 21:22 An: The Pacemaker cluster resource manager Cc: Grüninger, Andreas (LGL Extern);

[Pacemaker] Storage Locking To Prevent Split Brain

We're changing our SAN shortly and I'm putting together the procedure / config now for the shared storage. This will be based on XFS on top of clustered LVM2 via Pacemaker. I've implemented the exclusive=yes directive on the LVM resources (volume groups) but I am still able to mount on both

Re: [Pacemaker] Unable to add ping resource to pacemaker 1.0.12

- Original Message - From: Richard \Alan\ McAlexander alanmac1...@gmail.com To: Jake Smith jsm...@argotec.com, The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org Sent: Wednesday, October 17, 2012 3:21:42 PM Subject: Re: [Pacemaker] Unable to add ping resource to

Re: [Pacemaker] [Patch] The log when I lost Quorum is never output.

What about this instead? diff --git a/crmd/heartbeat.c b/crmd/heartbeat.c index cae143b..3a7f31d 100644 --- a/crmd/heartbeat.c +++ b/crmd/heartbeat.c @@ -354,14 +354,13 @@ crmd_ccm_msg_callback(oc_ed_t event, void *cookie, size_t size, const void *data if (update_quorum) {

Re: [Pacemaker] will online node shoots the standby node when no cluster services?

On Wed, 17 Oct 2012 14:21:24 -0400 Digimer li...@alteeve.ca wrote: On 10/17/2012 02:10 PM, Jean-Francois Malouin wrote: Hi, A simple question for a simple 2-nodes cluster running pacemaker-1.0.9, corosync-1.2.1 (Debian/Squeeze): will the online node stonith the other standby node

Re: [Pacemaker] [Patch] The log when I lost Quorum is never output.

Hi Andrew, Thank you for comments. Even your correction is good, but one place of correction is necessary. #if SUPPORT_HEARTBEAT -static gboolean fsa_have_quorum = FALSE; gboolean ccm_dispatch(int fd, gpointer user_data) { @@ -575,14 +574,14 @@ if(update_quorum) {

Re: [Pacemaker] [Patch] The log when I lost Quorum is never output.

Good catch! On Thu, Oct 18, 2012 at 10:33 AM, renayama19661...@ybb.ne.jp wrote: Hi Andrew, Thank you for comments. Even your correction is good, but one place of correction is necessary. #if SUPPORT_HEARTBEAT -static gboolean fsa_have_quorum = FALSE; gboolean ccm_dispatch(int fd,

Re: [Pacemaker] will online node shoots the standby node when no cluster services?

On Thu, Oct 18, 2012 at 9:58 AM, Arnold Krille arn...@arnoldarts.de wrote: On Wed, 17 Oct 2012 14:21:24 -0400 Digimer li...@alteeve.ca wrote: On 10/17/2012 02:10 PM, Jean-Francois Malouin wrote: Hi, A simple question for a simple 2-nodes cluster running pacemaker-1.0.9, corosync-1.2.1

Re: [Pacemaker] resource can not be started

I just set one order rule: order rg_apache_order : res_ip_apache res_apache You mean the rule group rg_apache2 res_apache res_ip_apache \ meta target-role=Started also indicates an order rule ? 2012/10/17 Lars Marowsky-Bree l...@suse.com: On 2012-10-17T14:03:16, Florian Crouzat

Re: [Pacemaker] resource can not be started

(Sorry for the top post)Yes... Groups are a syntactical shortcut for order and collocation statements. Resources in a group are ordered in the sequence they are written and collocated in reverse. HTHJakeFrom: Mia Lueng Sent: Wed, 17/10/2012 09:17 PMTo: The Pacemaker cluster

Re: [Pacemaker] 'crm configure edit' failed with Timer expired

This is your resource: Current DC: NONE All the crm configure commands try to talk to the DC, and you don't have one. Normally one would be elected quite quickly, you may have a network/filewall issue. On Thu, Oct 18, 2012 at 10:37 AM, Lonni J Friedman netll...@gmail.com wrote: I'm running

Re: [Pacemaker] cannot create gfs2 filesystem : can't open device /dev/drbd1: Read-only file system

On Wed, Oct 17, 2012 at 7:56 PM, Digimer li...@alteeve.ca wrote: Please paste your cluster.conf file ?xml version=1.0? cluster config_version=1 name=cluster logging debug=off/ clusternodes clusternode name=cluster1 nodeid=1 fence method name=pcmk-redirect device