<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:x="urn:schemas-microsoft-com:office:excel" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40" dir="ltr"><head></head><body lang="EN-GB" style="text-align:left; direction:ltr;"><div>I don't have an answer as to what's going on yet, but I changed the xymonclient_config.xml on one of the problem hosts and then restarted the XymonPSClient service and it immediately created the cpu graph and started populating the data correctly. The change I made to the config was only to remove the secure server name with user/pass and replace it with just the server name so it would connect insecurely over port 1984. I know it's been stated that the same data is sent over port 443 as it is over 1984, but something weird is going on here. Any ideas?</div><div><br></div><div><br></div><div><u><b>Here's a chunk of info from the xymonlog for the functioning port 1984 host.</b></u></div><div>2021-05-28 08:25:01.663 Setting thread/UI culture to en-US</div><div>2021-05-28 08:25:04.342 Resetting thread/UI culture to previous: en-US / en-US</div><div>2021-05-28 08:25:04.346 Event log Security entries since last scan: 455</div><div>2021-05-28 08:25:04.348 Entries to add to payload: 455 </div><div>2021-05-28 08:25:04.351 Payload length reached 2265, greater than 1024</div><div>2021-05-28 08:25:04.352 Event log System adding to payload</div><div>2021-05-28 08:25:04.353 Event log Application adding to payload</div><div>2021-05-28 08:25:04.356 Event log processing finished</div><div>2021-05-28 08:25:04.357 XymonProcs start</div><div>2021-05-28 08:25:04.389 XymonProcs finished.</div><div>2021-05-28 08:25:04.392 XymonNetstat start</div><div>2021-05-28 08:25:04.415 XymonNetstat finished.</div><div>2021-05-28 08:25:04.418 XymonPorts start</div><div>2021-05-28 08:25:04.459 XymonPorts finished.</div><div>2021-05-28 08:25:04.461 XymonIpconfig start</div><div>2021-05-28 08:25:04.479 XymonIpconfig finished.</div><div>2021-05-28 08:25:04.481 XymonRoute start</div><div>2021-05-28 08:25:04.546 XymonRoute finished.</div><div>2021-05-28 08:25:04.548 XymonIfstat start</div><div>2021-05-28 08:25:04.550 wanted address families: InterNetwork</div><div>2021-05-28 08:25:04.564 XymonIfstat finished.</div><div>2021-05-28 08:25:04.566 XymonSvcs start</div><div>2021-05-28 08:25:04.694 XymonSvcs finished.</div><div>2021-05-28 08:25:04.746 XymonWho start</div><div>2021-05-28 08:25:04.748 XymonWho finished.</div><div>2021-05-28 08:25:04.750 XymonUsers start</div><div>2021-05-28 08:25:04.773 XymonUsers finished.</div><div>2021-05-28 08:25:04.775 Executing XymonServiceCheck</div><div>2021-05-28 08:25:04.777 Executing XymonDirSize</div><div>2021-05-28 08:25:04.780 Executing XymonDirTime</div><div>2021-05-28 08:25:04.781 Executing XymonTerminalServicesSessionsCheck</div><div>2021-05-28 08:25:04.784 Executing XymonActiveDirectoryReplicationCheck</div><div>2021-05-28 08:25:04.786 Executing XymonProcessRuntimeCheck</div><div>2021-05-28 08:25:04.788 Sending output for procruntime</div><div>2021-05-28 08:25:04.790 Using "original" ASCII encoding</div><div>2021-05-28 08:25:04.792 Connecting to host -redacted-</div><div>2021-05-28 08:25:04.870 Sent 102 bytes to server</div><div>2021-05-28 08:25:05.073 Received 0 bytes from server</div><div>2021-05-28 08:25:05.076 XymonProcessRuntimeCheck finished</div><div>2021-05-28 08:25:05.078 Executing XymonProcessExternalData</div><div>2021-05-28 08:25:05.080 No files in C:\Program Files\xymon\tmp, nothing to do</div><div>2021-05-28 08:25:05.082 XymonProcessExternalData finished</div><div>2021-05-28 08:25:05.084 Executing XymonProcessLocalData</div><div>2021-05-28 08:25:05.086 Local data path C:\Program Files\xymon\local does not exist, nothing to do</div><div>2021-05-28 08:25:05.087 XymonProcessLocalData finished</div><div>2021-05-28 08:25:05.117 Main and optional tests finished.</div><div>2021-05-28 08:25:05.121 Sending to server</div><div>2021-05-28 08:25:05.126 Using "original" ASCII encoding</div><div>2021-05-28 08:25:05.129 Connecting to host REDACTED</div><div>2021-05-28 08:25:05.207 Sent 405096 bytes to server</div><div>2021-05-28 08:25:05.594 Received 380 bytes from server</div><div><br></div><div> </div><div><u><b>Here's a chunk of info from the xymonlog for the non-functioning port 443 host.</b></u></div><div>2021-05-28 08:23:29.052 Setting thread/UI culture to en-US</div><div>2021-05-28 08:23:30.630 Resetting thread/UI culture to previous: en-US / en-US</div><div>2021-05-28 08:23:30.630 Event log Security entries since last scan: 234</div><div>2021-05-28 08:23:30.630 Entries to add to payload: 234 </div><div>2021-05-28 08:23:30.630 Payload length reached 2271, greater than 1024</div><div>2021-05-28 08:23:30.646 Event log System adding to payload</div><div>2021-05-28 08:23:30.646 Event log Application adding to payload</div><div>2021-05-28 08:23:30.646 Event log processing finished</div><div>2021-05-28 08:23:30.646 XymonProcs start</div><div>2021-05-28 08:23:30.661 XymonProcs finished.</div><div>2021-05-28 08:23:30.661 XymonNetstat start</div><div>2021-05-28 08:23:30.677 XymonNetstat finished.</div><div>2021-05-28 08:23:30.677 XymonPorts start</div><div>2021-05-28 08:23:30.692 XymonPorts finished.</div><div>2021-05-28 08:23:30.708 XymonIpconfig start</div><div>2021-05-28 08:23:30.724 XymonIpconfig finished.</div><div>2021-05-28 08:23:30.724 XymonRoute start</div><div>2021-05-28 08:23:30.786 XymonRoute finished.</div><div>2021-05-28 08:23:30.802 XymonIfstat start</div><div>2021-05-28 08:23:30.802 wanted address families: InterNetwork</div><div>2021-05-28 08:23:30.817 XymonIfstat finished.</div><div>2021-05-28 08:23:30.817 XymonSvcs start</div><div>2021-05-28 08:23:30.927 XymonSvcs finished.</div><div>2021-05-28 08:23:30.927 XymonWho start</div><div>2021-05-28 08:23:30.927 XymonWho finished.</div><div>2021-05-28 08:23:30.927 XymonUsers start</div><div>2021-05-28 08:23:30.958 XymonUsers finished.</div><div>2021-05-28 08:23:30.958 Executing XymonServiceCheck</div><div>2021-05-28 08:23:30.958 Executing XymonDirSize</div><div>2021-05-28 08:23:30.958 Executing XymonDirTime</div><div>2021-05-28 08:23:30.958 Executing XymonTerminalServicesSessionsCheck</div><div>2021-05-28 08:23:30.958 Executing XymonActiveDirectoryReplicationCheck</div><div>2021-05-28 08:23:30.958 Executing XymonProcessRuntimeCheck</div><div>2021-05-28 08:23:30.974 Sending output for procruntime</div><div>2021-05-28 08:23:30.974 Executing XymonSendViaHttp</div><div>2021-05-28 08:23:30.974 Using url https://REDACTED/xymon-cgi/xymoncgimsg.cgi</div><div>2021-05-28 08:23:30.974 Decrypting serverHttpPassword</div><div>2021-05-28 08:23:30.974 Using username REDACTED</div>2021-05-28 08:23:31.052 Connecting to https://REDACTED/xymon-cgi/xymoncgimsg.cgi, body length 98, timeout 100000ms<div>2021-05-28 08:23:31.349 Received 0 bytes from server</div><div>2021-05-28 08:23:31.364 XymonSendViaHttp finished</div><div>2021-05-28 08:23:31.364 XymonProcessRuntimeCheck finished</div><div>2021-05-28 08:23:31.364 Executing XymonProcessExternalData</div><div>2021-05-28 08:23:31.364 No files in C:\Program Files\xymon\tmp, nothing to do</div><div>2021-05-28 08:23:31.364 XymonProcessExternalData finished</div><div>2021-05-28 08:23:31.364 Executing XymonProcessLocalData</div><div>2021-05-28 08:23:31.364 Local data path C:\Program Files\xymon\local does not exist, nothing to do</div><div>2021-05-28 08:23:31.364 XymonProcessLocalData finished</div><div>2021-05-28 08:23:31.396 Main and optional tests finished.</div><div>2021-05-28 08:23:31.396 Sending to server</div><div>2021-05-28 08:23:31.411 Executing XymonSendViaHttp</div>2021-05-28 08:23:31.411 Using url https://REDACTED/xymon-cgi/xymoncgimsg.cgi<div>2021-05-28 08:23:31.411 Decrypting serverHttpPassword</div><div>2021-05-28 08:23:31.411 Using username REDACTED</div>2021-05-28 08:23:31.442 Connecting to https://REDACTED/xymon-cgi/xymoncgimsg.cgi, body length 86082, timeout 100000ms<div>2021-05-28 08:23:31.739 Received 295 bytes from server</div><div>2021-05-28 08:23:31.739 XymonSendViaHttp finished</div><div><br></div><div><br></div><div><span><pre>-- <br></pre><div style="width: 71ch;">Kris Springer</div><div style="width: 71ch;"><br></div><div style="width: 71ch;"><br></div><div style="width: 71ch;"></div></span></div><div><br></div><div>-----Original Message-----</div><div><b>From</b>: "Beck, Zak" <<a href="mailto:%22Beck,%20Zak%22%20%3czak.beck@accenture.com%3e">zak.beck@accenture.com</a>></div><div><b>To</b>: Jeremy Laidman <<a href="mailto:Jeremy%20Laidman%20%3cjeremy@laidman.org%3e">jeremy@laidman.org</a>>, Kris Springer <<a href="mailto:Kris%20Springer%20%3ckspringer@innovateteam.com%3e">kspringer@innovateteam.com</a>></div><div><b>Cc</b>: Xymon MailingList <<a href="mailto:Xymon%20MailingList%20%3cxymon@xymon.com%3e">xymon@xymon.com</a>></div><div><b>Subject</b>: RE: [External] Re: [Xymon] cpu rrd files not being generated</div><div><b>Date</b>: Thu, 27 May 2021 09:21:16 +0000</div><div><br></div><!-- text/html -->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#034BED;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#034BED;mso-fareast-language:EN-US">Hi<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#034BED;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#034BED;mso-fareast-language:EN-US">There’s no difference in the data sent between TCP / HTTP(S) transport (aside from a flag at the end to indicate whether TCP or HTTP was used).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#034BED;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#034BED;mso-fareast-language:EN-US">You probably know you can look at the xymon-lastcollect.txt log to see what is being sent. This log will get overwritten every time the client sends the data but you can retain and
rotate the last so many versions using <clientlogretain><b>number</b></clientlogretain> in xymonclient_config.xml e.g. <clientlogretain>5</clientlogretain> to keep the last 5 copies, which may be helpful. The client will rotate the files so you should not
run out of space.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#034BED;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#034BED;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#034BED">Zak <br>
<br>
</span><span style="color:#034BED;mso-fareast-language:EN-US"><o:p></o:p></span></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Xymon <xymon-bounces@xymon.com>
<b>On Behalf Of </b>Jeremy Laidman<br>
<b>Sent:</b> 27 May 2021 04:39<br>
<b>To:</b> Kris Springer <kspringer@innovateteam.com><br>
<b>Cc:</b> Xymon MailingList <xymon@xymon.com><br>
<b>Subject:</b> [External] Re: [Xymon] cpu rrd files not being generated<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" align="center" style="text-align:center"><span style="color:#EE0701">This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.</span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#EE0701" align="center">
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">On Thu, 27 May 2021 at 03:16, Kris Springer <<a href="mailto:kspringer@innovateteam.com">kspringer@innovateteam.com</a>> wrote:<o:p></o:p></p>
</div>
<div>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<p class="MsoNormal">I added a new Windows host yesterday and I'm using XymonPSClient v2.41
<br>
and data is coming into server encrypted over port 443. All data seems <br>
to be coming in just fine, and disk/memory/tcp graphs were auto <br>
generated and work fine. But the cpu graph did not generate. I am <br>
receiving the cpu stats but the la.rrd file did not get created. I <br>
cleared the hosts data and let everything auto generate again, but the <br>
same result occurred with no la.rrd file being created. I added 7 more <br>
new hosts all using the same XymonPSClient over port 443 and the same <br>
missing cpu graphs occurred with all of them.<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Firstly, RRD seems to need two consecutive samples to start outputting RRD data in graphs. If it only gets one, it doesn't show the data in graphs. Or something like that. Sometimes you need to give it a bit of time. If a sample is rejected
due to being non-contiguous, I'd expect to see a log message in rrd-data.log or rrd-status.log (depending on the test).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Disk, memory and CPU all originally come from the client data message. So if you're getting data for one of these, you should be getting for all of these.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<p class="MsoNormal">I've got other hosts <br>
using the same PSClient over 443 and they work just fine. Any ideas?<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Same exact version of XymonPSClient?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<p class="MsoNormal">I've looked through all the xymon logs and found no errors. Server
<br>
reboot affected nothing.<br>
<br>
I added a new host using the same XymonPSClient but NOT sending the data <br>
encrypted, just using port 1984, and the cpu graph auto generated <br>
correctly. Can anyone give me a clue?<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Hmm, interesting. I can't think why that would change the behaviour. Unless XymonPSClient behaves differently in this mode.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Check the client data for a working and a non-working host. Compare the "[cpu]" sections and see if there are any discrepancies. You can do this from the command line like so:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> $XYMON $XYMSRV "clientlog <hostname> section=cpu"<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If the output of this command for the two hosts both look similar, there's a good chance that the faulty host's message is being parsed correctly. The status essentially looks for "load=NNNN%" where NNNN is one or more digits. It also expects
to see "CPU states" but that's not mandatory for a successful data message to be created. If so, you should have a CPU status message.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The RRD data parser looks at the status message contents. It essentially looks for the first line to contain "up: " followed (at some point) by ", load=NNNN%" (or load=NN or load=NN.NN for other OSes). Compare the CPU status messages between
the two hosts and see if there are any discrepancies. You can do this from the command line like so:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"> $XYMON $XYMSRV "xymondlog <hostname>.cpu"<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If there is no difference in the structure of these messages, then both should be correctly handled by the RRD parser and the la.rrd file should be created. If this doesn't show any problems, but the la.rrd file still isn't being updated
(double-check using "rrdtool fetch <filename> AVERAGE | tail" or similar), then you might need to run xymond_rrd with the "--debug" flag, and look for helpful output in rrd-status.log.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Cheers<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Jeremy<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by
you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of
internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement
at https://www.accenture.com/us-en/privacy-policy. <br>
______________________________________________________________________________________<br>
<br>
www.accenture.com<br>
</font>
</body></html>