[Pacemaker] Pacemaker cant promote Master/Slave resource

Bryan Bueter bryan at bueterfamily.org
Thu Jul 3 15:05:37 UTC 2014


I have a two node active/standby cluster that I'm building and I cant get
pacemaker to promote my DRBD resource.  I'm thinking I have something
wrong in the configuration but I dont see it.

The errors I get on NODE1 are:
/var/log/corosync.log:
drbd(nfshome-drbd)[24632]:	2014/07/03_10:09:23 ERROR: nfshome: Called
drbdadm -c /etc/drbd.conf primary nfshome
drbd(nfshome-drbd)[24632]:	2014/07/03_10:09:23 ERROR: nfshome: Exit code 17
drbd(nfshome-drbd)[24632]:	2014/07/03_10:09:23 ERROR: nfshome: Command
output:
drbd(nfshome-drbd)[24632]:	2014/07/03_10:09:23 CRIT: Refusing to be
promoted to Primary without UpToDate data
drbd(nfshome-drbd)[24632]:	2014/07/03_10:09:23 WARNING: promotion failed;
sleep 15 # to prevent tight recovery loop

And on NODE2 I get:
/var/log/corosync.log:
Jul 03 10:17:17 [510] local2        cib:     info: cib_process_request:
	Completed cib_query operation for section
//cib/status//node_state[@id='1084752206']//transient_attributes//nvpair[@name='master-nfshome-drbd']:
No such device or address (rc=-6, origin=local/attrd/206,
version=0.347.284)
Jul 03 10:17:17 [510] local2        cib:     info: cib_process_request:
	Completed cib_apply_diff operation for section status: OK (rc=0,
origin=local1/attrd/480, version=0.347.285)
Jul 03 10:17:17 [510] local2        cib:     info: cib_process_request:
	Completed cib_apply_diff operation for section status: OK (rc=0,
origin=local1/crmd/279, version=0.347.286)


It looks like it does a "drbdadm up nfshome" on local1 but not local2.


Here is the configuration I'm using (applied using: crm configure):

property stonith-enabled=false
primitive nfshome-drbd ocf:linbit:drbd params drbd_resource="nfshome" \
  op monitor interval="29s" role="Master" \
  op monitor interval="31s" role="Slave"
ms nfshome-drbd-master nfshome-drbd \
  meta master-max="1" master-node-max="1" \
  clone-max="1" clone-node-max="1" \
  notify="true" target-role="Master"
primitive nfshome-filesystem \
  ocf:heartbeat:Filesystem \
  params device="/dev/drbd/by-res/nfshome" directory="/nfshome" fstype="ext4"
group nfshome nfshome-filesystem
colocation nfshome-colocation inf: nfshome nfshome-drbd-master
order nfshome-order inf: nfshome-drbd-master:promote nfshome:start
location nfshome-location nfshome \
  rule $id="nfshome-location-rule" 100: #uname eq local1


My DRBD config appears to be good:

root at local1:~# drbdadm up nfshome
...
root at local2:~# drbdadm up nfshome
root at local2:~# cat /proc/drbd
version: 8.4.3 (api:1/proto:86-101)
srcversion: F97798065516C94BE0F27DC

 2: cs:Connected ro:Secondary/Secondary ds:UpToDate/UpToDate A r-----
    ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0

...
root at local1:~# drbdadm primary nfshome
root at local1:~# cat /proc/drbd
version: 8.4.3 (api:1/proto:86-101)
srcversion: F97798065516C94BE0F27DC

 2: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate A r-----
    ns:0 nr:0 dw:0 dr:728 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0


so on and so forth.  Local2 has no problems being primary either.

For reference this is ubuntu server 14.04 with all the latest patches
(Pacemaker 1.1.10).

Thanks in advance.


Bryan





More information about the Pacemaker mailing list