ip_conntrack_max missing - not found!

SupermanInNY

Verified User
Joined
Sep 28, 2004
Messages
419
I got a lot of error msgs (and also got kicked out of my network - TG for KVM-OverIP) of:

ip_conntrack: table full, dropping packet.

I googled around and found that the value in ip_conntrack_max is probably not big enough and I need to increase it.

Given the answer in: http://support.imagestream.com/Resolving_ip_conntrack_table_full_Errors.html

It is a simple value change.

BUT,.. here is my problem:


server.com:/proc/sys/net/ipv4 # cat /proc/sys/net/ipv4/ip_conntrack_max
cat: /proc/sys/net/ipv4/ip_conntrack_max: No such file or directory

The directory has lots of files,.. except that one file.

OK,. let me vi /proc/sys/net/ipv4/ip_conntrack_max


NOPE.. can't do this!
It won't let me Write, no :wq! commands.

server.com:/proc/sys/net/ipv4 # less /etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details
LABEL=/ / ext3 defaults,usrquota,grpquota 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
LABEL=/home /home ext3 defaults,usrquota,grpquota 1 2
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
LABEL=/tmp /tmp ext3 defaults,nosuid,noexec 1 2
LABEL=/usr /usr ext3 defaults 1 2
LABEL=/var /var ext3 defaults 1 2
LABEL=SWAP-sda5 swap swap defaults 0 0
/etc/fstab (END)



server.com:/proc/sys/net/ipv4 # uname --all
Linux server.com 2.6.9-55.0.12.ELsmp #1 SMP Fri Nov 2 11:19:08 EDT 2007 i686 i686 i386 GNU/Linux


I tried to be 'sneaky' about it and create it elsewhere and move it:

server.com:/home/alon # mv ip_conntrack_max /proc/sys/net/ipv4/
mv: cannot create regular file `/proc/sys/net/ipv4/ip_conntrack_max': No such file or directory


Any pointers?

-Alon.
 
The /proc directory structure isn't a directory of files.

Or let me rephrase that, since in unix/linux everything is a file ;).

the /proc directory structure is really a peek/poke interface into kernel memory.

Unless you've got the same kernel as a SlipStream router, you may not be writing to the same place.

Or may be called something else.

So your first step is to find out where the file is.

On my CentOS4 system it's just where your example says it is.

Of course you can't use locate to find it; locate doesn't find files that aren't really files.

You should be able to find it using: find / -name ip_conntrack_max

Once you've found it:

If you want to risk it you can move a value to it with an echo command. If your server crashes you can reboot it; it doesn't actually write anything to the kernel. You can check the current value with the cat command.

Jeff
 
Back
Top