Hi Dejan, thanks for your response, but : - the releases are those delivered with RHEL6 snapshot 4, so I can't easily upgrade it. - and ok /findif/ is called inside IPaddr with OCF_RESKEY variables, but when tracing IPaddr, I can see that /findif/ is called only with the OCF_RESKEY_ip value (which is rightly set) and no other variables. Nethertheless, /findif/ call in IPaddr returns 1.
Regards Alain > Hi, > > On Thu, Jun 03, 2010 at 02:07:23PM +0200, Alain.Moulle wrote: > > Hi , > > > > I got a problem when starting a failover ip ocf:heartbeat resource > > IPaddr and > > the problem seems to be that the /findif/ (version 2.99.1) command > > That release is rather old. Can you please upgrade to 3.0.3, > resource-agents 1.0.3, and cluster-glue 1.0.5. > > > always return 1 when > > starting the resource. So I tried it manually and got an error that I > > don't understand : > > /usr/lib64/heartbeat/findif *12.13.0.1* > > This is wrong usage. findif gets the information through > environment variables, as shown below. > > > /usr/lib64/heartbeat/findif version 2.99.1 Copyright Alan Robertson > > > > Usage: /usr/lib64/heartbeat/findif [-C] > > Options: > > -C: Output netmask as the number of bits rather than as 4 octets. > > Environment variables: > > OCF_RESKEY_ip ip address (mandatory!) > > OCF_RESKEY_cidr_netmask netmask of interface > > OCF_RESKEY_broadcast broadcast address for interface > > OCF_RESKEY_nic interface to assign to > > That's really the basic functionality. Don't see anything special > in your configuration. It should just work. > > Thanks, > > Dejan > > > and $?=1 > > > > whereas ifconfig displays: > > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP > > qlen 1000 > > link/ether 00:31:22:da:8a:1a brd ff:ff:ff:ff:ff:ff > > inet *12.13.0.1*/16 brd 12.13.255.255 scope global eth0 > > etc. > > > > I can't find where is the problem ? > > > > Thanks for your help. > > Regards. > > Alain Moull? _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
