<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:w="urn:schemas-microsoft-com:office:word"><head><META content="text/html; charset=utf-8" http-equiv="Content-Type">
<STYLE><!-- /* Style Definitions */ p.57f7ad01-a3ec-4234-a232-4c8251a6c008, li.57f7ad01-a3ec-4234-a232-4c8251a6c008, div.57f7ad01-a3ec-4234-a232-4c8251a6c008, table.57f7ad01-a3ec-4234-a232-4c8251a6c008Table {margin:0cm; margin-bottom:.0001pt;} div.Section1 {page:Section1;} --> <!-- #57f7ad01-a3ec-4234-a232-4c8251a6c008excontact a{color:white;text-decoration:none;} #57f7ad01-a3ec-4234-a232-4c8251a6c008excontact a:hover{text-decoration:underline;} --></STYLE>
<meta content="text/html; charset=utf-8" http-equiv=Content-Type><meta content="Microsoft Word 14 (filtered medium)" name=Generator><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
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";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Actually, I have found some cases where an “auto fix” script is helpful (tools licenses going down, Oracle Listeners that die, etc.), however they are the exception not the rule. Also, they need to be coded very carefully, to make sure they don’t keep doing the fix, but the problem is not solved. Want to bring down a server, have 2000 none functional Oracle Listener processes running, doing nothing!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> …..Bruce<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> xymon-bounces@xymon.com [mailto:xymon-bounces@xymon.com] <b>On Behalf Of </b>Larry Barber<br><b>Sent:</b> Friday, April 06, 2012 4:34 PM<br><b>To:</b> xymon@xymon.com<br><b>Subject:</b> Re: [Xymon] autofixing<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>I've tried looking at Google, but can't seem to come up with a good search phrase. What I mainly get is articles about various tools that will auto repair various Microsoft products. This is the kind of thing that happens once you start on the auto repair bandwagon, but some software, then buy some more software to keep the first program running, than but some more to keep the second running then ....<br><br>Thanks,<br>Larry Barber<o:p></o:p></p><div><p class=MsoNormal>On Fri, Apr 6, 2012 at 4:31 PM, Larry Barber <<a href="mailto:lebarber@gmail.com">lebarber@gmail.com</a>> wrote:<o:p></o:p></p><p class=MsoNormal>Resending to the list, Gmail seems to be hiding the "reply to all". <br><br>Thanks,<br>Larry Barber<o:p></o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Fri, Apr 6, 2012 at 4:28 PM, Larry Barber <<a href="mailto:lebarber@gmail.com" target="_blank">lebarber@gmail.com</a>> wrote:<o:p></o:p></p><p class=MsoNormal>The kind of things that you can automate should be handled routinely, not be triggered by an alert from your monitoring tool. If you have logs growing to fast that they are filling up you file system you should find out what is filling them up and why and then fix that. Automatic log rotation and compression should be done by a tool like logrotate, not Xymon or any other monitoring tool. You shouldn't be using a monitoring tool to trigger routine maintenance, it simply causes unnecessary alerts that cause problems in other areas. <br><br>Thanks,<br>Larry Barber<o:p></o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Fri, Apr 6, 2012 at 4:06 PM, KING, KEVIN <<a href="mailto:KK1051@att.com" target="_blank">KK1051@att.com</a>> wrote:<o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Larry,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Some auto correcting is not bad. Back in the Big brother days I had a datacenter and team of folks. We managed to the “yellow” alerts. I had folks correct and build scripts to address the things that brought on the yellow so we never saw the red. This made it so very little red was ever seen.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Now the things you can automate are the disk full kind of things. If that happens you can run a script to clean logs compress and that stuff. This was usually handled by managing the yellow. There would be a script in place to keep the space to below the yellow trigger. So if you got a red it was usually a bug temp file or something that would get cleaned shortly. So say on the red alert you could have it run the cleanup script rather than waiting for your cron to do the normal cleanup.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Now on other issues it really depends on what the alert is about. You cannot automate everything economically. At some point it is cheaper and faster to put a human in the loop. I did have a script that would take the e-mail response from the alert and we could have it parse the message and do the work. This was back in the day with the RIM pagers. So you got an alert you replied to the alert with “run clean script on host” The reply e-mail was parsed in by the same script we were using to acknowledge the alert. It would parse and run a clean script. This let my admins be able to work issues while away from a PC or network connection.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>I do hear and agree with your concerns. A blanket statement from managers that do not have a full understanding of all the elements is a ruff thing to swallow. But there heart is in the right spot </span><span style='font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</span><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>I guess in a rather long rambling way I am saying that you learn and tune your systems. Address re-occurring issues so they do not. Then watch for the next thing to be addressed.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'>-Kevin</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Arial","sans-serif";color:#1F497D'> </span><o:p></o:p></p><div style='border:none;border-left:solid windowtext 1.5pt;padding:0in 0in 0in 4.0pt;border-color:-moz-use-text-color -moz-use-text-color -moz-use-text-color blue'><div><div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;border-color:-moz-use-text-color -moz-use-text-color'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a href="mailto:xymon-bounces@xymon.com" target="_blank">xymon-bounces@xymon.com</a> [mailto:<a href="mailto:xymon-bounces@xymon.com" target="_blank">xymon-bounces@xymon.com</a>] <b>On Behalf Of </b>Larry Barber<br><b>Sent:</b> Friday, April 06, 2012 1:43 PM<br><b>To:</b> <a href="mailto:xymon@xymon.com" target="_blank">xymon@xymon.com</a><br><b>Subject:</b> [Xymon] autofixing</span><o:p></o:p></p></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>My management has gotten the idea that we should be automating the repair processes on our servers. They want things set up so that when a fault is detected a script is run that attempts to repair it. I've tried to convince them that this is a profoundly wrong-headed idea, but I'm not having much luck. Do any of you know of any articles or resources that might help convince them? <br><br>Thanks,<br>Larry Barber<o:p></o:p></p></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div>
<P CLASS="57f7ad01-a3ec-4234-a232-4c8251a6c008"> </P>
<P CLASS="57f7ad01-a3ec-4234-a232-4c8251a6c008"><FONT FACE="Arial"><FONT SIZE="2"><FONT COLOR="#999999"><FONT COLOR="#000000"><STRONG>Bruce<FONT COLOR="#808080"><FONT COLOR="#000000"> White</FONT></FONT></STRONG></FONT></FONT></FONT></FONT></P>
<P CLASS="57f7ad01-a3ec-4234-a232-4c8251a6c008"><FONT FACE="Arial"><FONT SIZE="2"><FONT COLOR="#808080">Senior Enterprise Systems Engineer | Phone: 1-630-671-5169 | Fax: 630-893-1648 | bewhite@fellowes.com | <A HREF="http://www.fellowes.com/">www.fellowes.com</A></FONT></FONT></FONT></P>
<P CLASS="57f7ad01-a3ec-4234-a232-4c8251a6c008"><FONT FACE="Arial" SIZE="2"></FONT> </P>
<P CLASS="57f7ad01-a3ec-4234-a232-4c8251a6c008"><IMG ALIGN="baseline" ALT="" BORDER="0" HSPACE="0" SRC="cid:fellbrand1.jpg@0b301163.887243a1"> </P>
<P CLASS="57f7ad01-a3ec-4234-a232-4c8251a6c008"><FONT FACE="Arial" SIZE="2"></FONT> </P>
<P CLASS="57f7ad01-a3ec-4234-a232-4c8251a6c008"><FONT SIZE="+0"></FONT><STRONG></STRONG><FONT SIZE="+0"></FONT><FONT SIZE="+0"></FONT><FONT SIZE="+0"></FONT><FONT COLOR="#808080" FACE="Arial" SIZE="1">Disclaimer: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc.</FONT></P>
<P CLASS="57f7ad01-a3ec-4234-a232-4c8251a6c008"><FONT FACE="Arial" SIZE="2"></FONT> </P>
<P CLASS="57f7ad01-a3ec-4234-a232-4c8251a6c008"><FONT FACE="Arial" SIZE="2"></FONT></P></BODY></HTML>