Hi, I'm from Japan, in trouble. In the case blow, server which was primary sometimes do not run drbd/heartbeat.
Server A(primary), Server B(secondary) is running. Shutdown A and immediately Shutdown B. Switch on only A, it dose not run drbd/heartbeat. It may happen when one server was broken. I'm using, drbd83-8.3.8-1.el5 heartbeat-3.0.5-1.1.el5 pacemaker-1.0.11-1.2.el5 resource-agents-3.9.2-1.1.el5 centos5.6 Servers are using two LANs(eth0, eth1) and not using serial cable. I checked /usr/lib/ocf/resource.d/linbit/drbd, and insert some debug codes. At drbd_stop(), in while loop, only when "Unconfigured", break and call maybe_outdate_self(). But sometimes, $OCF_RESKEY_CRM_meta_notify_master_uname or $OCF_RESKEY_CRM_meta_notify_promote_uname are not null. So, at maybe_outdate_self(), it is going to set "outdate". And, it always show warning messages below. But, "outdated" flag is set. "State change failed: Disk state is lower than outdated" " state = { cs:StandAlone ro:Secondary/Unknown ds:Diskless/DUnknown r--- }" "wanted = { cs:StandAlone ro:Secondary/Unknown ds:Outdated/DUnknown r--- }" I do not want to be set outdated flag, when shutdown both of them. I want to know what program set $OCF_RESKEY_CRM_* variables, with what condition set these variables, and when these variables are set. Thanks, Nickey _______________________________________________ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker