<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;
mso-fareast-language:SV;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=SV link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I think this is somehow related to oversized status messages. We were having problems with this on 4.3.0 beta, and we also had a lot of oversized status messages (ports etc). Since we increased the max message size, we have not seen the problem with the disk test.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>/Johan<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Shailesh Paudyal [mailto:shailesh.paudyal@gmail.com] <br><b>Sent:</b> den 23 september 2010 22:57<br><b>To:</b> xymon@xymon.com<br><b>Subject:</b> Re: [xymon] Problem with disk monitoring<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks Henrik,<o:p></o:p></p><div><p class=MsoNormal>But I still see the problem, please see the following alert came from xymon a week or so ago.....<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoPlainText>red Su] Aug 22 01:26:51 EDT 2010 - Filesystems NOT ok &red 21% / (20461936% used) has reached the PANIC level (95%) &red 1% /app (65009052% used) has reached the PANIC level (95%) &red 1% /home (112112360% used) has reached the PANIC level (95%) &red 6% /var (8933348% used) has reached the PANIC level (95%) &red 1% /tmp (18638136% used) has reached the PANIC level (95%) &red 49% /boot (48938% used) has reached the PANIC level (95%) &red 11% /u01 (218810168% used) has reached the PANIC level (95%) &red 7% /u04 (228560164% used) has reached the PANIC level (95%) &red 35% /u02 (1154279480% used) has reached the PANIC level (95%) &red 24% /old_u02 (1507070236% used) has reached the PANIC level (95%)<o:p></o:p></p><p class=MsoPlainText> <o:p></o:p></p><p class=MsoPlainText>Filesystem 1<o:p></o:p></p><p class=MsoPlainText>24-]locks Used Available Capacity Mounted on<o:p></o:p></p><p class=MsoPlainText>/dev/sda5 27054004 5195620 20461936 21% /<o:p></o:p></p><p class=MsoPlainText>/dev/sdb1 68814716 253696 65009052 1% /app<o:p></o:p></p><p class=MsoPlainText>/dev/sdc2 118417044 192356 112112360 1% /home<o:p></o:p></p><p class=MsoPlainText>/dev/sda3 9920624 475208 8933348 6% /var<o:p></o:p></p><p class=MsoPlainText>/dev/sdc1 19840892 178616 18638136 1% /tmp<o:p></o:p></p><p class=MsoPlainText>/dev/sda1 101086 46929 48938 49% /boot<o:p></o:p></p><p class=MsoPlainText>/dev/mapper/VolGroup01-u01 258022788 26105832 218810168 11% /u01<o:p></o:p></p><p class=MsoPlainText>/dev/mapper/VolGroup04-u04 258022788 16355836 228560164 7% /u04<o:p></o:p></p><p class=MsoPlainText>/dev/mapper/VolGroup03-u03 1857784872 609135396 1154279480 35% /u02<o:p></o:p></p><p class=MsoPlainText>/dev/mapper/VolGroup02-u02 2064204960 452279172 1507070236 24% /old_u02<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Thu, Sep 23, 2010 at 3:45 PM, Henrik Størner <<a href="mailto:henrik@hswn.dk">henrik@hswn.dk</a>> wrote:<o:p></o:p></p><p class=MsoNormal>This is a somewhat old post, but I'm responding anyway ...<o:p></o:p></p><div><p class=MsoNormal><br>In <<a href="mailto:AANLkTinFdgiz2ie3NCxhuop8picZj6izZPdH6fESQfif@mail.gmail.com">AANLkTinFdgiz2ie3NCxhuop8picZj6izZPdH6fESQfif@mail.gmail.com</a>> Steve Holmes <<a href="mailto:sholmes42@mac.com">sholmes42@mac.com</a>> writes:<br><br>>>>> Please see below, there is a problem with disk monitoring on one of the<br>>>>> server. Can some one tell me if I did something wrong?<br>>>>><br>>>>> W]d Jul 28 10:34:31 EDT 2010 - Filesystems NOT ok<br>>>>><br>>>>> 7% / (8816628% used) has reached the PANIC level (95%)<br>>>>> 38% /u01 (90371708% used) has reached the PANIC level (95%)<br>>>>><o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>>>>> Filesystem 10<br>>>>> 4-b]ocks Used Available Capacity Mounted on<br>>>>> /dev/sda9 9920592 591896 8816628 7% /<br>>>>> /dev/sda10 152435112 54195172 90371708 38% /u01<br>>>>> /dev/sda8 9920592 154056 9254468 2% /tmp<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>>It appears that Xymon has slipped one field to the left in parsing the df<br>>output. The string at the beginning of each of the lines before the actual<br>>df ouput should be the name of the filesystem (plus an icon, but we'll<br>>ignore that for now). Then it is using the available number as the percent<br>>used, which, of course, is huge.<br><br>>I don't know if this is causing the problem but there is some funkiness with<br>>the first line of the df output. It is broken between the 10 and the 4 and<br>>there is a ']' instead of an 'l' in the word "blocks". Maybe this is a<br>>cut/paste error, but if not, it is certainly not right.<br><br><o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>There is a bug somewhere in the Xymon 4.3.0-beta code with the "df"<br>status handling. I've seen it cause random RRD files to appear for<br>systems that don't have such filesystems, and occasionally it would<br>also result in this behaviour where a disk status goes wild.<br><br>I haven't been able to nail it yet, mostly because it seems to happen<br>very rarely and completely without any pattern. It would seem like<br>some sort of memory corruption problem, but I've had the client-message<br>handler running for days with valgrind (memory access checker) enabled,<br>and it came up with nothing.<br><br>Very annoying.<br><br><br>Regards,<br>Henrik<br><br><br>To unsubscribe from the xymon list, send an e-mail to<br><a href="mailto:xymon-unsubscribe@xymon.com">xymon-unsubscribe@xymon.com</a><br><br><o:p></o:p></p></div><p class=MsoNormal><br><br clear=all><br>-- <br>Shailesh K. Paudyal<br><a href="mailto:shailesh.paudyal@gmail.com">shailesh.paudyal@gmail.com</a><o:p></o:p></p></div></div></body></html>