Linux sometimes kernel panics when starting memcached... (eek)
Justin Matlock
jmat@shutdown.net
Tue, 2 Sep 2003 16:12:35 -0400
This is a multi-part message in MIME format.
------=_NextPart_000_0007_01C3716D.06124360
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
This is the strangest thing I've seen...
I just upgraded two of my webservers to Linux 2.4.22, virgin, which I =
then patched with the ipvs and the epoll patches; both applied cleanly, =
without rejections. The servers work fine, until I start up memcached =
-- and every single time, the machines will kernel panic (aiee!) within =
3 minutes. If I don't start memcached, the machine runs fine for hours =
-- until I get bored waiting for it to kernel panic, and I start =
memcached.. *boom*.
I have no idea how memcached could be causing this, unless there's =
something funky about the epoll patch (that's written for 2.4.21, but it =
merges clean into 2.4.22).
This happens with 1.1.8, the 1.1.9 snapshot from early August, and the =
latest memcached from CVS.
The servers in question are Dell PowerEdge 650's, 2.8ghz P4, and 2GB =
RAM... these are rock solid servers.. my other two are running Linux =
2.4.21 and memcached, and are fine.=20
So.. I guess this is a warning, of sorts... if you're thinking about =
upgrading your kernel to 2.4.22, you might want to wait until the 2.4.22 =
epoll patch is released before running memcached on them. :)
Justin
------=_NextPart_000_0007_01C3716D.06124360
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1226" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>This is the strangest thing I've=20
seen...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I just upgraded two of my webservers to =
Linux=20
2.4.22, virgin, which I then patched with the ipvs and the epoll =
patches; both=20
applied cleanly, without rejections. The servers work fine, until =
I start=20
up memcached -- and every single time, the machines will kernel panic =
(aiee!)=20
within 3 minutes. If I don't start memcached, the machine runs =
fine for=20
hours -- until I get bored waiting for it to kernel panic, and I start=20
memcached.. *boom*.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I have no idea how memcached could be =
causing this,=20
unless there's something funky about the epoll patch (that's written for =
2.4.21,=20
but it merges clean into 2.4.22).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>This happens with 1.1.8, the 1.1.9 =
snapshot from=20
early August, and the latest memcached from CVS.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The servers in question are Dell =
PowerEdge 650's,=20
2.8ghz P4, and 2GB RAM... these are rock solid servers.. my other=20
two are running Linux 2.4.21 and memcached, and are fine. =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>So.. I guess this is a warning, of =
sorts... if=20
you're thinking about upgrading your kernel to 2.4.22, you might want to =
wait=20
until the 2.4.22 epoll patch is released before running memcached on =
them.=20
:)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Justin</FONT></DIV></BODY></HTML>
------=_NextPart_000_0007_01C3716D.06124360--