Hello,

On 10/17/2011 02:53 PM, SINN Andreas wrote:
> Hello!
> 
> I have installed drbd 8.4.0 on RHEL 6 and want to build a cluster with 
> corosync. The drbd runs without any problem.
> 
> When I configure with crm and want to start, I get the following error in the 
> crm_mon:
> 
> Failed actions:
>     data_monitor_0 (node=cl-sftp-server1, call=2, rc=6, status=complete): not 
> configured
>     data_monitor_0 (node=cl-sftp-server2, call=2, rc=6, status=complete): not 
> configured
> 
> When I do a crm_verify -LV , I get the following errors:
> 
> crm_verify[6097]: 2011/10/17_14:51:46 ERROR: unpack_rsc_op: Hard error - 
> data_monitor_0 failed with rc=6: Preventing data from re-starting anywhere in 
> the cluster
> crm_verify[6097]: 2011/10/17_14:51:46 ERROR: unpack_rsc_op: Hard error - 
> data_monitor_0 failed with rc=6: Preventing data from re-starting anywhere in 
> the cluster
> 
> cat /etc/drbd.conf
> global {
>   usage-count yes;
> }
> common {
>   net {
>     protocol C;
>   }
> }
> resource data {
>   meta-disk internal;
>   device    /dev/drbd0;
>   syncer {
>     verify-alg sha1;
>   }
>   net {
>     allow-two-primaries;

^^^^^^^^^^^^^
Don't enable this if you don't know what you are doing ...

>   }
>   on cl-sftp-server1 {
>     disk       /dev/sda3;
>     address    10.100.49.101:7790;
>   }
> 
>   on cl-sftp-server2 {
>     disk       /dev/sda3;
>     address    10.100.49.102:7790;
>   }
> 
> crm configure show:
> node cl-sftp-server1
> node cl-sftp-server2
> primitive data ocf:linbit:drbd \
>         params drbd_resource="data" \
>         op monitor interval="60s" \
>         op monitor interval="10" role="Master" \
>         op monitor interval="30" role="Slave"
> property $id="cib-bootstrap-options" \
>         dc-version="1.0.11-a15ead49e20f047e129882619ed075a65c1ebdfe" \
>         cluster-infrastructure="openais" \
>         expected-quorum-votes="2" \
>         default-action-timeout="240" \
>         stonith-enabled="false"
> 
> Can you someone help? What is the failure?

You need to configure a Master/Slave rescource, not only the
primitive...e.g:

master ms_data data meta notify=true

should solve your problem ... and reading through your logs should also
reveal this ;-)

Regards,
Andreas

-- 
Need help with Pacemaker or DRBD?
http://www.hastexo.com/now

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to