Andrew Beekhof wrote: > On 7/31/07, Michael Kapp <[EMAIL PROTECTED]> wrote: >> Andrew Beekhof wrote: >>> On 7/31/07, Michael Kapp <[EMAIL PROTECTED]> wrote: >>>> Andrew Beekhof wrote: >>>>> On 7/31/07, Michael Kapp <[EMAIL PROTECTED]> wrote: >>>>>> Same with heartbeat-2.1.2 but gave me one error less: >>>>>> (IPaddr2 used as RA in cib.xml seems to be working.) >>>>>> >>>>>> BasicSanityCheck >>>>>> ================ >>>>>> >>>>>> stdout: >>>>>> ======= >>>>>> >>>>>> ... >>>>>> ERROR: IPaddr2 RA failed >>>>>> OOPS! Looks like we had some errors come up. >>>>>> 1 errors. Log file is stored in /tmp/linux-ha.testlog >>>>>> ... >>>>>> >>>>>> set -x >>>>>> ====== >>>>>> >>>>>> ... >>>>>> Testing RA: IPaddr2 >>>>>> + /usr/sbin/ocf-tester -o ip=127.0.0.20 -o netmask=32 -n DemoIPaddr2 >>>>>> /usr/lib/ocf/resource.d//heartbeat/IPaddr2 >>>>>> + rc=1 >>>>>> + '[' 1 -ne 0 ']' >>>>>> + echo 'ERROR: IPaddr2 RA failed' >>>>>> ... >>>>>> >>>>>> logfile >>>>>> ======= >>>>>> >>>>>> ... >>>>>> Testing RA: IPaddr2 >>>>>> Beginning tests for /usr/lib/ocf/resource.d//heartbeat/IPaddr2... >>>>>> * rc=5: Validation failed. Did you supply enough options with -o ? >>>>>> Aborting tests >>>>>> ERROR: IPaddr2 RA failed >>>>>> ... >>>>> I just tried the latest version too and it seemed to work. >>>>> I've had trouble in the past if no default route was present... what >>>>> does your routing table look like? >>>> With heartbeat-2.0.8 - BasicSanityCheck had no problems with this setup: >>> its a test that was introduced long after 2.0.8 >>> >>>> 10.90.1.0/24 dev eth1 proto kernel scope link src 10.90.1.51 >>>> 192.168.19.0/24 dev eth0 proto kernel scope link src 192.168.19.11 >>>> 127.0.0.0/8 dev lo scope link >>>> default via 10.90.1.252 dev eth1 >>>> >>>> 1: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000 >>>> link/ether 00:04:75:ab:a2:49 brd ff:ff:ff:ff:ff:ff >>>> inet 192.168.19.11/24 brd 192.168.19.255 scope global eth0 >>>> 2: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000 >>>> link/ether 00:0f:1f:e2:12:66 brd ff:ff:ff:ff:ff:ff >>>> inet 10.90.1.51/24 brd 10.90.1.255 scope global eth1 >>>> inet 10.90.1.50/24 brd 10.90.1.255 scope global secondary eth1:0 >>>> 3: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue >>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >>>> inet 127.0.0.1/8 brd 127.255.255.255 scope host lo >>>> >>>> 10.90.1.50 - cluster IP alias >>>> 192.168.19.0 - heartbeat/drbd net >>> looks sane enough. >>> >>> can you try running it manually (as root): >>> >>> OCF_ROOT=/usr/lib/ocf /usr/sbin/ocf-tester -o ip=127.0.0.20 -o >>> netmask=32 -n DemoIPaddr2 /usr/lib/ocf/resource.d//heartbeat/IPaddr2 >>> >>> even better, could you add "set -x" to the IPaddr2 script first? >> $> OCF_ROOT=/usr/lib/ocf /usr/sbin/ocf-tester -o ip=127.0.0.20 -o >> netmask=32 -n DemoIPaddr2 /usr/lib/ocf/resource.d//heartbeat/IPaddr2 >> Beginning tests for /usr/lib/ocf/resource.d//heartbeat/IPaddr2... >> * rc=5: Validation failed. Did you supply enough options with -o ? >> Aborting tests >> >> btw, set -x in the IPaddr2 script did not changed the output above. > > > hmm, maybe you need to pass -v to ocf-tester to get the output
Yes, thanks Andrew - that's it! ;-) ... + Echo 'IPaddr2[11328]: 2007/07/31_15:40:27' 'ERROR: Setup problem: Couldn'\''t find utility iptables' + echo 'IPaddr2[11328]: 2007/07/31_15:40:27' 'ERROR: Setup problem: Couldn'\''t find utility iptables' + exit 5 * rc=5: Validation failed. Did you supply enough options with -o ? ... Iptables was not installed! Now, can you explain me, why iptables is needed for the IPaddr2 ocf resource script? Cheers, Michael -- Yours sincerely Michael Kapp, Projectmanager IT - Avira GmbH Phone (general office): +49 (0) 7542-500 0 Phone (service department): +49 (0) 7542-500 700 Fax: +49 (0) 7542-500 724 Avira GmbH Lindauer Str. 21, D-88069 Tettnang, Germany CEO: Tjark Auerbach; AG Ulm HRB 630992
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
