Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I had the same problem. Check that your heartbeat timeouts in /etc/ha.d/ha.cf are greater than your drbd timeouts in /etc/drbd.conf. It was caused by my setting the heartbeat timeouts very low to detect failures quickly without updating the drbd timeouts. When my failover occurred drbd had not yet given up on the other node and refused to become primary. You can check if that is your problem by waiting for another minute after the failover then running drbdsetup from the command line. If it works then you may have to do some tuning on your drbd timeouts. > -----Original Message----- > From: John S Little [SMTP:JSLittl at Hendricks.org] > Sent: Monday, December 13, 2004 7:51 AM > To: drbd-user at lists.linbit.com > Subject: [DRBD-user] drbd not coming up as primary on failover > > Hi all, > I have drbd 0.7.5 installed on two machines with SuSE Enterprise Server 9. > > When I stop machine-a machine-b > sees that it is stopped but does not bring up the drbd disks on machine-b > as primary. > > I have 3 drbd disks. The log output is shown below for the first disk. All > > three of the disks have the same > output with the exception of the mountpoints and drbd[x] numbers. > > /etc/ha.d/resource.d IPaddr 128.1.245.240 16 start done. RC=0 > Dec 12 14:12:02 fp3lb heartbeat: info: Running > /etc/ha.d/resource.d/drbddisk drbd0 start > Dec 12 14:12:02 fp3lb heartbeat: debug: Starting > /etc/ha.d/resource.d/drbddisk drbd0 start > Dec 12 14:12:02 fp3lb heartbeat: debug: /etc/ha.d/resource.d/drbddisk > drbd0 start done. RC=0 > Dec 12 14:12:02 fp3lb heartbeat: info: Running > /etc/ha.d/resource.d/Filesystem /dev/drbd0 www xfs start > Dec 12 14:12:02 fp3lb heartbeat: debug: Starting > /etc/ha.d/resource.d/Filesystem /dev/drbd0 www xfs start > Dec 12 14:12:02 fp3lb heartbeat: ERROR: Couldn't mount filesystem > /dev/drbd0 on www > Dec 12 14:12:02 fp3lb heartbeat: debug: /etc/ha.d/resource.d/Filesystem > /dev/drbd0 www xfs start done. RC=1 > Dec 12 14:12:02 fp3lb heartbeat: ERROR: Return code 1 from > /etc/ha.d/resource.d/Filesystem > > drbd status shows: > fp3lb: etc ha.d # rcdrbd status drbd driver loaded OK; device status: > > version: 0.7.5 (api:76 proto:74) SVN Revision: 1578 build by > xjlittle at fp3lb, 2004-11-01 12:24:45 > 0: cs:WFConnection st:Secondary Unknown ld:Consistent > ns:1053189 nr:6854481 dw:6854998 dr:1053429 al:0 bm:1494 lo:0 pe:0 ua:0 > ap:0 > 1: cs:WFConnection st:Secondary Unknown ld:Consistent > ns:520554 nr:3585188 dw:3585550 dr:521315 al:1 bm:1061 lo:0 pe:0 ua:0 ap:0 > 2: cs:WFConnection st:Secondary Unknown ld:Consistent > ns:520454 nr:3454184 dw:3454443 dr:520896 al:1 bm:1006 lo:0 pe:0 ua:0 ap:0 > > When machine-a comes back up it makes itself primary and resyncs ok with > machine-b. I have insured that the drbd.conf and haresource files are the > same on both machines. Here is the haresource file: > > fp3la 128.1.245.240 16 drbddisk::drbd0 Filesystem:: dev drbd0:: > www::xfs \ > drbddisk::drbd1 Filesystem:: dev drbd1:: home::xfs \ > drbddisk::drbd2 Filesystem:: dev drbd2:: share2::xfs \ > rcsmb rcnmb rcwinbind apachectl > fp3lb > > I understand from reading the manual that drbddisk is the script that runs > > to configure drbd as primary. What am I missing here or need to do > > so that machine-b will make itself primary? Thanks for your help > and insights. > > John Little > HRH IS Department > 317-718-4752 > jslittl at hendricks.org > > > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user