Re: 2.6.18-028test007.1 crush [message #9177 is a reply to message #9176] |
Thu, 21 December 2006 02:50 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) |
dagr
Messages: 83 Registered: February 2006
|
Member |
|
|
restarted with kernel 2.6.9 023stab037.3
got just same error in message log
Checked sysctl
sudo sysctl -a | grep -i tcp_max
net.ipv4.netfilter.ip_conntrack_tcp_max_retrans = 3
net.ipv4.tcp_max_syn_backlog = 1024
net.ipv4.tcp_max_tw_buckets_ve = 2048
net.ipv4.tcp_max_tw_kmem_fraction = 128
net.ipv4.tcp_max_tw_buckets = 180000
net.ipv4.tcp_max_orphans = 131072
set net.ipv4.tcp_max_syn_backlog = 2048
No more erorr messages so far.
First question - why net.ipv4.tcp_max_tw_buckets_ve and net.ipv4.tcp_max_tw_buckets - differ so much ? It looks like this parameter affects HN as well , ie VPS 0 .
How far is it safe to increase this parameter in case i have no running VPSs at all, is it safe to set it 180000 ?
Still wondering if that kernel panic was caused by this thing , it used to work ok for 2 day with that error messages.
|
|
|