[Pacemaker] Is it possible for ocf:heartbeat:IPaddr2 to be on different NICs?

[daniel qian]

On 2010-04-23, at 12:13 PM, daniel qian wrote:

> 
> On 2010-04-23, at 12:04 PM, Dejan Muhamedagic wrote:
> 
>> Hi,
>> 
>> On Fri, Apr 23, 2010 at 11:44:16AM -0400, daniel qian wrote:
>>> We have a simple two-node cluster with apache running together with two floating IPs as shown below:
>>> 
>>> node gamma
>>> node sql
>>> primitive ClusterIP ocf:heartbeat:IPaddr2 \
>>>       params ip="x.x.x.x" cidr_netmask="32" \
>>>       op monitor interval="30s" \
>>>       meta target-role="Started"
>>> primitive apache ocf:heartbeat:apache \
>>>       params configfile="/usr/local/apache2/conf/httpd.conf" httpd="/usr/local/apache2/bin/httpd" \
>>>       op monitor interval="1min" \
>>>       meta target-role="Started"
>>> primitive secure2 ocf:heartbeat:IPaddr2 \
>>>       params ip="y.y.y.y" cidr_netmask="32" \
>>>       op monitor interval="30s"
>>> group WebCluster ClusterIP secure2 apache
>>> property $id="cib-bootstrap-options" \
>>>       dc-version="1.0.6-f709c638237cdff7556cb6ab615f32826c0f8c06" \
>>>       cluster-infrastructure="openais" \
>>>       expected-quorum-votes="2" \
>>>       stonith-enabled="false" \
>>>       no-quorum-policy="ignore" \        
>>> 
>>> 
>>> The floating IPs can start fine on the node1 with eth0 in the same network block of the two IPS - x.x.x.x and y.y.y.y but they cant start on the second node with eth1 meant for binding these two floating IPs. 
>>> 
>>> [root at sql conf]# crm_mon -1
>>> 
>>> 
>>> ============
>>> Last updated: Fri Apr 23 11:31:15 2010
>>> Stack: openais
>>> Current DC: sql - partition with quorum
>>> Version: 1.0.6-f709c638237cdff7556cb6ab615f32826c0f8c06
>>> 2 Nodes configured, 2 expected votes
>>> 1 Resources configured.
>>> ============
>>> 
>>> Online: [ sql gamma ]
>>> 
>>> Resource Group: WebCluster
>>>    ClusterIP  (ocf::heartbeat:IPaddr2):       Started sql
>>>    secure2    (ocf::heartbeat:IPaddr2):       Started sql
>>>    apache     (ocf::heartbeat:apache):        Started sql
>>> 
>>> Failed actions:
>>>   ClusterIP_monitor_0 (node=gamma, call=2, rc=5, status=complete): not installed
>>>   secure2_monitor_0 (node=gamma, call=3, rc=5, status=complete): not installed 
>>> 
>>> 
>>> snippet of /var/log/messages of the second node:
>>> 
>>> Apr 23 05:11:11 gamma attrd: [2664]: info: crm_new_peer: Node sql now has id: 16847020
>>> Apr 23 05:11:11 gamma attrd: [2664]: info: crm_new_peer: Node 16847020 is now known as sql
>>> Apr 23 05:11:11 gamma attrd: [2664]: info: find_hash_entry: Creating hash entry for probe_complete
>>> Apr 23 05:11:11 gamma attrd: [2664]: info: attrd_perform_update: Delaying operation probe_complete=<null>: cib not connected
>>> Apr 23 05:11:11 gamma attrd: [2664]: info: attrd_perform_update: Delaying operation terminate=<null>: cib not connected
>>> Apr 23 05:11:11 gamma attrd: [2664]: info: attrd_perform_update: Delaying operation shutdown=<null>: cib not connected
>>> Apr 23 05:11:11 gamma attrd: [2664]: info: find_hash_entry: Creating hash entry for last-failure-apache
>>> Apr 23 05:11:11 gamma attrd: [2664]: info: attrd_perform_update: Delaying operation last-failure-apache=<null>: cib not connected
>>> Apr 23 05:11:11 gamma attrd: [2664]: info: find_hash_entry: Creating hash entry for fail-count-apache
>>> Apr 23 05:11:11 gamma attrd: [2664]: info: attrd_perform_update: Delaying operation fail-count-apache=<null>: cib not connected
>>> Apr 23 05:11:11 gamma crmd: [2666]: info: do_lrm_rsc_op: Performing key=8:299:7:645d88d1-3c62-4652-87a6-3f63037ee41c op=ClusterIP_monitor_0 )
>>> Apr 23 05:11:11 gamma lrmd: [2663]: info: rsc:ClusterIP:2: probe
>>> Apr 23 05:11:11 gamma crmd: [2666]: info: do_lrm_rsc_op: Performing key=9:299:7:645d88d1-3c62-4652-87a6-3f63037ee41c op=secure2_monitor_0 )
>>> Apr 23 05:11:11 gamma lrmd: [2663]: info: rsc:secure2:3: probe
>>> Apr 23 05:11:11 gamma crmd: [2666]: info: do_lrm_rsc_op: Performing key=10:299:7:645d88d1-3c62-4652-87a6-3f63037ee41c op=apache_monitor_0 )
>>> Apr 23 05:11:11 gamma lrmd: [2663]: info: rsc:apache:4: probe
>>> Apr 23 05:11:11 gamma IPaddr2[2678]: ERROR: Setup problem: Couldn't find utility ip
>>> Apr 23 05:11:11 gamma crmd: [2666]: info: process_lrm_event: LRM operation ClusterIP_monitor_0 (call=2, rc=5, cib-update=8, confirmed=true) not installed
>>> Apr 23 05:11:11 gamma IPaddr2[2679]: ERROR: Setup problem: Couldn't find utility ip
>> 
>> You need to install the ip utility (iproute2).
>> 
> 
> iproute2 is there.
> 
> [root at gamma log]# rpm -qa | grep -i iproute
> iproute-2.6.18-10.el5
> [root at gamma log]# which ip
> /sbin/ip
> 
> Is it possible that pacemanager couldnt find it for some reasons?
> 

I found there is a function called check_binary in /usr/lib/ocf/resource.d/heartbeat/IPaddr2. the error message  "Couldnt fnd utility ip" is probably produced by this function. But I was not able to locate this function. Any one knows which file this function is in?

Thanks,
Daniel