Out of socket memory [message #11959] |
Thu, 12 April 2007 19:25 |
dlzinc
Messages: 34 Registered: March 2006
|
Member |
|
|
I'm getting a lot of "Out of socket memory" messages on console. I've looked at some past posts... (like http://forum.openvz.org/index.php?t=msg&goto=10220&& amp; amp;srch=out+of+socket+memory#msg_10220 ) but the settings don't seem to apply to me.
Server runs several high load many-many connection VEs.
# cat /proc/user_beancounters | grep tcp | sort
numtcpsock 13 27 9223372036854775807 9223372036854775807 0
numtcpsock 29 38 250 250 0
numtcpsock 3 21 80 80 0
numtcpsock 4 21 250 250 0
numtcpsock 4 22 250 250 0
numtcpsock 4 4 80 80 0
numtcpsock 48 181 500 500 0
numtcpsock 68 343 700 700 0
tcprcvbuf 0 0 319488 524288 0
tcprcvbuf 0 8904 319488 524288 0
tcprcvbuf 1058296 2166624 10485760 15728640 0
tcprcvbuf 131072 667400 1048576 1688576 0
tcprcvbuf 212992 953776 9223372036854775807 9223372036854775807 0
tcprcvbuf 519384 1101680 4194304 6291456 0
tcprcvbuf 65536 133368 1048576 1688576 0
tcprcvbuf 65536 688904 1048576 1688576 0
tcpsndbuf 0 0 319488 524288 0
tcpsndbuf 0 13776 319488 524288 0
tcpsndbuf 1141400 3874264 10485760 15728640 0
tcpsndbuf 149184 284648 1048576 1688576 0
tcpsndbuf 358744 565648 9223372036854775807 9223372036854775807 0
tcpsndbuf 532816 3119728 4194304 6291456 0
tcpsndbuf 69504 271552 1048576 1688576 0
tcpsndbuf 69504 554232 1048576 1688576 0
Nowhere near barrier or limit...
# sysctl net.ipv4.tcp_mem
net.ipv4.tcp_mem = 16777216 33554432 67108864
# sysctl net.ipv4.tcp_max_orphans
net.ipv4.tcp_max_orphans = 65536
I bumped up tcp_mem by... a lot, but I'm still getting these messages. Any ideas?
kernel-smp-2.6.18-ovz028stab023.1 (binary RPM from openvz.org, will upgrade to new RHEL5 kernel soon)
[Updated on: Thu, 12 April 2007 19:27] Report message to a moderator
|
|
|
|
Re: Out of socket memory [message #12008 is a reply to message #11998] |
Sat, 14 April 2007 00:22 |
dlzinc
Messages: 34 Registered: March 2006
|
Member |
|
|
It's not so much a stability/crashing problem. Like you, I've had no stability related issues while getting this message either. It's more of a "why am I still getting this message" problem.
|
|
|