OpenVZ Forum


Home » General » Support » TCP: time wait bucket table overflow - memory leak?
Re: TCP: time wait bucket table overflow - memory leak? [message #36788 is a reply to message #36785] Mon, 20 July 2009 06:56 Go to previous messageGo to previous message
nksupport is currently offline  nksupport
Messages: 16
Registered: June 2007
Junior Member
Quote:

I just want to clarify the situation because I don't understand clearly what your problem consists of.


me neither, that's why i am attempting to clarify it before filing.

Quote:
The last "top" output doesn't contain anything frightening from my point of view.
A "huge" load average is just a consequence of a "great" number of process. A good idea is to obtain the status of these processes. You can do it with help of "ps" utility. Please, examine their states.

It is freaking frightening because i can't understand it! There are no "great number" of processes. ps doesn't show anything unusual. The top output i provided shows a completely idle system - what are those tons of active processes? I will try to find something in the process table next time, but i had a brief look before - there's nothing strange there.

Quote:
Why do you want to increase kmemsize? The only failcounters I can see on proivided vzstats output are those concerning with privvmpages not kememsize.


i posted UBC taken during normal operation. The UBC i posted is just the info about limits set in my system. Like i wrote, kmemsize counters start growing when i encounter this issue: i hope you can trust me this much Very Happy

Quote:
What process are running in a failed VE?

like i wrote, during the last test i killed most of the apps within the failed VE. There was pretty much nothing running except for init and a few basic daemons. I'll try to grab ps next time.

Quote:
You have mentioned that ssh dies when this occurs. Don't you think that this problem relates to network? Do you have a direct access to that server to confirm that the node completely dies?

man, the server behaves exactly like you'd expect from an overloaded server Smile i just can't find the reason for this overload.
it's not a networking issue. Local login stops working as well - it just times out since the system becomes too slow to process password or rsa auth. The actual question is why the load grows infinitely: this is our problem.

Quote:
Do you have any specific settings, for example nfs inside VE?

No, there's no crap. 5 basic LAMP VEs.

Will try to collect extra data - looks like we have nothing useful yet... Thanks anyway!



"It's the power cord", I say
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message icon5.gif
Read Message
Read Message
Previous Topic: number of cpus on a x64 kernel
Next Topic: dump broken in Debian 5 lenny?
Goto Forum:
  


Current Time: Mon Jul 21 02:01:53 GMT 2025

Total time taken to generate the page: 0.07448 seconds