|
John Reuning wrote:
Okay, as long as you've rebooted then, the running kernel should match the
modules. Here are a couple more thoughts:
1. Have you tried running insmod or modprobe on the ipvs modules manually.
Maybe you would get helpful info with a -v flag or two. Do the modules
load properly?
Yes, I have loaded both ip_vs and ip_vs_wlc manually. In both cases, I
have tried the -v flag and it returns nothing alarming:
# insmod -v ip_vs.o
Using ip_vs.o
Symbol version prefix ''
# insmod -v ip_vs_wlc.o
Using ip_vs_wlc.o
Symbol version prefix ''
2. I wonder if ipvsadm needs to match ipvs. Have you tried compiling that
with your current kernel source tree?
Yes, I have tried compiling ipvsadm from ipvs-1.0.10 and from
ipvsadm-1.21. In both cases using /usr/src/linux pointing to the right
kernel source. In both cases I get the same error.
On Thu, 21 Aug 2003, Marc Tardif wrote:
Good point. However, I always run the following commands when building
or rebuilding a kernel:
# make menuconfig
# make dep
# make bzImage
# make modules
# make modules_install
# cp System.map /boot/System.map-2.4.21
# cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.21
John Reuning wrote:
Did you rebuild the entire kernel group (kernel + modules) after patching
ipvs, changing the config settings, and compiling? Kernel module
versioning is usually turned on by default, and that can cause problems
when trying to load modules that weren't built at the same time as the
running kernel.
_______________________________________________
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
--
Marc Tardif
Sitepak
(514) 866-8883
|
