You've disabled stonith, which alone is a very bad idea with DRBD and cman. Please enable it, configure and test stonith devices, and then hook DRBD into pacemaker using the 'fence-handler '/path/to/crm-fence-peer.sh' and set 'fencing resource-and-stonith'. Then configure cman to hook into pacemaker's fencing using the fence_pcmk fence handler in cluster.conf.

On 04/01/15 03:01 PM, raby wrote:
Hi this is the drbdadm dump

/# resource pcmAppData on pcmk-1: not ignored, not stacked
# defined at /etc/drbd.conf:10
resource pcmAppData {
     on pcmk-1 {
         device           /dev/drbd1 minor 1;
         disk             /dev/mapper/VolGroup-drbd--demo;
         meta-disk        internal;
         address          ipv4 192.168.203.128:7789
<http://192.168.203.128:7789>;
     }
     on pcmk-2 {
         device           /dev/drbd1 minor 1;
         disk             /dev/mapper/VolGroup-drbd--demo;
         meta-disk        internal;
         address          ipv4 192.168.203.130:7789
<http://192.168.203.130:7789>;
     }
     net {
         verify-alg       sha1;
         allow-two-primaries yes;
     }
}/

and this is the pacemaker configuration

/node pcmk-1 \
     attributes standby="off"
node pcmk-2 \
     attributes standby="off"
primitive ClusterIP ocf:heartbeat:IPaddr2 \
     params ip="192.168.203.150" cidr_netmask="32" \
     op monitor interval="30s"
primitive PcmData ocf:linbit:drbd \
     params drbd_resource="pcmAppData" \
     op monitor interval="60s"
primitive PcmFS ocf:heartbeat:Filesystem \
     params device="/dev/drbd/by-res/pcmAppData"
directory="/home/hassan/logs" fstype="gfs2"
primitive PcmtestApp ocf:raby:RabyAgent \
     op monitor interval="100ms" \
     meta target-role="Started" migration-threshold="1" failure-timeout="1"
ms PcmDataClone PcmData \
     meta master-max="2" master-node-max="1" clone-max="2"
clone-node-max="1" notify="true" target-role="Started"
clone ClusterIPClone ClusterIP \
     meta golbally-unique="true" clone-max="2" clone-node-max="2"
clone PcmFSClone PcmFS
clone PcmtestAppClone PcmtestApp
colocation PcmtestApp-with-PcmFS inf: PcmtestAppClone PcmFSClone
colocation PcmtestApp-with-ip inf: PcmtestAppClone ClusterIPClone
colocation fs_on_drbd inf: PcmFSClone PcmDataClone:Master
order PcmFS-after-PcmData inf: PcmDataClone:promote PcmFSClone:start
order PcmtestApp-after-PcmFS inf: PcmFSClone PcmtestAppClone
property $id="cib-bootstrap-options" \
     dc-version="1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c" \
     cluster-infrastructure="cman" \
     expected-quorum-votes="2" \
     stonith-enabled="false" \
     no-quorum-policy="ignore" \
     last-lrm-refresh="1417122793"/


As for the update, i unfortunately cannot to upgrade to Ubuntu-14 +
pacemaker 1.1


2015-01-02 14:48 GMT-08:00 Digimer <li...@alteeve.ca
<mailto:li...@alteeve.ca>>:

    Pacemaker 1.1.6 is very, very old. If you can upgrade to Ubuntu
    14.04 LTS you will get 1.1.10 (or newer). A *lot* changed in the
    meantime, plus a lot of bug fixes.

    Can you upgrade?

    If you still have trouble, please reply with your pacemaker
    configuration as well, and the 'drbdadm dump' output wouldn't hurt.

    On 02/01/15 05:39 PM, raby wrote:

        Hi i am following the cluster from scratch guide to set up an active
        active drbd configuration. here is my configuration
        Ubuntu 12 kernel 3.11.0-19-generic
        pacemaker 1.1.6
        corosync 1.4.2
        cman 3.1.7
        gfs2 3.1.3

        I am trying to do
        *mount /dev/drbd1*
        and i get this message
        /gfs_controld join connect error: Connection refused
        error mounting lockproto lock_dlm/

        here is the corosync configuration:
        /# Please read the corosync.conf.5 manual page

        compatibility: whitetank

        totem {
              version: 2
              secauth: off
              threads: 0
              interface {

                          member {
                                  memberaddr: 192.168.203.128
                          }
                          member {
                                  memberaddr: 192.168.203.130
                          }


                  ringnumber: 0
        bindnetaddr: 192.168.203.0
        mcastaddr: 239.255.1.1
        mcastport: 4000
                  ttl: 1
              }
        }

        logging {
              fileline: off
              to_stderr: no
              to_logfile: yes
              to_syslog: yes
              logfile: /var/log/cluster/corosync.log
              debug: off
              timestamp: on
              logger_subsys {
                  subsys: AMF
                  debug: off
              }
        }

        amf {
              mode: disabled
        }


        service {

           # Load the Pacemaker Cluster Resource Manager
           ver: 1
           name: pacemaker
           }
           aisexec {
           user: root
           group: root
           }/

        The cluster.conf configuration
        /<?xml version="1.0"?>
        <cluster config_version="1" name="PcmkCluster">
              <logging debug="off"/>
              <clusternodes>
                  <clusternode name="pcmk-1" nodeid="1">
                      <fence>
                          <method name="pcmk-redirect">
                              <device name="pcmk" port="pcmk-1"/>
                          </method>
                      </fence>
                  </clusternode>
                  <clusternode name="pcmk-2" nodeid="2">
                      <fence>
                          <method name="pcmk-redirect">
                              <device name="pcmk" port="pcmk-2"/>
                          </method>
                      </fence>
                  </clusternode>
              </clusternodes>
              <fencedevices>
                  <fencedevice name="pcmk" agent="fence_pcmk"/>
              </fencedevices>
        </cluster>/

        On the previous threads i have seen that you have to check how
        dlm is
        managed but i have no idea how to check that, ant help ? thanks.


        _________________________________________________
        Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
        <mailto:Pacemaker@oss.clusterlabs.org>
        http://oss.clusterlabs.org/__mailman/listinfo/pacemaker
        <http://oss.clusterlabs.org/mailman/listinfo/pacemaker>

        Project Home: http://www.clusterlabs.org
        Getting started:
        http://www.clusterlabs.org/__doc/Cluster_from_Scratch.pdf
        <http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf>
        Bugs: http://bugs.clusterlabs.org



    --
    Digimer
    Papers and Projects: https://alteeve.ca/w/
    What if the cure for cancer is trapped in the mind of a person
    without access to education?

    _________________________________________________
    Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
    <mailto:Pacemaker@oss.clusterlabs.org>
    http://oss.clusterlabs.org/__mailman/listinfo/pacemaker
    <http://oss.clusterlabs.org/mailman/listinfo/pacemaker>

    Project Home: http://www.clusterlabs.org
    Getting started:
    http://www.clusterlabs.org/__doc/Cluster_from_Scratch.pdf
    <http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf>
    Bugs: http://bugs.clusterlabs.org




_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org



--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without access to education?

_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to