LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Help debugging director problems after a period of time

To: "'LinuxVirtualServer.org users mailing list.'" <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Help debugging director problems after a period of time
From: "Randy Paries" <randy.paries@xxxxxxxxxxx>
Date: Fri, 2 Apr 2004 11:17:53 -0600
I am setting up a LVS-DR with ldirectord

I am running into a problem and I really do not know where to start
debugging.

The box is pretty well only running LVS-DR and ldirectord

Here is the problem. 
It works fine for a period of time. Then after a while(hours not minutes)
everything slows down.
The symptom is I can not longer ping my name server.

If I reboot it works fine again for a while. I tried killing ldirectord to
see if he was the problem but nope. I can ssh into the box just fine, it is
just the name resolution. I can not even ping the name server ip.(every
other box can, and if I reboot I can immediately.)

Ipvsadm takes about 30 seconds to display(must use the name server I assume)

So here is my config(for what it is worth) I am running the 2.4.20-30.9.um.1
kernel

Thanks for anyhelp or any suggestions on how to debug it

randy

============================================================================
===================
# Global Directives
checktimeout=3
checkinterval=10
fallback=127.0.0.1:80
autoreload=yes
logfile="/var/log/ldirectord.log"
quiescent=yes

# 
virtual=66.208.187.27:80
        real=192.168.0.203:80 gate
        real=192.168.0.204:80 gate
        fallback=127.0.0.1:80 gate
        service=http
        request="ldirectordping.html"
        receive="Test Page"
        scheduler=wlc
        persistent=1800
        netmask=255.255.255.0
        protocol=tcp
#SSL part
virtual=66.208.187.27:443
        real=192.168.0.203:443 gate
        fallback=127.0.0.1:80 gate
        service=https
        request="ldirectordping.html"
        receive="Test Page"
        scheduler=wlc
        persistent=1800
        netmask=255.255.255.0
        protocol=tcp
============================================================================
======
eth1      Link encap:Ethernet  HWaddr 00:08:54:D0:9E:06  
          inet addr:192.168.0.205  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1395 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1497 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:327849 (320.1 Kb)  TX bytes:0 (0.0 b)
          Interrupt:10 Base address:0x1800 

eth2      Link encap:Ethernet  HWaddr 00:01:02:E8:65:FF  
          inet addr:66.208.187.25  Bcast:66.208.187.127
Mask:255.255.255.128
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:727 errors:0 dropped:0 overruns:0 frame:0
          TX packets:547 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:70986 (69.3 Kb)  TX bytes:218884 (213.7 Kb)
          Interrupt:9 Base address:0x1400 

eth2:0    Link encap:Ethernet  HWaddr 00:01:02:E8:65:FF  
          inet addr:66.208.187.27  Bcast:66.208.187.27  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:727 errors:0 dropped:0 overruns:0 frame:0
          TX packets:547 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:70986 (69.3 Kb)  TX bytes:218884 (213.7 Kb)
          Interrupt:9 Base address:0x1400 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:140 (140.0 b)  TX bytes:140 (140.0 b)

============================================================================
===========

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