LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

System crash

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: System crash
From: Sébastien BONNET <sebastien.bonnet@xxxxxxxxxxx>
Date: Thu, 30 Sep 2004 13:30:45 +0200
Hi list,

I've been using IVPS 1.0.x for years now and I never had any problem.

I recently built a new cluster, running Fedora Core 2 and IPVS 1.2.0. Since then, I'm having big problems. Eventhough the servers are not loaded, the director periodically crashed.

No more network, no more interactive console access ... the only thing left is Alt-SysRq ! No single char logged (to disk or to the console) that could help :(

Alt-SysRq-p has recently shown that something related to ipvs tcp defense was found in the stack trace. Unfornunately, I wasn't able to read enough infos as they scroll way too fast.

Right now, I don't know what I can try and test ? I've changed the NIC driver, I've stopped the backup director, I've just stopped the sync daemon ... and still hoping it won't crash again. If it crashes again, I'll run without ipvs for a few days to see if it's really the cause.

Has anybody already faced such a situation ? Any help appreciated.

Kind regards.

[root@frioul root]# uname -a
Linux frioul 2.6.5-1.358smp #1 SMP Sat May 8 09:25:36 EDT 2004 i686 i686 i386 GNU/Linux

[root@hawai root]# ipvsadm -ln
IP Virtual Server version 1.2.0 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  a.b.c.78:80 wrr
  -> a.b.c.104:80             Local   981    0          0
TCP  a.b.c.79:80 wrr
  -> a.b.c.104:80             Local   981    0          0
TCP  a.b.c.74:80 wrr
  -> a.b.c.104:80             Local   1000   0          0
TCP  a.b.c.78:443 wrr
  -> a.b.c.104:443            Local   1000   0          0
TCP  a.b.c.79:443 wrr
  -> a.b.c.104:443            Local   1000   0          0
TCP  a.b.c.74:443 wrr
  -> a.b.c.104:443            Local   1000   0          70

Setup : 2 servers with one NIC each, both acting as director and realserver, forwarding method is Direct Routing, MAC pb solved using net.ipv4.conf.{lo,all}.arp_{ignore,announce} The above ipvsadm output shows the current situation with only one active server as I investigate on the other one.

--
Sébastien BONNET     --    Ingénieur système
Tel: 04.42.25.15.40      GSM: 06.64.44.58.98
<Prev in Thread] Current Thread [Next in Thread>
  • System crash, Sébastien BONNET <=