I'm installing heartbeat in debian lenny for example and I have a problem. When start the server it have follow error: root@nodo2:/etc/ha.d# /etc/init.d/heartbeat restart Stopping High-Availability services: Done. Waiting to allow resource takeover to complete: Done. Starting High-Availability services: 2009/09/22_09:05:27 INFO: Resource is stopped Done. Also suddenly on node1. --------------------------------------------------------------------- My config files: ha.cf: debugfile /var/log/ha-debug logfile /var/log/ha-log keepalive 2 deadtime 30 warntime 10 initdead 120 udpport 694 bcast eth1 auto_failback on node nodo1 nodo2 ping 192.168.1.254 haresources: nodo1 IPaddr::192.168.1.10/24/eth1 apache2 proftpd authkeys: auth 1 1 sha1 hola ------------------------------------------------------------------ I have the config files identical in two nodes. My /var/log/messages: Sep 22 08:18:09 nodo2 kernel: [ 12.017110] lp0: using parport0 (interrupt-driven). Sep 22 08:18:09 nodo2 kernel: [ 12.464000] Adding 1502036k swap on /dev/sda5. Priority:-1 extents:1 across:1502036k Sep 22 08:18:09 nodo2 kernel: [ 12.964927] EXT3 FS on sda1, internal journal Sep 22 08:18:09 nodo2 kernel: [ 14.519125] ip_tables: (C) 2000-2006 Netfilter Core Team Sep 22 08:18:09 nodo2 kernel: [ 14.589539] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1 Sep 22 08:18:09 nodo2 kernel: [ 15.791522] NET: Registered protocol family 10 Sep 22 08:18:09 nodo2 kernel: [ 15.792243] lo: Disabled Privacy Extensions Sep 22 08:18:12 nodo2 kernel: [ 21.057055] warning: `proftpd' uses 32-bit capabilities (legacy support in use) Sep 22 08:38:08 nodo2 -- MARK -- Sep 22 08:56:54 nodo2 kernel: [ 2343.356033] NET: Registered protocol family 17 The server it's working good but I don't know that error... Can I help me please any anybody?? Sorry for my english. Thanks in adanced.
Any errors in /var/log/syslog? Do you see the virtual IP on any of the nodes in the output of Code: ifconfig ?
About heartbeat and drbd Thanks Falko. yes, see this: NODE1 root@nodo1:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:50:8d:73:20:4c inet addr:192.168.1.8 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::250:8dff:fe73:204c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:38198 errors:0 dropped:0 overruns:0 frame:0 TX packets:34852 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:20931242 (20.9 MB) TX bytes:5928984 (5.9 MB) Interrupt:18 Base address:0xa000 eth0:0 Link encap:Ethernet HWaddr 00:50:8d:73:20:4c inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:18 Base address:0xa000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:19404 errors:0 dropped:0 overruns:0 frame:0 TX packets:19404 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4585138 (4.5 MB) TX bytes:4585138 (4.5 MB) NODE2 root@nodo1:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:56:8E:89:20:9z inet addr:192.168.1.7 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::250:8dff:fe73:204c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:38198 errors:0 dropped:0 overruns:0 frame:0 TX packets:34852 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:20931242 (20.9 MB) TX bytes:5928984 (5.9 MB) Interrupt:18 Base address:0xa000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:19404 errors:0 dropped:0 overruns:0 frame:0 TX packets:19404 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4585138 (4.5 MB) TX bytes:4585138 (4.5 MB) The server it's work 100% but... root@nodo1:/etc/ha.d# /etc/init.d/heartbeat start logd is already running Starting High-Availability services: 2009/09/23_14:45:16 INFO: Running OK 2009/09/23_14:45:16 CRITICAL: Resource IPaddr::192.168.1.10/24/eth0 is active, a 2009/09/23_14:45:16 CRITICAL: Non-idle resources can affect data integrity! 2009/09/23_14:45:16 info: If you don't know what this means, then get help! 2009/09/23_14:45:16 info: Read the docs and/or source to /usr/share/heartbeat/Re CRITICAL: Resource IPaddr::192.168.1.10/24/eth0 is active, and should not be! CRITICAL: Non-idle resources can affect data integrity! info: If you don't know what this means, then get help! info: Read the docs and/or the source to /usr/share/heartbeat/ResourceManager fo 2009/09/23_14:45:16 CRITICAL: Non-idle resources will affect resource takeback! 2009/09/23_14:45:16 CRITICAL: Non-idle resources may affect data integrity! Done. root@nodo1:/etc/ha.d# /etc/init.d/heartbeat restart Stopping High-Availability services: Done. Waiting to allow resource takeover to complete: Done. Starting High-Availability services: 2009/09/23_14:46:01 INFO: Resource is stopped Done. But it is less significant. Now I'm installing drbd ddrbd-modules and drbd-utils but I'm running the commands follow: nodo1:/etc# drbdadm create-md vm1 md_offset 3997446144 al_offset 3997413376 bm_offset 3997290496 Found ext3 filesystem which uses 3903760 kB current configuration leaves usable 3903604 kB Device size would be truncated, which would corrupt data and result in 'access beyond end of device' errors. You need to either * use external meta data (recommended) * shrink that filesystem first * zero out the device (destroy the filesystem) Operation refused. Command 'drbdmeta /dev/drbd0 v08 /dev/sda5 internal create-md' terminated with e xit code 40 drbdadm aborting ----------------------------------------------------------------------- root@nodo1:/etc/ha.d# fdisk -l Disk /dev/sda: 122.9 GB, 122942324736 bytes 255 heads, 63 sectors/track, 14946 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xbe427406 Device Boot Start End Blocks Id System /dev/sda1 * 1 1912 15358108+ 83 Linux /dev/sda2 1913 14946 104695605 5 Extended /dev/sda5 1913 2167 2048256 82 Linux swap / Solaris /dev/sda6 2168 2186 152586 83 Linux /dev/sda7 2187 10366 65705818+ 83 Linux /dev/sda8 10367 14946 36788818+ 83 Linux I used /dev/sda6 for meta-data and /dev/sda7 for disk. My drbd.conf global { usage-count yes; } common { syncer { rate 10M; } } resource drbd0 { protocol C; net { cram-hmac-alg sha1; shared-secret "FooFunFactory"; } on nodo1 { device /dev/drbd0; disk /dev/sda7; address 192.168.1.8:7789; meta-disk internal; } on nodo2 { device /dev/drbd0; disk /dev/sda7; address 192.168.1.7:7789; meta-disk internal; } } /dev/sda7 as well as /dev/sda8 are identical in size on node1 and node2, Not that I'm doing wrong. Can I help me, please?
I have resolved my problem Hi, I solved this problem by doing a dd if=/dev/zero of=/dev/sda5 bs=1M count=128 By the way, I suppose that the error message "If you want me to do this, you need to zero out the first part of the device (destroy the content)." should be more detailed and with the suggestion command like above " dd if=/dev/zero of=/dev/sda5 bs=1M count=128"included.It will help a lot for new comers. Thank You All.
