|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
~ I got the solution,
~ I recompile the kernel 2.6.10 with enabling IP virtual server
(downloaded from kernel.org) and complile ipvsadm from
linuxvirtaulserver.org for kernel 2.6.10 .
Now my loadbalancer working fine with SMP kernel.
Regards
Ritesh
Sebastiaan Veldhuisen wrote:
| Hi Ritesh,
|
| I have noticed the same strange behaviour this week. We have a master
| director with SLES 9 running 2.6.5 smp kernel with a hyperthreading
| processor. This machines locks up within a couple of hours.
| Our slave director has an identical software install (SLES9, install is
| with autoyast, PXE) and runs a p3 1300 non hyperthreading cpu and works
| without any problems!
|
| I'm going to run a couple of tests with non smp kernels to see if this
| is the issue i'm facing.
|
| regards,
|
| Sebastiaan Velhuisen
|
|
|
| Nielsen, Steve wrote:
|
|> We use ipvsadm on SMP kernels and it works (redhat7.3). What kernel
|> version are you having issues with?
|>
|> Steve
|>
|> -----Original Message-----
|> From: Ritesh Agrawal [mailto:ritesh.a@xxxxxxxxxxxxx]
|> Sent: Saturday, June 04, 2005 2:02 PM
|> To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
|> Subject: IPVSADM hangs with SMP kernel ??
|>
|>
|> Hi list,
|> ~ Recently i configured LVS load blanacer using ultramonkey(NAT) .
|> When machine is booted with SMP kernel and runing ldirectord
|> daemon and sending request from other host, after completing 10-15
|> request successfully , LVS server hangs.
|>
|> but when i boot the machine with non SMP kernel with same hardware
|> and software configuration , it works well.
|>
|> it means IPVSADM doesn't work with SMP kernel or any other reason.
|> is IPVSADM suitable with SMP kernel ????
|> A big question for me.
|> Thanks in advance.
|>
|> - --
|> Regards
|> Ritesh Agrawal
|> _______________________________________________
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCpshrFoz+P95jnTIRAlHvAJ9yJ4yLOhsK4BELc2SZjaE2DJPz5QCfQNZ+
JhlIayYivGcjp83zQZAeihE=
=XPyE
-----END PGP SIGNATURE-----
|
