[Linux-cluster] rgmanager is ping-ponging service

[Mark Hlawatschek]

Hi, 

some additional info:

setting recovery="relocate" to the service definition solved it for now. 

Nevertheless, with recovery="restart" rgmanager should also recognize that 
bond1 is not up and relocate the service to node2.

Any opinions ?

Mark

On Friday 16 March 2007 14:49:15 Mark Hlawatschek wrote:
> Hi,
>
> I have the following configuration:
> 2-node cluster with a priorized failover group:
> [...]
> <failoverdomain name="FD" ordered="1" restricted="1">
>                                 <failoverdomainnode name="node1"
> priority="1"/>
>                                 <failoverdomainnode name="node2"
> priority="2"/>
> </failoverdomain>
> [...]
>
> Two IP resources configured:
> <resources>
>           <ip address="10.0.46.46" monitor_link="1"/>
>           <ip address="10.226.3.80" monitor_link="1"/>
>  </resources>
>
> and a service:
> <service autostart="1" domain="FD" name="VIP">
>           <ip ref="10.0.46.46"/>
>           <ip ref="10.226.3.80"/>
> </service>
>
> bond1 is configured
> - node1: 10.0.46.48
> - node2: 10.0.46.47
>
> bond2 is configured:
> - node1: 10.226.3.82
> - node2: 10.226.3.81
>
> Now, if I shut down bond1 on node1. the service ping-pongs on node1:
> Here's the rgmanager output:
>
> node1:
> <debug>  Checking 10.0.46.46, Level 0
> <warn>   10.0.46.46 is not configured
> [28810] notice: status on ip "10.0.46.46" returned 1 (generic error)
> [28810] notice: Stopping service VIP
> <debug>  10.0.46.46 is not configured
> <info>   Removing IPv4 address 10.226.3.80 from bond2
>
> node2:
> [23903] notice: Service VIP is stopped
> [23903] debug: Sent relocate request to 1
>
> node1:
> [29867] notice: Service VIP is recovering
> [29867] notice: Recovering failed service VIP
> <debug>  Link for bond2: Detected
> <info>   Adding IPv4 address 10.226.3.80 to bond2
> <debug>  Sending gratuitous ARP: 10.226.3.80 00:19:bb:e9:2a:c6 brd
> ff:ff:ff:ff:ff:ff
> [29867] notice: Service VIP started
> <info>   Executing /etc/init.d/ldap status
> <debug>  Checking 10.0.46.46, Level 10
> <warn>   10.0.46.46 is not configured
> [30905] notice: status on ip "10.0.46.46" returned 1 (generic error)
> [30905] notice: Stopping service VIP
> <debug>  10.0.46.46 is not configured
> <info>   Removing IPv4 address 10.226.3.80 from bond2
>
> Any ideas ?
>
> Mark

-- 
Gruss / Regards,

** Visit us at CeBIT 2007 in Hannover/Germany **
** in Hall 5, Booth G48/2  (15.-21. of March) **

Dipl.-Ing. Mark Hlawatschek
http://www.atix.de/
http://www.open-sharedroot.org/

**
ATIX - Ges. fuer Informationstechnologie und Consulting mbH
Einsteinstr. 10 - 85716 Unterschleissheim - Germany