Ilya Eremin wrote:
Hello,
I am running a P2P related server, which has many connections to it at one time
(about 100,000 at peak times). But I have been getting
eserver invoked oom-killer: gfp_mask=0xd0, order=0, oomkilladj=0 errors
followed by
Out of socket memory
I believe this is related
Hello,
I am running a P2P related server, which has many connections to it at one time
(about 100,000 at peak times). But I have been getting
eserver invoked oom-killer: gfp_mask=0xd0, order=0, oomkilladj=0 errors
followed by
Out of socket memory
I believe this is related to rmem, but I am
Hello,
I am running a P2P related server, which has many connections to it at one time
(about 100,000 at peak times). But I have been getting
eserver invoked oom-killer: gfp_mask=0xd0, order=0, oomkilladj=0 errors
followed by
Out of socket memory
I believe this is related to rmem, but I am
Ilya Eremin wrote:
Hello,
I am running a P2P related server, which has many connections to it at one time
(about 100,000 at peak times). But I have been getting
eserver invoked oom-killer: gfp_mask=0xd0, order=0, oomkilladj=0 errors
followed by
Out of socket memory
I believe this is related
e been trying the 2.4
> > development kernels as they come out and I've been tweaking the /proc
> > filesystem variables but so far nothing seems to have fixed the
> > problem. The problem is that I get "Out of socket memory" errors and the
> > networking loc
Hello!
> What am I doing wrong?
You change parameters without investigating why failure happened.
This approach cannot succeed, of course.
> problem? Is there any way I can get runtime information from the kernel on
> things like amount of socket memory used and amount available?
cat
I've been trying the 2.4
> development kernels as they come out and I've been tweaking the /proc
> filesystem variables but so far nothing seems to have fixed the
> problem. The problem is that I get "Out of socket memory" errors and the
> networking locks up. Someti
ment kernels as they come out and I've been tweaking the /proc
> filesystem variables but so far nothing seems to have fixed the
> problem. The problem is that I get "Out of socket memory" errors and the
> networking locks up...
FWIW, the code that prints this is in ipv4/tcp_timer.
out and I've been tweaking the /proc
filesystem variables but so far nothing seems to have fixed the
problem. The problem is that I get "Out of socket memory" errors and the
networking locks up...
FWIW, the code that prints this is in ipv4/tcp_timer.c
and it looks like it's a
the 2.4
development kernels as they come out and I've been tweaking the /proc
filesystem variables but so far nothing seems to have fixed the
problem. The problem is that I get "Out of socket memory" errors and the
networking locks up. Sometimes the server will go for weeks without
Hello!
What am I doing wrong?
You change parameters without investigating why failure happened.
This approach cannot succeed, of course.
problem? Is there any way I can get runtime information from the kernel on
things like amount of socket memory used and amount available?
cat
I'm not quite clear how the settings under /proc/sys/vm/* would effect the
problem. I neglected to mention in my previous post that all web content
is served directly from the memory of the web server (no file
accesses). The only file accesses that happen are from a MySQL server
which
the /proc
filesystem variables but so far nothing seems to have fixed the
problem. The problem is that I get "Out of socket memory" errors and the
networking locks up. Sometimes the server will go for weeks without
running into the problem and other times it'll last 30 minutes. The
the /proc
filesystem variables but so far nothing seems to have fixed the
problem. The problem is that I get "Out of socket memory" errors and the
networking locks up. Sometimes the server will go for weeks without
running into the problem and other times it'll last 30 minutes. The
I'm not quite clear how the settings under /proc/sys/vm/* would effect the
problem. I neglected to mention in my previous post that all web content
is served directly from the memory of the web server (no file
accesses). The only file accesses that happen are from a MySQL server
which
15 matches
Mail list logo
