nanny "Read Timed Out" Errors

Tue Nov 3 19:46:29 UTC 2009

Thanks for your offers of help!

I have made some changes since reading your message saying the servers
should all be on the same net -- now I have one real server and it is
on the same network as the load balancer. The output of the ipvsadmn
command you requested is below.

[root at omsbuild ~]# ipvsadm -L -n
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  192.168.0.69:80 lc

NIC/IP information:

[root at omsbuild ~]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:50:56:AE:14:E3
          inet addr:192.168.3.28  Bcast:192.168.7.255  Mask:255.255.248.0
          inet6 addr: fe80::250:56ff:feae:14e3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:35121740 errors:1120 dropped:1231 overruns:0 frame:0
          TX packets:8682408 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4182471094 (3.8 GiB)  TX bytes:606337720 (578.2 MiB)
          Interrupt:177 Base address:0x1400

eth0:1    Link encap:Ethernet  HWaddr 00:50:56:AE:14:E3
          inet addr:192.168.0.69  Bcast:192.168.7.255  Mask:255.255.248.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:177 Base address:0x1400

I'm still getting the same errors from nanny even though the real
server is now on the same net as the load balancer:

Nov  3 10:44:22 omsbuild nanny[16919]: READ to 192.168.3.38:80 timed out

As represented in eth0:1, my virtual server is listening on
192.168.0.69:80. If I do netstat, do a port/service check from a
workstation to that IP or similar, shouldn't I see the load balancer
listening on 80? Right now, I do not see the load balancer waiting for
connections on port 80.

Here is what my lvs.conf file looks like now:

serial_no = 89
primary = 192.168.3.28
service = lvs
backup = 0.0.0.0
heartbeat = 1
heartbeat_port = 539
keepalive = 6
deadtime = 18
network = tunnel
debug_level = NONE
virtual test1 {
     active = 1
     address = 192.168.0.69 eth0:1
     vip_nmask = 255.255.248.0
     port = 80
     expect = "HTTP"
     use_regex = 0
     load_monitor = none
     scheduler = lc
     protocol = tcp
     timeout = 6
     reentry = 15
     quiesce_server = 0
     server Speedy {
         address = 192.168.18.29
         active = 0
         port = 80
         weight = 1
     }
     server test1 {
         address = 65.39.179.197
         active = 0
         port = 80
         weight = 1
     }
:

Mike

On 02/11/2009, Tapan Thapa <tapan.thapa2000 at gmail.com> wrote:
> Hello Mike,
>
> I am not an expert in IPVS but recently i have setup IPVS with the help of
> Piranha and i am quite comfortable with IPVS.
>
> Please let me know your Network diagram and also the output of below
> mentioned command.
>
> ipvsadm -L -n
>
> ----------------------------------------
> I think your network diagram should be---
>
> Linux Director ----(One NIC)--->First Real Server (One NIC)
>                                        --->Second Real Server (One NIC)
> ----------------------------------------------
>
> Your Linux Director and Your real server should be on the same network
> segment. Please also post your Linux Director's (Where you have installed
> Piranha) Network cards ip information.
>
>
> Regards
> Tapan Thapa
> India
>
> On Tue, Nov 3, 2009 at 6:09 AM, mojorising <moj0rising at aim.com> wrote:
>
>> Hello!
>>
>> I have set up a test load balancer with IPVS and Piranha-GUI. For some
>> reason, when I attempt to connect to one of the two web servers I have
>> set-up via the load balancer's virtual IP, the load balancer does not
>> seem to pass those requests on to the real servers.
>>
>> The firewall on the Piranha box is off and I can successfully
>> establish HTTP sessions with netcat and telnet from the Piranha box as
>> well as from my workstation. So the web services are running and
>> connectivity to them is good.
>>
>> The error I'm getting in /var/log/messages is (public IP changed for
>> privacy):
>>
>> Nov  2 14:28:09 omsbuild nanny[13583]: READ to 65.39.169.xxx:80 timed out
>> Nov  2 14:28:10 omsbuild nanny[13582]: READ to 192.168.18.29:80 timed out
>>
>> It looks like nanny can't talk to the web servers but I can't figure
>> out why. That may not be the only problem I have here but it's
>> probably one of them. All the other services are up and seem to be
>> running fine.
>>
>> I've googled around quite a bit and checked the documentation but I
>> haven't found anything in those places that gets me to a solution.
>>
>> Can anyone out there give me a little push in the right direction as
>> to what the problem might be?
>>
>>
>> Thank you!
>>
>> Mike
>>
>>
>> My lvs.conf file:
>>
>> serial_no = 76
>> primary = 192.168.3.28
>> service = lvs
>> backup = 0.0.0.0
>> heartbeat = 1
>> heartbeat_port = 539
>> keepalive = 6
>> deadtime = 18
>> network = direct
>> debug_level = NONE
>> virtual test1 {
>>     active = 1
>>     address = 192.168.0.69 eth0:1
>>     vip_nmask = 255.255.248.0
>>     port = 3128
>>     expect = "HTTP"
>>     use_regex = 0
>>     load_monitor = none
>>     scheduler = lc
>>     protocol = tcp
>>     timeout = 6
>>     reentry = 15
>>     quiesce_server = 0
>>     server Speedy {
>>         address = 192.168.18.29
>>         active = 1
>>         port = 80
>>         weight = 1
>>     }
>>     server test1 {
>>         address = 65.39.169.xxx
>>         active = 1
>>         port = 80
>>         weight = 1
>>     }
>>
>> _______________________________________________
>> Piranha-list mailing list
>> Piranha-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/piranha-list
>>
>