OpenVZ Forum


Home » General » Support » Out of socket memory then crash
Out of socket memory then crash [message #11393] Thu, 22 March 2007 15:23 Go to next message
devonblzx is currently offline  devonblzx
Messages: 127
Registered: December 2006
Senior Member
I believe this is a TCP error as I have been researching about it but nothing seems to be fixing the problem.

I have noticed the error on the last two devel kernels, (2.6.18-018, 2.6.18-021). I'm not sure if it was there before but my system never crashed before.

This is what my kernel log says before the crash:

Mar 22 09:00:50  kernel: TCP: too many of orphaned sockets
Mar 22 09:01:02  last message repeated 2 times
Mar 22 09:01:07  kernel: Out of socket memory
Mar 22 09:01:52  kernel: Out of socket memory
Mar 22 09:02:24  last message repeated 10 times
Mar 22 09:47:32  kernel: printk: 22 messages suppressed.
Mar 22 09:47:32  kernel: Out of socket memory
Mar 22 11:02:49  syslogd 1.4.1: restart.


I researched and found some things to add to my sysctl.conf which now looks like...

net.ipv4.ip_forward = 1
net.ipv4.conf.default.proxy_arp = 0
net.ipv4.conf.all.rp_filter = 1
kernel.sysrq = 1
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.all.send_redirects = 0
net.ipv4.tcp_mem = 999999 1572864 1972864
net.ipv4.tcp_max_orphans 48000
net.ipv4.tcp_wmem = 4096 65536 524288
net.core.wmem_max = 1048576
net.ipv4.tcp_rmem = 4096 87380 524288
net.core.rmem_max = 1048576
net.ipv4.tcp_sack = 0
net.ipv4.tcp_timestamps = 0


My system is still crashing about once every other day, any help would be appreciated.

Thank you.


http://static.openvz.org/userbars/openvz-user-2.png
ByteOnSite President

[Updated on: Thu, 22 March 2007 15:25]

Report message to a moderator

Re: Out of socket memory then crash [message #11508 is a reply to message #11393] Mon, 26 March 2007 08:37 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Hello,

can you inform us, how it is crashing: Oops on console? Or?...

Thank you,
Vasily.
Re: Out of socket memory then crash [message #11536 is a reply to message #11508] Mon, 26 March 2007 15:14 Go to previous messageGo to next message
devonblzx is currently offline  devonblzx
Messages: 127
Registered: December 2006
Senior Member
The last message in my messages was out of socket memory and the TCP: out of orphans and my server would go unreachable.

I fixed the problem by reverting to the older 2.6.18-015 kernel. This problem only occured for me under the new 018 and 021 kernels. My system hasn't crashed in a couple days but I just realized I do have those out of socket memory messages again. The main message in my console with the 015 is TCP: time wait bucket table overflow tho. Any idea what that is?


http://static.openvz.org/userbars/openvz-user-2.png
ByteOnSite President

[Updated on: Mon, 26 March 2007 15:16]

Report message to a moderator

Re: Out of socket memory then crash [message #11562 is a reply to message #11536] Tue, 27 March 2007 08:30 Go to previous message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Seems, that this message was fixed in 028test018 (look at http://bugzilla.openvz.org/show_bug.cgi?id=460). But according to your report, in 028test018 your node gets unreachable after some time. Please, can you set up a remote console (if the node is not near) and check, is there any Ooops on it after the node gets unreachable. You can read http://wiki.openvz.org/Remote_console_setup for more information.

Your help is very appreciated,
thank you,
Vasily.
Previous Topic: Problems with NFS?
Next Topic: *SOLVED* Live Migartion + kerenl Version
Goto Forum:
  


Current Time: Sun Sep 15 06:18:41 GMT 2024

Total time taken to generate the page: 0.04800 seconds