cpu rrd files not being generated
I added a new Windows host yesterday and I'm using XymonPSClient v2.41 and data is coming into server encrypted over port 443.? All data seems to be coming in just fine, and disk/memory/tcp graphs were auto generated and work fine.? But the cpu graph did not generate.? I am receiving the cpu stats but the la.rrd file did not get created.? I cleared the hosts data and let everything auto generate again, but the same result occurred with no la.rrd file being created.? I added 7 more new hosts all using the same XymonPSClient over port 443 and the same missing cpu graphs occurred with all of them.? I've got other hosts using the same PSClient over 443 and they work just fine.? Any ideas?
I've looked through all the xymon logs and found no errors.? Server reboot affected nothing.
I added a new host using the same XymonPSClient but NOT sending the data encrypted, just using port 1984, and the cpu graph auto generated correctly.? Can anyone give me a clue?
-- Kris Springer
On Thu, 27 May 2021 at 03:16, Kris Springer <kspringer at innovateteam.com> wrote:
I added a new Windows host yesterday and I'm using XymonPSClient v2.41 and data is coming into server encrypted over port 443. All data seems to be coming in just fine, and disk/memory/tcp graphs were auto generated and work fine. But the cpu graph did not generate. I am receiving the cpu stats but the la.rrd file did not get created. I cleared the hosts data and let everything auto generate again, but the same result occurred with no la.rrd file being created. I added 7 more new hosts all using the same XymonPSClient over port 443 and the same missing cpu graphs occurred with all of them.
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).
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.
I've got other hosts
using the same PSClient over 443 and they work just fine. Any ideas?
Same exact version of XymonPSClient?
I've looked through all the xymon logs and found no errors. Server
reboot affected nothing.
I added a new host using the same XymonPSClient but NOT sending the data encrypted, just using port 1984, and the cpu graph auto generated correctly. Can anyone give me a clue?
Hmm, interesting. I can't think why that would change the behaviour. Unless XymonPSClient behaves differently in this mode.
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:
$XYMON $XYMSRV "clientlog <hostname> section=cpu"
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.
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:
$XYMON $XYMSRV "xymondlog <hostname>.cpu"
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.
Cheers Jeremy
Hi
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).
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>number</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.
Zak
From: Xymon <xymon-bounces at xymon.com> On Behalf Of Jeremy Laidman Sent: 27 May 2021 04:39 To: Kris Springer <kspringer at innovateteam.com> Cc: Xymon MailingList <xymon at xymon.com> Subject: [External] Re: [Xymon] cpu rrd files not being generated
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.
On Thu, 27 May 2021 at 03:16, Kris Springer <kspringer at innovateteam.com<mailto:kspringer at innovateteam.com>> wrote: I added a new Windows host yesterday and I'm using XymonPSClient v2.41 and data is coming into server encrypted over port 443. All data seems to be coming in just fine, and disk/memory/tcp graphs were auto generated and work fine. But the cpu graph did not generate. I am receiving the cpu stats but the la.rrd file did not get created. I cleared the hosts data and let everything auto generate again, but the same result occurred with no la.rrd file being created. I added 7 more new hosts all using the same XymonPSClient over port 443 and the same missing cpu graphs occurred with all of them.
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).
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.
I've got other hosts using the same PSClient over 443 and they work just fine. Any ideas?
Same exact version of XymonPSClient?
I've looked through all the xymon logs and found no errors. Server reboot affected nothing.
I added a new host using the same XymonPSClient but NOT sending the data encrypted, just using port 1984, and the cpu graph auto generated correctly. Can anyone give me a clue?
Hmm, interesting. I can't think why that would change the behaviour. Unless XymonPSClient behaves differently in this mode.
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:
$XYMON $XYMSRV "clientlog <hostname> section=cpu"
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.
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:
$XYMON $XYMSRV "xymondlog <hostname>.cpu"
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.
Cheers Jeremy
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.
www.accenture.com
I updated the XymonPSClient to v2.42 just to make sure that wasn't
the cause. It didn't resolve anything.I checked the rrd folders to make sure there wasn't some duplicate hostname folders or something. There wasn't.
I reviewed the clientlog from both functioning and non-functioning hosts and the cpu data looks the same. Both show load=NN.NN% The difference between them is that the functioning host is 'Win Server 2012 R2 Datacenter' and non-functining one is 'Win Server 2019 Datacenter'. But if the v2019 was the issue then my other 2019 hosts that are sending their data over port 1984 wouldn't be working either?
I ran the $XYMON $XYMSRV "xymondlog <hostname>.cpu" and reviewed the content for both hosts. The content exists and looks the same, other than the non-functioning one has a LOT more of it. I'm starting to think the data might be getting truncated. But the same lack of cpu graphs are happening for 8 new hosts. All other incoming data seems totally fine, just no cpu graphs.
I looked through the 'Xymon client log' and noticed this message.
'Payload length reached 2738, greater than 1024'
I ran into this issue once before long ago when I switched from
BBwin to XymonPSClient. The client data coming into the server was
larger than the default allowed, so it was getting truncated and
causing purple alerts. Server default was 512k, so I increased it
to 1024k and everything has been fine for years. Now it seems with
new Windows servers there's more client data coming in. I'm thinking this may be my current issue, so I just
increase it to 3072k in the xymonserver.cfg file and restarted
Xymon Server. I waited a few cycles and watched the 'Xymon client
log' for the changes to appear. It's still showing the same
'Payload length is greater than 1024' message. I also restarted the
XymonPSClient service on the Windows host and it didn't seem to
resolve anything. What am I missing here? The server should be
allowing larger amounts of client data now.
Kris Springer
On 5/27/21 3:21 AM, Beck, Zak wrote:@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;}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;}div.WordSection1 {page:WordSection1;} Hi 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). 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>number</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. Zak
From: Xymon <xymon-bounces at xymon.com> On Behalf Of Jeremy Laidman Sent: 27 May 2021 04:39 To: Kris Springer <kspringer at innovateteam.com> Cc: Xymon MailingList <xymon at xymon.com> Subject: [External] Re: [Xymon] cpu rrd files not being generated This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments. On Thu, 27 May 2021 at 03:16, Kris Springer <kspringer at innovateteam.com> wrote:I added a new Windows host yesterday and I'm using XymonPSClient v2.41 and data is coming into server encrypted over port 443. All data seems to be coming in just fine, and disk/memory/tcp graphs were auto generated and work fine. But the cpu graph did not generate. I am receiving the cpu stats but the la.rrd file did not get created. I cleared the hosts data and let everything auto generate again, but the same result occurred with no la.rrd file being created. I added 7 more new hosts all using the same XymonPSClient over port 443 and the same missing cpu graphs occurred with all of them.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). 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.I've got other hosts using the same PSClient over 443 and they work just fine. Any ideas?Same exact version of XymonPSClient?I've looked through all the xymon logs and found no errors. Server reboot affected nothing. I added a new host using the same XymonPSClient but NOT sending the data encrypted, just using port 1984, and the cpu graph auto generated correctly. Can anyone give me a clue?Hmm, interesting. I can't think why that would change the behaviour. Unless XymonPSClient behaves differently in this mode. 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: $XYMON $XYMSRV "clientlog <hostname> section=cpu" 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. 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: $XYMON $XYMSRV "xymondlog <hostname>.cpu" 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. Cheers Jeremy 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.
www.accenture.com
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?
Here's a chunk of info from the xymonlog for the functioning port 1984 host.2021-05-28 08:25:01.663 Setting thread/UI culture to en-US2021-05-28 08:25:04.342 Resetting thread/UI culture to previous: en-US / en-US2021-05-28 08:25:04.346 Event log Security entries since last scan: 4552021-05-28 08:25:04.348 Entries to add to payload: 455 2021-05-28 08:25:04.351 Payload length reached 2265, greater than 10242021-05-28 08:25:04.352 Event log System adding to payload2021-05-28 08:25:04.353 Event log Application adding to payload2021-05-28 08:25:04.356 Event log processing finished2021-05-28 08:25:04.357 XymonProcs start2021-05-28 08:25:04.389 XymonProcs finished.2021-05-28 08:25:04.392 XymonNetstat start2021-05-28 08:25:04.415 XymonNetstat finished.2021-05-28 08:25:04.418 XymonPorts start2021-05-28 08:25:04.459 XymonPorts finished.2021-05-28 08:25:04.461 XymonIpconfig start2021-05-28 08:25:04.479 XymonIpconfig finished.2021-05-28 08:25:04.481 XymonRoute start2021-05-28 08:25:04.546 XymonRoute finished.2021-05-28 08:25:04.548 XymonIfstat start2021-05-28 08:25:04.550 wanted address families: InterNetwork2021- 05-28 08:25:04.564 XymonIfstat finished.2021-05-28 08:25:04.566 XymonSvcs start2021-05-28 08:25:04.694 XymonSvcs finished.2021-05-28 08:25:04.746 XymonWho start2021-05-28 08:25:04.748 XymonWho finished.2021-05-28 08:25:04.750 XymonUsers start2021-05-28 08:25:04.773 XymonUsers finished.2021-05-28 08:25:04.775 Executing XymonServiceCheck2021-05-28 08:25:04.777 Executing XymonDirSize2021-05-28 08:25:04.780 Executing XymonDirTime2021-05- 28 08:25:04.781 Executing XymonTerminalServicesSessionsCheck2021-05-28 08:25:04.784 Executing XymonActiveDirectoryReplicationCheck2021-05-28 08:25:04.786 Executing XymonProcessRuntimeCheck2021-05-28 08:25:04.788 Sending output for procruntime2021-05-28 08:25:04.790 Using "original" ASCII encoding2021-05-28 08:25:04.792 Connecting to host -redacted-2021-05-28 08:25:04.870 Sent 102 bytes to server2021-05-28 08:25:05.073 Received 0 bytes from server2021-05-28 08:25:05.076 XymonProcessRuntimeCheck finished2021-05-28 08:25:05.078 Executing XymonProcessExternalData2021-05-28 08:25:05.080 No files in C:\Program Files\xymon\tmp, nothing to do2021-05-28 08:25:05.082 XymonProcessExternalData finished2021-05-28 08:25:05.084 Executing XymonProcessLocalData2021-05-28 08:25:05.086 Local data path C:\Program Files\xymon\local does not exist, nothing to do2021-05-28 08:25:05.087 XymonProcessLocalData finished2021-05-28 08:25:05.117 Main and optional tests finished.2021- 05-28 08:25:05.121 Sending to server2021-05-28 08:25:05.126 Using "original" ASCII encoding2021-05-28 08:25:05.129 Connecting to host REDACTED2021-05-28 08:25:05.207 Sent 405096 bytes to server2021-05-28 08:25:05.594 Received 380 bytes from server Here's a chunk of info from the xymonlog for the non-functioning port 443 host.2021-05-28 08:23:29.052 Setting thread/UI culture to en-US2021-05-28 08:23:30.630 Resetting thread/UI culture to previous: en-US / en-US2021-05-28 08:23:30.630 Event log Security entries since last scan: 2342021-05-28 08:23:30.630 Entries to add to payload: 234 2021-05-28 08:23:30.630 Payload length reached 2271, greater than 10242021-05-28 08:23:30.646 Event log System adding to payload2021-05-28 08:23:30.646 Event log Application adding to payload2021-05-28 08:23:30.646 Event log processing finished2021-05-28 08:23:30.646 XymonProcs start2021-05-28 08:23:30.661 XymonProcs finished.2021-05-28 08:23:30.661 XymonNetstat start2021-05-28 08:23:30.677 XymonNetstat finished.2021-05-28 08:23:30.677 XymonPorts start2021-05-28 08:23:30.692 XymonPorts finished.2021-05-28 08:23:30.708 XymonIpconfig start2021-05-28 08:23:30.724 XymonIpconfig finished.2021-05-28 08:23:30.724 XymonRoute start2021-05-28 08:23:30.786 XymonRoute finished.2021-05-28 08:23:30.802 XymonIfstat start2021-05-28 08:23:30.802 wanted address families: InterNetwork2021- 05-28 08:23:30.817 XymonIfstat finished.2021-05-28 08:23:30.817 XymonSvcs start2021-05-28 08:23:30.927 XymonSvcs finished.2021-05-28 08:23:30.927 XymonWho start2021-05-28 08:23:30.927 XymonWho finished.2021-05-28 08:23:30.927 XymonUsers start2021-05-28 08:23:30.958 XymonUsers finished.2021-05-28 08:23:30.958 Executing XymonServiceCheck2021-05-28 08:23:30.958 Executing XymonDirSize2021-05-28 08:23:30.958 Executing XymonDirTime2021-05- 28 08:23:30.958 Executing XymonTerminalServicesSessionsCheck2021-05-28 08:23:30.958 Executing XymonActiveDirectoryReplicationCheck2021-05-28 08:23:30.958 Executing XymonProcessRuntimeCheck2021-05-28 08:23:30.974 Sending output for procruntime2021-05-28 08:23:30.974 Executing XymonSendViaHttp2021-05-28 08:23:30.974 Using url https://REDACTED/xymon-cgi/xymoncgimsg.cgi2021-05-28 08:23:30.974 Decrypting serverHttpPassword2021-05-28 08:23:30.974 Using username REDACTED2021-05-28 08:23:31.052 Connecting to https://REDACTED/xymon-cgi/xymoncgimsg.cgi, body length 98, timeout 100000ms2021-05-28 08:23:31.349 Received 0 bytes from server2021-05-28 08:23:31.364 XymonSendViaHttp finished2021-05-28 08:23:31.364 XymonProcessRuntimeCheck finished2021-05-28 08:23:31.364 Executing XymonProcessExternalData2021-05-28 08:23:31.364 No files in C:\Program Files\xymon\tmp, nothing to do2021-05-28 08:23:31.364 XymonProcessExternalData finished2021-05-28 08:23:31.364 Executing XymonProcessLocalData2021-05-28 08:23:31.364 Local data path C:\Program Files\xymon\local does not exist, nothing to do2021-05-28 08:23:31.364 XymonProcessLocalData finished2021-05-28 08:23:31.396 Main and optional tests finished.2021-05-28 08:23:31.396 Sending to server2021-05-28 08:23:31.411 Executing XymonSendViaHttp2021-05-28 08:23:31.411 Using url https://REDACTED/xymon-cgi/xymoncgimsg.cgi2021-05-28 08:23:31.411 Decrypting serverHttpPassword2021-05-28 08:23:31.411 Using username REDACTED2021-05-28 08:23:31.442 Connecting to https://REDACTED/xymon-cgi/xymoncgimsg.cgi, body length 86082, timeout 100000ms2021-05-28 08:23:31.739 Received 295 bytes from server2021-05-28 08:23:31.739 XymonSendViaHttp finished
-----Original Message-----From: "Beck, Zak" <zak.beck at accenture.com>To: Jeremy Laidman <jeremy at laidman.org>, Kris Springer <kspringer at innovateteam.com>Cc: Xymon MailingList <xymon at xymon.com>Subject: RE: [External] Re: [Xymon] cpu rrd files not being generatedDate: Thu, 27 May 2021 09:21:16 +0000
<!-- /* 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;} -->
Hi
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).
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>number</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.
Zak
From: Xymon <xymon-bounces at xymon.com> On Behalf Of Jeremy Laidman
Sent: 27 May 2021 04:39
To: Kris Springer <kspringer at innovateteam.com>
Cc: Xymon MailingList <xymon at xymon.com>
Subject: [External] Re: [Xymon] cpu rrd files not being generated
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.
On Thu, 27 May 2021 at 03:16, Kris Springer <kspringer at innovateteam.com> wrote:
I added a new Windows host yesterday and I'm using XymonPSClient v2.41
and data is coming into server encrypted over port 443. All data seems
to be coming in just fine, and disk/memory/tcp graphs were auto
generated and work fine. But the cpu graph did not generate. I am
receiving the cpu stats but the la.rrd file did not get created. I
cleared the hosts data and let everything auto generate again, but the
same result occurred with no la.rrd file being created. I added 7 more
new hosts all using the same XymonPSClient over port 443 and the same
missing cpu graphs occurred with all of them.
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).
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.
I've got other hosts
using the same PSClient over 443 and they work just fine. Any ideas?
Same exact version of XymonPSClient?
I've looked through all the xymon logs and found no errors. Server
reboot affected nothing.
I added a new host using the same XymonPSClient but NOT sending the data
encrypted, just using port 1984, and the cpu graph auto generated
correctly. Can anyone give me a clue?
Hmm, interesting. I can't think why that would change the behaviour. Unless XymonPSClient behaves differently in this mode.
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:
$XYMON $XYMSRV "clientlog <hostname> section=cpu"
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.
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:
$XYMON $XYMSRV "xymondlog <hostname>.cpu"
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.
Cheers
Jeremy
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.
www.accenture.com
-- Kris Springer
When I have had issues with rrd files not being created/updated, it has sometimes been caused by confusion over the? hostname/fqdn or even simply the case of the hostname.? It might be worth checking whether $XYMONRRDS contains multiple directory candidates for your new host.
-- Andy
On 26/05/2021 18:16, Kris Springer wrote:
I added a new Windows host yesterday and I'm using XymonPSClient v2.41 and data is coming into server encrypted over port 443.? All data seems to be coming in just fine, and disk/memory/tcp graphs were auto generated and work fine.? But the cpu graph did not generate.? I am receiving the cpu stats but the la.rrd file did not get created.? I cleared the hosts data and let everything auto generate again, but the same result occurred with no la.rrd file being created.? I added 7 more new hosts all using the same XymonPSClient over port 443 and the same missing cpu graphs occurred with all of them.? I've got other hosts using the same PSClient over 443 and they work just fine.? Any ideas?
I've looked through all the xymon logs and found no errors. Server reboot affected nothing.
I added a new host using the same XymonPSClient but NOT sending the data encrypted, just using port 1984, and the cpu graph auto generated correctly.? Can anyone give me a clue?
participants (4)
-
a.b.smith＠shadymint.com
-
jeremy＠laidman.org
-
kspringer＠innovateteam.com
-
zak.beck＠accenture.com