On Fri, Oct 16, 2009 at 1:44 PM, Schmidt, Torsten <torsten.schm...@tecdoc.net> wrote: > i think there is a problem with the monitor operation for the stacked drbd > resouce: > > after erase + commit of my crm-config the CIP and mysqldb (lower) resource > started on node 2 > > so i looked at drbd-status on node 2 and there was nothing to be seen of the > stacked device: > > /proc/drbd > -------------------------------------------------------------------- > 0: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r---- > ns:0 nr:30 dw:30 dr:0 al:0 bm:1 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0 > -------------------------------------------------------------------- > > > ptest -L -VVVVV -s -a: > -------------------------------------------------------------------- > info: res.drbd.mysqldb:0_monitor_0 on mysqlHA2 returned 0 (ok) instead of the > expected value: 7 (not running) > notice: Operation res.drbd.mysqldb:0_monitor_0 found resource > res.drbd.mysqldb:0 active on mysqlHA2 > info: res.drbd.mysqlstack:0_monitor_0 on mysqlHA2 returned 6 (not configured) > instead of the expected value: 7 (not running) > ERROR: Hard error - res.drbd.mysqlstack:0_monitor_0 failed with rc=6: > Preventing ms.drbd.mysqlstack from re-starting anywhere in the cluster > info: res.drbd.mysqlstack:0_monitor_0 on mysqlHA1 returned 6 (not configured) > instead of the expected value: 7 (not running) > ERROR: Hard error - res.drbd.mysqlstack:0_monitor_0 failed with rc=6: > Preventing ms.drbd.mysqlstack from re-starting anywhere in the cluster > WARN: native_color: Resource res.drbd.mysqlstack:0 cannot run anywhere > -------------------------------------------------------------------- > > output of crm_mon see below. > > im i correct that i only have to load the drbd kernel-module on node 1 + 2; > pacemaker should do the rest (configuration, promote/demote...) right?
I think the RA does that too. But the RA also expects clone-max="2" and will return "not configured" if it finds it set to anything else _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
