<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 http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:11.0pt;
font-family:"Calibri","sans-serif";}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:24.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
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
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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.emailstyle17
{mso-style-name:emailstyle17;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Cambria","serif";
color:#365F91;
font-weight:bold;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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 lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Never mind I found it. I made an error in my puppet configuration that was overwriting the file with the wrong script. Doh!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Lenny<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<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""> Phil Crooker [mailto:Phil.Crooker@orix.com.au]
<br>
<b>Sent:</b> Thursday, February 13, 2014 6:04 PM<br>
<b>To:</b> Hewitt, Lenny; 'xymon@xymon.com'<br>
<b>Subject:</b> RE: Cannot get custom script column back.<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div name="divtagdefaultwrapper" id="divtagdefaultwrapper">
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;color:#282828">
<hr size="2" width="98%" align="center">
</span></div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> Xymon on behalf of Hewitt, Lenny<br>
<b>Sent:</b> Thursday, 13 February 2014 5:13 AM<br>
<b>To:</b> 'xymon@xymon.com'<br>
<b>Subject:</b> [Xymon] Cannot get custom script column back.</span><span style="font-size:12.0pt;color:#282828">
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#282828"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:#282828">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#282828"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#282828">I’m having problems with how xymon is reporting a status and wanted to give you a step-by-step detailed description of what I did to get in the state that it is in so that it will hopefully describe what to do
to fix this anomally.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#282828"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#282828">I set up a custom script to monitor the status of process, more than just monitoring to see if the daemon is up or down, etc, etc. In testing the script I used the example of the client-side script on my client.
I created the script on the clients and everything showed up on the xymon webpage and worked perfectly. I then realized that I wanted to rename the script on the client to something better describing it. So I proceeded to rename the script and update the
clientlaunch.cfg in etc on each client to reflect the new name. After a short period the column on the xymon website showing the status of the original name of the script went purple because that script name was not reporting anymore. I removed this purple
column by running xymon 127.0.0.1 “drop <HOSTNAME> <columname>”. The problem is I can’t get the column to show back up again with the status from the newly named script that is currently configured. The names of the columns were the same, just the script
name changed. I suspect that is why it is behaving this way but don’t know what to do to fix this state that it’s in.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#282828"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#282828">Any help would be greatly appreciated.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#282828"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#282828">Lenny<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#282828">--------------------------------- <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#282828"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">The name of the script wouldn't affect the test status if the renamed script is still running, it should not have gone purple. Did you change the name of the script in clientlaunch.cfg? What if
you run the script manually as the xymon user, does that appear at the server? Are you sure the script is actually running and the client is sending the results to the server - try running tcpdump to capture that traffic. Do you see any anominalies under
the xymond page of the xymon server? Are other tests from that xymon client working?</span><span style="color:#282828"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">cheers, Phil<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#282828"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">--
<o:p></o:p></span></p>
<div id="signature">
<div id="sigText">
<h1 style="margin:0in;margin-bottom:.0001pt"><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#949494">Please consider the environment before printing this e-mail<o:p></o:p></span></h1>
<p style="text-align:justify"><span style="font-size:7.0pt;font-family:"Arial","sans-serif";color:#949494">This message from ORIX Australia may contain confidential and/or privileged information. If you are not the intended recipient, any use, disclosure or
copying of this message (or of any attachments to it) is not authorised. If you have received this message in error, please notify the sender immediately and delete the message and any attachments from your system. Please inform the sender if you do not wish
to receive further communications by email. ORIX handles personal information according to a Privacy Policy that is consistent with the National Privacy Principles. Please let us know if you would like a copy.<br>
It is also available at <a href="http://www.orix.com.au" target="_blank"><span style="color:#949494">http://www.orix.com.au</span></a><o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>