Hi On Sun, Feb 22, 2015 at 03:14:19PM -0500, Stephen R Guglielmo wrote: > Hi list, > > I have a VPS with a company. The image I initially chose was Debian > Wheezy. I immediately upgraded to Jessie. I updated the kernel and > rebooted. However, it seems I can't use iptables: > > $ sudo iptables --list > modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could > not open moddep file '/lib/modules/3.2.0-4-amd64/modules.dep.bin' > > iptables v1.4.21: can't initialize iptables table `filter': Table does > not exist (do you need to insmod?) > Perhaps iptables or your kernel needs to be upgraded. > > 3.2.0-4-amd64 is from Wheezy. It seems that the system is still looking > for the previous kernel. Does anyone have information about this?
What does "uname -a" report? This should tell you what the running kernel version is. It could be a case of your providing implementing your Virtual Private Server using kernel cgroups - e.g. via Linux Containers (LXC). If so, then you do not control what kernel you run - you share the kernel of the host operating system, but have limited access inside it. Tools like grub and lilo do not apply inside Linux Containers either. A VPC is a very close approximation to a "real" hardware server, but not quite the same. One relatively easy way of detecting whether you're inside a LXC is to run "uptime" - this will report the uptime of the host kernel. If you recently rebooted your VPS, you will see an uptime which is "too long". Tools like the "imvirt" package can also tell you what virtualisation you're running under. Hope this helps -- Karl E. Jorgensen -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150222213646.ga24...@eee.karl.home.jorgensen.org.uk
