Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
OK so i just read on a post that i am not suppose to have heartbeat
and my services start on boot up..... so i removed them from startup via
the "update-rc.d -f heartbeat remove" command on my Debian system and
then rebooted, everything came up????
Hhmmm can i not add heartbeat as an S99heartbeat on start up rather than
have to manually start it after boot?
also i see this in my /proc/drbd n the primary
version: 8.0.4 (api:86/proto:86)
SVN Revision: 2947 build by root at stewie, 2008-01-17 12:26:19
0: cs:StandAlone st:Primary/Unknown ds:UpToDate/DUnknown r---
ns:0 nr:0 dw:40 dr:1549 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
resync: used:0/31 hits:0 misses:0 starving:0 dirty:0 changed:0
act_log: used:0/257 hits:10 misses:0 starving:0 dirty:0 changed:0
And on secondary...
version: 8.0.4 (api:86/proto:86)
SVN Revision: 2947 build by root at megs, 2008-01-17 13:19:05
0: cs:StandAlone st:Secondary/Unknown ds:UpToDate/DUnknown r---
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
resync: used:0/31 hits:0 misses:0 starving:0 dirty:0 changed:0
act_log: used:0/257 hits:0 misses:0 starving:0 dirty:0 changed:0
Does this mean drbd is not working correctly?
Rob Morin
Dido Internet Inc.
Montreal,Canada
http://www.dido.ca
514-990-4444
Rob Morin wrote:
> Hello all, my first post here so be gentle....
>
> I install DRBD 8 via Debian package on Debian Etch...
>
> i pretty much got everything working, except.....
>
> When i reboot the primary nothing comes up.... i get this in the
> heartbeat log.... The secondary is up all the time and does not have
> control of anything...
> Please let me know if more info or log file entries are needed....
>
> conf and log files are below.... i removed comments to shorten post
> ---------------------------------------------------------------------
> Heartbeat log file.....
>
> /dev/drbd0: Wrong medium type
> INFO: Filesystem Success
> INFO: IPaddr Success
>
>
> drbd.conf file......
>
>
> global {
> usage-count yes;
> }
>
>
>
> common {
> syncer { rate 10M; }
> }
>
>
> resource web {
>
> protocol C;
>
> handlers {
> pri-on-incon-degr "echo o > /proc/sysrq-trigger ; halt -f";
>
> pri-lost-after-sb "echo o > /proc/sysrq-trigger ; halt -f";
>
> local-io-error "echo o > /proc/sysrq-trigger ; halt -f";
>
> outdate-peer "/usr/sbin/drbd-peer-outdater";
> }
>
> startup {
> wfc-timeout 60;
>
> degr-wfc-timeout 120; # 2 minutes.
> }
>
> disk {
> on-io-error detach;
>
> }
>
> net {
> after-sb-0pri disconnect;
>
> after-sb-1pri disconnect;
>
>
> after-sb-2pri disconnect;
>
> rr-conflict disconnect;
>
> }
>
> syncer {
> rate 100M;
>
> }
>
> on stewie {
> device /dev/drbd0;
> disk /dev/md2;
> address 192.168.5.149:7788;
> flexible-meta-disk internal;
>
> }
>
> on megs {
> device /dev/drbd0;
> disk /dev/md2;
> address 192.168.5.151:7788;
> meta-disk internal;
> }
> }
>
>
>
> ha.cf conf file......
>
> stewie:/etc# cat ha.d/ha.cf
> logfacility daemon # This is deprecated
> keepalive 1 # Interval between heartbeat (HB) packets.
> deadtime 10 # How quickly HB determines a dead node.
> warntime 5 # Time HB will issue a late HB.
> initdead 120 # Time delay needed by HB to report a
> dead node.
> udpport 694 # UDP port HB uses to communicate
> between nodes.
> ping 192.168.5.1 # Ping VMware Server host to simulate
> network resource.
> serial /dev/ttyS0 # Which interface to use for HB packets.
> auto_failback on # Auto promotion of primary node upon
> return to cluster.
> node stewie # Node name must be same as uname -r.
> node megs # Node name must be same as uname -r.
>
> respawn hacluster /usr/lib/heartbeat/ipfail
> # Specifies which programs to run at startup
>
> use_logd yes # Use system logging.
> logfile /var/log/hb.log # Heartbeat logfile.
> debugfile /var/log/heartbeat-debug.log # Debugging logfile.
>
> haresources file.....
>
> stewie IPaddr::192.168.5.199 drbddisk::web \
> Filesystem::/dev/drbd0::/var/www::ext3::defaults apache2
> ---------------------------------------------------------------------------------------------------
>
>
> Also which is supposed to start first drbd or heartbeat? as drbd
> starts first as per rc2.d
>
> lrwxrwxrwx 1 root root 14 2008-01-16 14:41 S70drbd -> ../init.d/drbd
> lrwxrwxrwx 1 root root 19 2008-01-16 15:14 S75heartbeat ->
> ../init.d/heartbeat
>
> A ps -ax shows this after the reboot, but nothing comes up the ip is
> not enabled and my /var/www i snot mounted
>
> 2957 ? S 0:00 [drbd0_worker]
> 2972 ? S 0:00 [drbd0_receiver]
> 2987 ? S 0:00 ha_logd: read process
> 2988 ? S 0:00 ha_logd: write process
> 3112 ? SLs 0:00 heartbeat: master control process
> 3119 ? Ss 0:00 /usr/sbin/atd
> 3126 ? Ss 0:00 /usr/sbin/cron
> 3139 ? SL 0:00 heartbeat: FIFO reader
> 3140 ? SL 0:00 heartbeat: write: ping 192.168.5.1
> 3141 ? SL 0:00 heartbeat: read: ping 192.168.5.1
> 3148 ? SL 0:00 heartbeat: write: serial /dev/ttyS0
> 3149 ? SL 0:00 heartbeat: read: serial /dev/ttyS0
>
> Thanks to all for your help.....
>