Thanks, I will try this. One more question. I have set up of two node running in Active/Standby with DRBD. Is it good practise to start heartbeat while primary node is still synching with secondary node? In other words, when drbd connection between Primary and Secondary Node is in "SyncSource" state.
In my case, if i reboot the Primary system when drbd connection is in "SyncSource" state and heartbeat is running.Secondary system reboots automaticall. Please suggest for the above. On Tue, Mar 23, 2010 at 2:09 PM, Jochen Lienhard <[email protected]> wrote: > > Hi, > > here some code of my cib.xml ... hope this will help you: > > > <master id="msDRBD"> > <meta_attributes id="msDRBD-meta_attributes"> > <nvpair id="msDRBD-meta_attributes-clone-max" name="clone-max" value="2"/> > <nvpair id="msDRBD-meta_attributes-target-role" name="target-role" > value="started"/> > <nvpair id="msDRBD-meta_attributes-clone-node-max" name="clone-node-max" > value="1"/> > <nvpair id="msDRBD-meta_attributes-master-max" name="master-max" value="1"/> > <nvpair id="msDRBD-meta_attributes-master-node-max" > name="master-node-max" value="1"/> > <nvpair id="msDRBD-meta_attributes-notify" name="notify" value="true"/> > </meta_attributes> > <primitive class="ocf" id="resDRBD" provider="heartbeat" type="drbd"> > <operations id="resDRBD-operations"> > <op id="resDRBD-op-monitor-Slave-61" interval="61" name="monitor" > role="Slave" start-delay="30" timeout="60"/> > <op id="resDRBD-op-monitor-Master-60" interval="60" name="monitor" > role="Master" start-delay="30" timeout="60"/> > </operations> > <instance_attributes id="resDRBD-instance_attributes"> > <nvpair id="resDRBD-instance_attributes-drbd_resource" > name="drbd_resource" value="drbd0"/> > </instance_attributes> > <meta_attributes id="resDRBD-meta_attributes"> > <nvpair id="resDRBD-meta_attributes-target-role" name="target-role" > value="started"/> > </meta_attributes> > </primitive> > </master> > > > and ... > > <primitive class="ocf" id="resFilesystem" provider="heartbeat" > type="Filesystem"> > <operations id="resFilesystem-operations"> > <op id="resFilesystem-op-monitor-30" interval="30" name="monitor" > start-delay="0" timeout="30"/> > </operations> > <instance_attributes id="resFilesystem-instance_attributes"> > <nvpair id="resFilesystem-instance_attributes-device" name="device" > value="/dev/drbd0"/> > <nvpair id="resFilesystem-instance_attributes-directory" > name="directory" value="/data/replicated"/> > <nvpair id="resFilesystem-instance_attributes-fstype" name="fstype" > value="ext3"/> > </instance_attributes> > </primitive> > > Umakant Goyal schrieb: > > Hi, Thanks for Quick Response. Could u please suggest me the what all the > > parameter values i need to change? > > > > > > On Tue, Mar 23, 2010 at 1:37 PM, Jochen Lienhard< > > [email protected]> wrote: > > > > > >> Hi, > >> > >> I had a similar problem too. > >> The problem was, that the system tried to demote the dbrd before unmount > >> ... even if I had > >> a rule for this ... I solved this problems changing the timeouts. It > >> seems to me that the default > >> timeout oft the filesystem-ocf is to low. > >> > >> Greetings > >> > >> Jochen > >> > >> Umakant Goyal schrieb: > >> > >>> Hi All, > >>> > >>> I have Linux-HA in Active /Standby mode. When i reboot the Active System > >>> then Standby system trys to take control of the system. But most of the > >>> > >> time > >> > >>> Secondary system restarts automatically . When i check the ha-logs to > >>> > >> figure > >> > >>> out the cause of restart then i found that problem starts from following > >>> error. > >>> > >>> Filesystem[24262]: 2010/01/18_13:17:37 INFO: /home is unmounted > >>> > >> (stopped) > >> > >>> Filesystem[24198]: 2010/01/18_13:17:37 INFO: Filesystem Resource is > >>> stopped > >>> ResourceManager[22772]: 2010/01/18_13:17:37 info: Running > >>> /etc/ha.d/resource.d/Filesystem /dev/drbd1 /home ext3 start > >>> Filesystem[24364]: 2010/01/18_13:17:37 ERROR: Couldn't mount > >>> > >> filesystem > >> > >>> /dev/drbd1 on /home > >>> Filesystem[24300]: 2010/01/18_13:17:38 ERROR: Filesystem Generic error > >>> ResourceManager[22772]: 2010/01/18_13:17:38 ERROR: Return code 1 from > >>> /etc/ha.d/resource.d/Filesystem > >>> ResourceManager[22772]: 2010/01/18_13:17:38 CRIT: Giving up resources > >>> > >> due > >> > >>> to failure of Filesystem::/dev/drbd1::/home::ext3 > >>> > >>> After encountering above error secondary system tries to giving up the > >>> resources. During this process, system fails to stop some of the > >>> > >> resources > >> > >>> then it reboots automatically. > >>> Please suggest what is the cause of above given error. > >>> > >>> Thanks in Advance > >>> _______________________________________________ > >>> Linux-HA mailing list > >>> [email protected] > >>> http://lists.linux-ha.org/mailman/listinfo/linux-ha > >>> See also: http://linux-ha.org/ReportingProblems > >>> > >>> > >>> > >> > >> -- > >> Dr. rer. nat. Jochen Lienhard > >> UB Universität Freiburg > >> Dezernat EDV > >> Tel: (0761) 203-3908 > >> Email: [email protected] > >> > >> _______________________________________________ > >> Linux-HA mailing list > >> [email protected] > >> http://lists.linux-ha.org/mailman/listinfo/linux-ha > >> See also: http://linux-ha.org/ReportingProblems > >> > >> > > _______________________________________________ > > Linux-HA mailing list > > [email protected] > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > See also: http://linux-ha.org/ReportingProblems > > > > > > > -- > Dr. rer. nat. Jochen Lienhard > UB Universität Freiburg > Dezernat EDV > Tel: (0761) 203-3908 > Email: [email protected] > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
