<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">Likely the URL is not accessible from the box. Try to use the bb:// version to pick up file from xymon/download folder. I had issues a few weeks ago on one of my networks reaching any HTTP sites, but the bb:// uses TCP port 1984 directly off Xymon server..</div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small"><span style="font-family:Arial,"Segoe UI",Corbel,Verdana,Arial,Helvetica,sans-serif;font-size:14px">clientversion:2.37:bb://</span> <br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">Tim Williams</div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 20, 2019 at 11:55 AM Kris Springer <<a href="mailto:kspringer@innovateteam.com" target="_blank">kspringer@innovateteam.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
I left it running overnight to see if the slowscan was the issue,
but the cycle has passed more than once now. The current log said
it was on collection 36 of 72. <br>
<br>
I just restarted the service, waited 15 minutes to let things cycle
a few times, but still no update is occurring.<br>
<br>
Here's the last few lines of the xymonclient.log<br>
<br>
-----------------------------<br>
2019-02-20 08:48:16 Connecting to host 10.0.0.55<br>
2019-02-20 08:48:16 Sent 84667 bytes to server<br>
2019-02-20 08:48:16 Received 101 bytes from server<br>
2019-02-20 08:48:16 RepeatTests: nothing to do!<br>
2019-02-20 08:48:16 Using new remote config, saving locally<br>
2019-02-20 08:48:16 Found a command:
clientversion:2.37:<a class="gmail-m_-4913810713416834949gmail-m_5700232140579474004moz-txt-link-freetext" href="https://redacted.com/xymon/scripts%7CMD5%7Ca438ab32188505438e41444558578477" target="_blank">https://redacted.com/xymon/scripts|MD5|a438ab32188505438e41444558578477</a><br>
2019-02-20 08:48:16 Cached config now contains: <br>
2019-02-20 08:48:16
clientversion:2.37:<a class="gmail-m_-4913810713416834949gmail-m_5700232140579474004moz-txt-link-freetext" href="https://redacted.com/xymon/scripts%7CMD5%7Ca438ab32188505438e41444558578477" target="_blank">https://redacted.com/xymon/scripts|MD5|a438ab32188505438e41444558578477</a><br>
2019-02-20 08:48:16 XymonLogSend: nothing to do!<br>
2019-02-20 08:48:16 Delaying until next run: 295.3749488 seconds<br>
-----------------------------<br>
<br>
<pre class="gmail-m_-4913810713416834949gmail-m_5700232140579474004moz-signature" cols="72">Kris Springer
</pre>
<div class="gmail-m_-4913810713416834949gmail-m_5700232140579474004moz-cite-prefix">On 2/20/19 8:58 AM, Beck, Zak wrote:<br>
</div>
<blockquote type="cite">
<div class="gmail-m_-4913810713416834949gmail-m_5700232140579474004WordSection1">
<p class="MsoNormal"><span>Hi</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>The client only updates on slowscans
– usually every 6 hours – one of first lines in the logs
will tell which scan number you are on and which will be the
next slow scan.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>You can force a slow scan by
stop/starting the service.
</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>If you have waited more than 6 hours,
then you have some other issue – can you check the log on a
slow scan? Usually easiest to do this by stopping the
service and then running the client manually in a Powershell
prompt.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Cheers</span></p>
<p class="MsoNormal"><span> </span></p>
<div>
<p class="MsoNormal"><span>Zak </span></p>
</div>
<p class="MsoNormal"><span> </span></p>
<div>
<div>
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Kris Springer
<a class="gmail-m_-4913810713416834949gmail-m_5700232140579474004moz-txt-link-rfc2396E" href="mailto:kspringer@innovateteam.com" target="_blank"><kspringer@innovateteam.com></a>
<br>
<b>Sent:</b> Wednesday, 20 February 2019 15:39<br>
<b>To:</b> Beck, Zak <a class="gmail-m_-4913810713416834949gmail-m_5700232140579474004moz-txt-link-rfc2396E" href="mailto:zak.beck@accenture.com" target="_blank"><zak.beck@accenture.com></a>;
Xymon MailingList <a class="gmail-m_-4913810713416834949gmail-m_5700232140579474004moz-txt-link-rfc2396E" href="mailto:xymon@xymon.com" target="_blank"><xymon@xymon.com></a><br>
<b>Subject:</b> [External] Re: [Xymon] Windows
XymonPSClient v2.37</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><span>This message is from an EXTERNAL
SENDER - be CAUTIOUS, particularly with links and
attachments.</span></p>
<div class="MsoNormal">
<hr width="100%">
</div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal">I'm trying to remotely update a v2.28
client to the latest 2.37 version by following the
instructions in the XymonPSClient.doc, but the client isn't
updating. Here's what I've done. Maybe I'm missing
something.<br>
<br>
1. Download the latest xymonclient.ps1 from github and place
it in my server's scripts directory. (This is the directory
where I run other client scripts successfully)<br>
<br>
2. Rename the xymonclient.ps1 file to xymonclient_2.37.ps1
(per the doc instructions)<br>
<br>
3. Get the md5sum of the file<br>
<br>
4. Add the following line to the client-local.cfg file on the
server for the specific host I'm trying to update. (per the
doc instructions)<br>
clientversion:2.37:<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__my.domain.com_xymon_scripts-3AMD5-3Amd5sumadlkfskdkfkfdl&d=DwMD-g&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=S-aLwpx-PHBTBMIG_c2JczRC0SfuZCmsiH9Iams25FI&m=nCeHIt-8vEpIrED5Cu3dEPfxpWypoQE_ddD6QQAX9Ws&s=05m99yiMkc-55R1AKXecttl5doV-7QYCPGCbqVr5S_s&e=" target="_blank">https://my.domain.com/xymon/scripts:MD5:md5sumadlkfskdkfkfdl</a><br>
<br>
5. Check that the xymonclient_config.xml on the client has <br>
<clientremotecfgexec>1</clientremotecfgexec><br>
<br>
When I look at the logs on the client it says it sees the
instruction from the server, but it doesn't perform any
action. The client version never changes.<br>
<br>
<br>
</p>
<pre>Kris Springer</pre>
<pre> </pre>
<pre> </pre>
<pre> </pre>
<pre>------------------------------------------</pre>
<pre> </pre>
<div>
<p class="MsoNormal">On 2/15/19 5:03 AM, Beck, Zak wrote:</p>
</div>
<blockquote>
<div>
<p class="MsoNormal">Hi</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I have committed v2.37 today, this has
a big performance related fix and other fixes – thanks to
SebA <<a href="mailto:spah@syntec.co.uk" target="_blank">spah@syntec.co.uk</a>> and
Andy
<a href="mailto:abs@shadymint.com" target="_blank">abs@shadymint.com</a>
for extra work and prompting in this area.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_p_xymon_code_HEAD_tree_sandbox_WinPSClient_&d=DwMD-g&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=S-aLwpx-PHBTBMIG_c2JczRC0SfuZCmsiH9Iams25FI&m=nCeHIt-8vEpIrED5Cu3dEPfxpWypoQE_ddD6QQAX9Ws&s=L-dhmcu_CM75-ARQ7kmDxV7wP_abxGZqOuUDmZXC-RE&e=" target="_blank">Download from SVN</a> (the
documentation has been updated also, including uninstall
instructions).</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">The key fixes are:</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">* replaced WMI call to get number of
processors with Windows API call</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">The WMI call to get processor
information was taking anything from 4-5 seconds on most
of my VMs, some experience much longer waits and high CPU
usage while this WMI call executed. There have also been
instances where the WMI call returns incorrect data or no
data. This has been replaced with a call to
GetNativeSystemInfo(), which should work on 32-bit and
64-bit platforms and in testing executes in milliseconds.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">* only supply diskpart data if
EnableDiskPart = 1</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">There is a test in the client which
uses ‘diskpart’ to gather information about clustering
every slow scan. This is included in the data sent to
Xymon, but it’s not generally displayed – you can extract
it for reporting if needed. Hardly anyone uses this and
for some reason for some people it is causing memory
issues in the Microsoft Virtual Disk Service. Therefore by
default the test will now not be run, you can enable it
with the EnableDiskPart setting in xymonclient_config.xml.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">* add a dummy, ignored config item in
the internal client-local config table so that there is
always some configuration present (even if nothing in the
server-side client-local for this host)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">We found that if there is no
client-local.cfg for the host and no default
client-local.cfg (like [powershell] or [XymonPS]), on some
platforms there appears to be a memory leak. The fix
ensures there is always something in the internal cache of
client-config even if nothing is received from the server.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">* XymonAcceptUTF8 - default (0) is now
to use the original ASCII encoding, added setting for
'pure' ASCII coding which strips/converts diacritic
characters</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Prior to this version, by default, the
client uses ASCII encoding to send to the server but also
attempts to encode/filter diacritic characters. This was
added in v2.20, and for some people it adds a large time
overhead when sending data.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">It’s been changed so that the default
setting of 0 acts like it did before v2.20 – no diacritic
encoding – I’m calling this ‘original’ ASCII encoding.
XymonAcceptUTF8 = 1 is unchanged, uses UTF8.
XymonAcceptUTF8 = 2 is the v2.20 setting, use ASCII and
encode/filter diacritics – I’m calling this ‘pure’ ASCII
encoding. I don’t think this will impact on many people
other than saving time/cpu for the default setting.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Full changelog:</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">v2.37</p>
<p class="MsoNormal">* replaced WMI call to get number of
processors with Windows API call</p>
<p class="MsoNormal">* fixed servicecheck parentheses</p>
<p class="MsoNormal">* use TLS for uploading data to
xymoncgi if using http reporting and URL begins https</p>
<p class="MsoNormal">* add milliseconds to log timestamp</p>
<p class="MsoNormal">* add a dummy, ignored config item in
the internal client-local config table so that there is
always some configuration present (even if nothing in the
server-side client-local for this host)</p>
<p class="MsoNormal">* fix a couple of instances where we
were using variables before they are assigned</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">settings changes/additions:</p>
<p class="MsoNormal">* XymonAcceptUTF8 - default (0) is now
to use the original ASCII encoding, added setting for
'pure' ASCII coding which strips/converts diacritic
characters</p>
<p class="MsoNormal">* only supply diskpart data if
EnableDiskPart = 1</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Zak
</p>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal"> </p>
<div class="MsoNormal">
<hr width="100%">
</div>
<p class="MsoNormal"><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 <a href="https://www.accenture.com/us-en/privacy-policy" target="_blank">https://www.accenture.com/us-en/privacy-policy</a>.
<br>
______________________________________________________________________________________<br>
<br>
<a href="http://www.accenture.com" target="_blank">www.accenture.com</a><br>
<br>
<br>
</p>
<pre>_______________________________________________</pre>
<pre> </pre>
<pre>Xymon mailing list</pre>
<pre> </pre>
<pre><a href="mailto:Xymon@xymon.com" target="_blank">Xymon@xymon.com</a></pre>
<pre> </pre>
<pre><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.xymon.com_mailman_listinfo_xymon&d=DwMD-g&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=S-aLwpx-PHBTBMIG_c2JczRC0SfuZCmsiH9Iams25FI&m=nCeHIt-8vEpIrED5Cu3dEPfxpWypoQE_ddD6QQAX9Ws&s=dlri1VGEnUrfF1SmKT2_B0vclSkFM--ZA8iIjLbfCtk&e=" target="_blank">http://lists.xymon.com/mailman/listinfo/xymon</a></pre>
<pre> </pre>
</blockquote>
<p class="MsoNormal"> </p>
</div>
</blockquote>
<br>
</div>
_______________________________________________<br>
Xymon mailing list<br>
<a href="mailto:Xymon@xymon.com" target="_blank">Xymon@xymon.com</a><br>
<a href="http://lists.xymon.com/mailman/listinfo/xymon" rel="noreferrer" target="_blank">http://lists.xymon.com/mailman/listinfo/xymon</a><br>
</blockquote></div>