>>> On 11/11/2009 at 05:08 PM, abhishek agrawal <[email protected]> >>> wrote: > I am trying to start a failover IP on a m/c . I m getting following error msg > > > crmd[8153]: 2009/11/11_11:19:07 info: attrd_update: Sent update: > probe_complete=true for localhost > attrd[8152]: 2009/11/11_11:19:07 info: attrd_ha_callback: flush > message from sit-dm-2.localdomain > attrd[8152]: 2009/11/11_11:19:07 info: find_hash_entry: Creating hash > entry for fail-count-rep_resource_10.1.1.177 > attrd[8152]: 2009/11/11_11:19:07 info: attrd_ha_callback: flush > message from sit-dm-2.localdomain > attrd[8152]: 2009/11/11_11:19:07 info: find_hash_entry: Creating hash > entry for last-failure-rep_resource_10.1.1.177 > crmd[8153]: 2009/11/11_11:19:09 info: do_lrm_rsc_op: Performing > key=15:6:0:2fc668c9-869a-4c06-ab08-c865373d27ce > op=ip_resource15.154.59.160_start_0 ) > lrmd[8150]: 2009/11/11_11:19:09 info: rsc:ip_resource15.154.59.160: start > lrmd[8150]: 2009/11/11_11:19:09 info: RA output: > (ip_resource15.154.59.160:start:stderr) ERROR: Cannot use default > route w/o netmask [15.154.59.160] > > IPaddr[8439]: 2009/11/11_11:19:09 ERROR: /usr/lib64/heartbeat/findif > failed [rc=1]. > crmd[8153]: 2009/11/11_11:19:09 info: process_lrm_event: LRM operation > ip_resource15.154.59.160_start_0 (call=7, rc=1, cib-update=18, > confirmed=true) complete unknown error > > my network config is as follows: > eth0 Link encap:Ethernet HWaddr 00:13:21:C9:5C:FF > inet addr:15.154.59.15 Bcast:15.154.59.255 Mask:255.255.254.0 > inet6 addr: fe80::213:21ff:fec9:5cff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:459289 errors:0 dropped:0 overruns:0 frame:0 > TX packets:20878 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:53030356 (50.5 MiB) TX bytes:4138331 (3.9 MiB) > Interrupt:217 > > can someone help me out..what does findif do..and what can be the > problem due to which it fails
findif tries to figure out which interface should be used for a given IP address. Check the output of "route -n" to see if there's anything weird-looking there, or try explicitly specifying a netmask or nic in the cidr_netmask or nic parameter for your IP address resource. Regards, Tim -- Tim Serong <[email protected]> Senior Clustering Engineer, Novell Inc. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
