LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

ldirectord not correctly starting after heartbeat upgrade

To: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: ldirectord not correctly starting after heartbeat upgrade
From: Simon Detheridge <simon@xxxxxxxxxx>
Date: Mon, 30 Oct 2006 21:56:36 +0000
Okay, I have another problem. (not having much luck... :-)

After solving my previous problem on my backup director, I then proceeded to upgrade my primary director (which was working fine) from heartbeat 1.2.3 to 1.2.5. All my configuration files remain the same. However, upon restarting heartbeat, ldirectord does not appear to set up my tunnels properly. It seems to hang, or something.

Here is what ipvsadm says on the working box:

# ipvsadm -Ln
IP Virtual Server version 1.2.0 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  10.32.32.17:80 wlc
  -> 127.0.0.1:80                 Local   1      0          0
TCP  10.32.32.15:80 wlc
  -> 10.0.0.100:80                Tunnel  50     0          0
  -> 10.0.0.101:80                Tunnel  50     0          0
TCP  10.32.32.17:443 wlc
  -> 127.0.0.1:443                Local   1      0          0
TCP  10.32.32.15:443 wlc
  -> 10.0.0.101:443               Tunnel  50     0          0
  -> 10.0.0.100:443               Tunnel  50     0          0

10.32.32.17 is supposed to be like that

Now... when the newly upgraded box is first started, shows nothing set up (as expected):
# ipvsadm
IP Virtual Server version 1.2.0 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn

After starting heartbeat however, it shows the following:

# ipvsadm
IP Virtual Server version 1.2.0 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  10.32.32.17:www wlc
  -> localhost:www                Local   1      0          0
TCP  10.32.32.15:www wlc
TCP  10.32.32.17:https wlc
TCP  10.32.32.15:https wlc

It seems to get stuck at this point. When I stop heartbeat, it does not return to the blank initial state, ipvsadm still shows the output directly above.

My syslog (grep ldirectord) on the broken machine, shows:
Oct 30 21:41:54 [ldirectord] Invoking ldirectord invoked as: /etc/ha.d/resource.d/ldirectord start _
Oct 30 21:41:54 [ldirectord] Starting Linux Director v1.77.2.51 as daemon_
Oct 30 21:41:54 [ldirectord] Added virtual server: 10.32.32.17:80_
Oct 30 21:41:54 [ldirectord] Added virtual server: 10.32.32.17:443_
Oct 30 21:41:54 [ldirectord] Added virtual server: 10.32.32.15:80_
Oct 30 21:41:54 [ldirectord] Added virtual server: 10.32.32.15:443_
Oct 30 21:41:54 [ldirectord] Added fallback server: 127.0.0.1:80 ( x 10.32.32.17:80) (Weight set to 1)_

On the working machine, it shows much more:
Oct 30 21:42:35 [ldirectord] Invoking ldirectord invoked as: /etc/ha.d/resource.d/ldirectord start _
Oct 30 21:42:35 [ldirectord] Starting Linux Director v1.77.2.51 as daemon_
Oct 30 21:42:35 [ldirectord] Added virtual server: 10.32.32.17:80_
Oct 30 21:42:35 [ldirectord] Added virtual server: 10.32.32.17:443_
Oct 30 21:42:35 [ldirectord] Added virtual server: 10.32.32.15:80_
Oct 30 21:42:35 [ldirectord] Added virtual server: 10.32.32.15:443_
Oct 30 21:42:35 [ldirectord] Added fallback server: 127.0.0.1:80 ( x 10.32.32.17:80) (Weight set to 1)_ Oct 30 21:42:35 [ldirectord] Added fallback server: 127.0.0.1:443 ( x 10.32.32.17:443) (Weight set to 1)_ Oct 30 21:42:35 [ldirectord] Added fallback server: 127.0.0.1:80 ( x 10.32.32.15:80) (Weight set to 1)_ Oct 30 21:42:35 [ldirectord] Added fallback server: 127.0.0.1:443 ( x 10.32.32.15:443) (Weight set to 1)_ Oct 30 21:42:36 [ldirectord] Quiescent real server: 10.0.0.100:443 ( x 10.32.32.15:443) (Weight set to 0)_ Oct 30 21:42:36 [ldirectord] Quiescent real server: 10.0.0.101:80 ( x 10.32.32.15:80) (Weight set to 0)_ Oct 30 21:42:36 [ldirectord] Quiescent real server: 10.0.0.101:443 ( x 10.32.32.15:443) (Weight set to 0)_ Oct 30 21:42:36 [ldirectord] Quiescent real server: 10.0.0.100:80 ( x 10.32.32.15:80) (Weight set to 0)_ Oct 30 21:42:36 [ldirectord] Restored real server: 10.0.0.100:80 ( x 10.32.32.15:80) (Weight set to 50)_ Oct 30 21:42:36 [ldirectord] Deleted fallback server: 127.0.0.1:80 ( x 10.32.32.15:80)_ Oct 30 21:42:36 [ldirectord] Restored real server: 10.0.0.101:80 ( x 10.32.32.15:80) (Weight set to 50)_ Oct 30 21:42:36 [ldirectord] Restored real server: 10.0.0.100:443 ( x 10.32.32.15:443) (Weight set to 50)_ Oct 30 21:42:36 [ldirectord] Deleted fallback server: 127.0.0.1:443 ( x 10.32.32.15:443)_ Oct 30 21:42:36 [ldirectord] Restored real server: 10.0.0.101:443 ( x 10.32.32.15:443) (Weight set to 50)_

my ldirectord.cf (and all files in /etc/ha.d are identical on the 2 machines, and it was working fine before I upgraded the package.

Any ideas?

Thanks,
Simon

--
Simon Detheridge
SEN Developer, Widgit Software






This message has been scanned for viruses by BlackSpider MailControl - 
www.blackspider.com

<Prev in Thread] Current Thread [Next in Thread>