[Linux-cluster] failover questions after upgrade

[jason at monsterjam.org]

> http://sources.redhat.com/cluster/faq.html#rgm_wontrestart
> 
> The init script probably is returning 1 for stop-after-stop (or
> stop-when-stopped), when it should be returning 0.  This is a bug in the
> initscripts package, and here's a patch to /etc/init.d/functions to make
> httpd work normally:
> 
> https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=111998

ok, applied those patches to both /etc/init.d/functions and ran my reboot test again
rebooted tf1 and saw this on tf2 

[root at tf2 init.d]# clustat
Member Status: Quorate

  Member Name                              Status
  ------ ----                              ------
  tf1                                      Offline
  tf2                                      Online, Local, rgmanager

  Service Name         Owner (Last)                   State         
  ------- ----         ----- ------                   -----         
  Apache Service       (unknown)                      failed          
[root at tf2 init.d]#

Nov 15 17:57:34 tf2 clurgmgrd[9588]: <info> Magma Event: Membership Change 
Nov 15 17:57:34 tf2 clurgmgrd[9588]: <info> State change: tf1 DOWN 
Nov 15 17:58:24 tf2 kernel: e100: eth2: e100_watchdog: link down
Nov 15 17:58:29 tf2 kernel: CMAN: removing node tf1 from the cluster : Missed too many heartbeats
Nov 15 17:58:54 tf2 kernel: e100: eth2: e100_watchdog: link up, 100Mbps, full-duplex
Nov 15 18:01:09 tf2 kernel: CMAN: node tf1 rejoining
Nov 15 18:01:50 tf2 clurgmgrd[9588]: <info> Magma Event: Membership Change 
Nov 15 18:01:50 tf2 clurgmgrd[9588]: <info> State change: tf1 UP 

and tf2 never got the virtual cluster ip address.. Im guessing thats the real reason why apache 
cant come up on tf2

[root at tf2 init.d]# service httpd start
Starting httpd: (99)Cannot assign requested address: make_sock: could not bind to address 
192.168.1.7:80
no listening sockets available, shutting down
Unable to open logs
                                                           [FAILED]
[root at tf2 init.d]# 

and when tf1 comes back up, he doesnt get the virtual cluster ip address (10.1.1.7) either.

Jason