|
It did it again...(lots of info , sorry)
All I did was ifdown eth2:0 and the problem went away
eth2:0 is my VIP for the director.
If I do a ifup eth2:0 name lookups fail again.
The easiest way to see if I am having problems is to do a
#host www.yahoo.om
I get the error
;; connection timed out; no servers could be reached
I then do
#ifdown eth2:0
# host www.yahoo.om
Host www.yahoo.om not found: 3(NXDOMAIN)
I tried /etc/rc.d/init.d/network/restart
No luck
I also tried to restart the network in the two realservers.
I do know that if a reboot the director will then work ok again.
If a do a
route -n (if I leave out the -n, it comes back with the same info but takes
1 minute)
I wonder why I have 3 0.0.0.0's. They are there when it is working or
failing(but the 66.208.187.126 has been resolved)
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
66.208.187.0 0.0.0.0 255.255.255.128 U 0 0 0 eth2
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 66.208.187.126 0.0.0.0 UG 0 0 0 eth2
0.0.0.0 66.208.187.126 0.0.0.0 UG 0 0 0 eth2
0.0.0.0 66.208.187.126 0.0.0.0 UG 1 0 0 eth2
Here is
ifconfig
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:197132 errors:0 dropped:0 overruns:0 frame:0
TX packets:220622 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:46306165 (44.1 Mb) 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:56794 errors:0 dropped:0 overruns:0 frame:0
TX packets:4440 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:5706731 (5.4 Mb) TX bytes:725812 (708.8 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:56794 errors:0 dropped:0 overruns:0 frame:0
TX packets:4440 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:5706731 (5.4 Mb) TX bytes:725812 (708.8 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:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:240 (240.0 b) TX bytes:240 (240.0 b)
ipvsadm --list -n (is fast)
IP Virtual Server version 1.0.10 (size=65536)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 66.208.187.27:80 wlc persistent 1800 mask 255.255.255.0
-> 192.168.0.203:80 Route 1 0 0
-> 127.0.0.1:80 Local 0 0 0
TCP 66.208.187.27:443 wlc persistent 1800 mask 255.255.255.0
-> 192.168.0.203:443 Route 1 0 0
-> 127.0.0.1:443 Local 1 0 0
# Global Directives
checktimeout=3
checkinterval=10
fallback=127.0.0.1:80
autoreload=yes
logfile="/var/log/ldirectord.log"
#logfile="local0"
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
-----Original Message-----
From: lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Gaston
Gorosterrazu
Sent: Friday, April 02, 2004 12:22 PM
To: LinuxVirtualServer.org users mailing list.
Subject: Re: Help debugging director problems after a period of time
When it happens again:
killall -HUP named
And let us know.
----- Original Message -----
From: "Randy Paries" <randy.paries@xxxxxxxxxxx>
To: "'LinuxVirtualServer.org users mailing list.'"
<lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, April 02, 2004 12:07 PM
Subject: RE: Help debugging director problems after a period of time
> Responses....
>
>
> > Here is the problem.
> > It works fine for a period of time. Then after a while(hours not
> > minutes) everything slows down.
>
> >>>is it busy (top)?
>
> No very low 1% - 5%
>
>
> > The symptom is I can not longer ping my name server.
> >>>by IP or name?
>
> Only ping by ip, since I the box I am trying to get to is the 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,
> >>>does this mean it's working again after you kill ldirectord or "nope"
> it's not working still.
>
> No it still does not work. The only thing that fixes it is the reboot. Now
> next time I will try restarting the network service.
>
>
> > it is just the name resolution.
> >>>I don't know what this means.
>
> Resolving name to ip using dns
>
>
> > Ipvsadm takes about 30 seconds to display(must use the name server I
> > assume)
> >>>try ipvsadm -n then ipvsadm
> >>>netstat -n, netstat
> >>>route -n, route
>
>
> I will try these. I did try these (ipvsadm , netstat -a , route)
>
> They all kind of hung for a while and then displayed. I did not try
the -n's
> though.
>
> Thanks
>
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
