LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Fwd: No active connections to "Local" real server

To: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Fwd: No active connections to "Local" real server
From: Alex Davies <daviesalex@xxxxxxxxx>
Date: Sun, 16 Oct 2005 23:57:22 +0100
Dear All,

I have still struggled to set this up - this is *so* frustrating!

I have tried running ldirectord on another host with the same
connection and have established that the same node gives a problem -
so it is not a problem with local connections, but is a problem with
the setup of this particular node.

However the interfaces are set up identically and the same script is
used to bring the shared IP over. The RIP for the server works fine
from the command line using lynx. However, whatever I do, I do not
seem able to get any Active connections to go to this node, although
it does pass the health check and does pick up inactive connections.
The logs are as far as I can tell normal:

[Sun Oct 16 23:43:19 2005|ldirectord] Starting Linux Director
v1.77.2.11 as daemon
 [Sun Oct 16 23:43:19 2005|ldirectord] Added virtual server: 83.223.121.75:80
[Sun Oct 16 23:43:19 2005|ldirectord] Added real server:
83.223.121.71:80 ( x 83.223.121.75:80) (Weight set to 3)
 [Sun Oct 16 23:43:19 2005|ldirectord] Added real server:
83.223.121.72:80 ( x 83.223.121.75:80) (Weight set to 3)
 [Sun Oct 16 23:43:20 2005|ldirectord] Added real server:
83.223.121.73:80 ( x 83.223.121.75:80) (Weight set to 3)
[Sun Oct 16 23:43:20 2005|ldirectord] Added real server:
83.223.121.74:80 ( x 83.223.121.75:80) (Weight set to 1)

It is just that always there are 0 active connections:

Every 2.0s: ipvsadm -L -n                                             
                                                              Sun Oct
16 23:45:24 2005

IP Virtual Server version 1.2.0 (size=4096)
 Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  83.223.121.75:80 wrr
   -> 83.223.121.74:80             Route   1      1          4
   -> 83.223.121.73:80             Route   3      4          12
  -> 83.223.121.72:80             Route   3      3          10
  -> 83.223.121.71:80              Local   3      0          6

ifconfig on the node that is not working followed by the node that is working:

eth0      Link encap:Ethernet  HWaddr 00:14:22:72:89:80
          inet addr:83.223.121.71  Bcast:83.223.121.95   Mask:255.255.255.224
          inet6 addr: fe80::214:22ff:fe72:8980/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:9158918 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9133324 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
           RX bytes:642500975 (612.7 MiB)  TX bytes:636513079 (607.0 MiB)
          Base address:0xecc0 Memory:dfde0000-dfe00000

eth0:0    Link encap:Ethernet  HWaddr 00:14:22:72:89:80
           inet addr:83.223.121.75  Bcast:83.223.121.95  Mask:255.255.255.224
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           Base address:0xecc0 Memory:dfde0000-dfe00000

 lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask: 255.0.0.0
          inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:523008 errors:0 dropped:0 overruns:0 frame:0
          TX packets:523008 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
          RX bytes:95629058 (91.1 MiB)  TX bytes:95629058 (91.1 MiB)

lo:0      Link encap:Local Loopback
           inet addr:83.223.121.75  Mask:255.255.255.255
           UP LOOPBACK RUNNING  MTU:16436  Metric:1

And the node that is working:

eth0      Link encap:Ethernet  HWaddr 00:14:22:72:90:91
           inet addr:83.223.121.72  Bcast:83.223.121.95  Mask:255.255.255.224
          inet6 addr: fe80::214:22ff:fe72:9091/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7817 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7615 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
          RX bytes:930861 (909.0 KiB)  TX bytes:4655618 (4.4 MiB)
          Base address:0xecc0 Memory:dfde0000-dfe00000

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:10115 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10115 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
           RX bytes:4275328 (4.0 MiB)  TX bytes:4275328 (4.0 MiB)

lo:0      Link encap:Local Loopback
          inet addr:83.223.121.75  Mask:255.255.255.255
          UP LOOPBACK RUNNING  MTU:16436  Metric:1

My ldirectord.cf :

logfile="/var/log/ha/ldir.log"

# Ldirectord configuration file generated by Loadbalancer.org appliance
# Global options
checktimeout=10
checkinterval=7
 quiescent=no
autoreload=yes
 callback="/etc/ha.d/sync"
virtual=83.223.121.75:80
         real=83.223.121.71:80 gate 3 "check.cfm","DB OK"
         real=83.223.121.72:80 gate 3 "check.cfm","DB OK"
        real= 83.223.121.73:80 gate 3 "check.cfm","DB OK"
        real= 83.223.121.74:80 gate 1 "check.cfm","DB OK"
         service=http
        checktype=negotiate
         request="check.cfm"
        receive="DB OK"
         scheduler=wrr
         protocol=tcp

Does anyone have any guesses and is there anything else that I can
post to help people track this down? As you can probably tell from the
above, I have 4 Real Servers, 83.223.121.71 - 83.223.121.74. I also
have a VIP ( 83.223.121.75) which happens to be hosted on the same
server as RIP1. However, when I move the RIP to be hosted on the same
server as RIP2 it still has a problem with Real Server 1.

Many thanks,

Alex Davies

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