OpenVZ Forum


Home » General » Support » Ip_conntrack_max is a unknown key
Ip_conntrack_max is a unknown key [message #35391] Mon, 23 March 2009 09:24 Go to next message
ittec is currently offline  ittec
Messages: 41
Registered: February 2008
Member
Hi all

Im a very confused about Conntrack and TCP performance. Was one of the little issues that I noticed when we start to use OpenVZ. I don't know really if was a problem of OpenVZ or problem of Linux itself, anyway, I could resolve with success, editing values of conntrack in sysctl.conf and then applying changes:

net.ipv4.netfilter.ip_conntrack_max = 65536

We have 5 servers running under OpenVZ and kernel version is 2.6.18-92.1.13.el5.028stab059.3PAE. But recently we tried another version and now, when I try to edit sysctl.conf and apply the changes, kernel returns

error: "net.ipv4.ip_conntrack_max" is an unknown key

I checked proc subsystem and I didn't find the "file"

[root@hn19 ~]# ls -ls /proc/sys/net/ipv4/ |grep conn
[root@hn19 ~]#

I'll like to understand more this issue, because I really don't know what is the main question here, why we have troubles in past in conntrack and if is a persistent problem on TCP linux performance.

I'll keep find a solution for this but if someone is so kind to explain a little the main problem will be very helpful to us.

Thanks.
Re: Ip_conntrack_max is a unknown key [message #35394 is a reply to message #35391] Mon, 23 March 2009 12:05 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

Are ip_conntrack and xt_conntrack kernel modules loaded?

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png
Re: Ip_conntrack_max is a unknown key [message #35395 is a reply to message #35394] Mon, 23 March 2009 14:31 Go to previous messageGo to next message
ittec is currently offline  ittec
Messages: 41
Registered: February 2008
Member
Quote:

Are ip_conntrack and xt_conntrack kernel modules loaded?


Mmm, I think so:

[root@k13 ~]# lsmod |grep conn
ip_conntrack          101012  11 vzrst,ip_nat,vzcpt,xt_state
nfnetlink              40392  2 ip_nat,ip_conntrack


Is ok?

Thanks!
Re: Ip_conntrack_max is a unknown key [message #35396 is a reply to message #35395] Mon, 23 March 2009 14:56 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

Allright so what's that «another version» you referred to in your first message?

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png
Re: Ip_conntrack_max is a unknown key [message #35397 is a reply to message #35396] Mon, 23 March 2009 15:16 Go to previous messageGo to next message
ittec is currently offline  ittec
Messages: 41
Registered: February 2008
Member
Thanks Kiri

so I understand that the modules needed are correctly loaded,right? The "version" of kernel is 2.6.18-028stab060.8.
Re: Ip_conntrack_max is a unknown key [message #35398 is a reply to message #35397] Mon, 23 March 2009 15:20 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

ittec wrote on Mon, 23 March 2009 18:16

The "version" of kernel is 2.6.18-028stab060.8.


A kernel with such version was never released by OpenVZ... Where'd you get it?


Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png
Re: Ip_conntrack_max is a unknown key [message #35572 is a reply to message #35398] Mon, 06 April 2009 10:03 Go to previous message
ittec is currently offline  ittec
Messages: 41
Registered: February 2008
Member
mmm

you were right. Was no a problem with OpenVZ kernel but a Virtuozzo VZ kernel. Excuse me Embarassed

Let me ask to you a question relationship with this. In OpenVZ I had some little issues with TCP performance related with conntrack. I solved that editing sysctl.conf and increasing ip_conntrack_max value and applying changes. OpenVZ kernel was 32 bits operating system. So the issue was resolved on Hardware Node level.

It is possible that a problem of conntrack will be only a VE level? And maybe it is related with the issue well-known of "low memory"?

Sorry but, I never understand good this problem.

Thanks!
Previous Topic: forcing commands from master node
Next Topic: Asterisk conference and DAHDI (SOLVED)
Goto Forum:
  


Current Time: Tue Sep 03 18:03:26 GMT 2024

Total time taken to generate the page: 0.04972 seconds