<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">Thanks! So for us it is just the bb:// which points to the default /download folder. It works!<br clear="all"></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small">We may make a XymonPS subfolder down the road.</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</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 6, 2019 at 12:43 PM Andy Smith <<a href="mailto:abs@shadymint.com">abs@shadymint.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">All,<br>
<br>
Spot on Zak, we use the bb:// urls for our upgrades, we have ~xymon/server/download/XymonPS/ populated with for example xymonclient_2.28.ps1<br>
<br>
and the client configured with lines such as :-<br>
<br>
clientversion:2.28:bb://XymonPS:SHA1:0737ef113b23f1994c21495e678eaa04bfd1e1c7<br>
<br>
-- <br>
Andy<br>
<br>
On Wed, Feb 06, 2019 at 05:15:40PM +0000, Beck, Zak wrote:<br>
> <br>
> I???d forgotten we added bb:// style urls, I must admit I don???t use them regularly.<br>
> <br>
> From the server side, the manpage<<a href="https://www.xymon.com/help/manpages/man1/xymon.1.html" rel="noreferrer" target="_blank">https://www.xymon.com/help/manpages/man1/xymon.1.html</a>> says:<br>
> <br>
> download FILENAME<br>
> Download a file from the Xymon server???s download directory.<br>
> <br>
> Looking at the xymond code (I???m hoping this is the right place):<br>
> <br>
> sprintf(fullfn, "%s/download/%s", xgetenv("XYMONHOME"), fn)<br>
> <br>
> so I think the download directory should be under your XYMONHOME and the path in the bb: url is relative to that.<br>
> <br>
> You will not be able to download from an absolute path per your config currently. I guess you might want to create an updates directory e.g. $XYMONHOME/download/updates/, put your new client files there and your bb url will be bb://updates.<br>
> <br>
> Zak<br>
> <br>
> <br>
> From: Xymon <<a href="mailto:xymon-bounces@xymon.com" target="_blank">xymon-bounces@xymon.com</a>> On Behalf Of Timothy Williams<br>
> Sent: Wednesday, 6 February 2019 16:54<br>
> To: <a href="mailto:xymon@xymon.com" target="_blank">xymon@xymon.com</a><br>
> Subject: [External] [Xymon] XymonPS upgrade source<br>
> <br>
> In our main 'regular' server environment we have a web server that holds the newest XymonPS client for successful self-upgrading on slow scan. However, in our restrictive PCI environment, the Windows servers are not permitted to access the outside web folder or even other servers in the environment excepting WSUS, antivirus, etc on specific ports. They do send and receive files on port 1984 to Xymon server.<br>
> <br>
> 2019-02-05 14:11:23 Main and optional tests finished.<br>
> 2019-02-05 14:11:23 Sending to server<br>
> 2019-02-05 14:11:23 Using UTF8 encoding<br>
> 2019-02-05 14:11:23 Connecting to host 192.168.47.233<br>
> 2019-02-05 14:11:23 Sent 69413 bytes to server<br>
> 2019-02-05 14:11:23 Received 107 bytes from server<br>
> <br>
> I have tried to use the bb: pseudo-URL to access the download folder on the Xymon (3.28) Linux server. World Read permissions have been verified. From the client logs, it appears to find the file and initiates a download, but the new file has zero bytes. The upgrade process continues to restart the service, but obviously hangs as there is now no script file. I have tried both ASCII and UTF8 encoding.<br>
> <br>
> 2019-02-05 14:11:23 Found a command: clientversion:2.35:bb://usr/local/xymon/server/download<br>
> ..<br>
> 2019-02-05 14:11:23 Executing XymonCheckUpdate<br>
> 2019-02-05 14:11:24 Running version 2.28; config version 2.35; attempting upgrade<br>
> 2019-02-05 14:11:24 XymonDownloadFromServer - Downloading usr/local/xymon/server/download/xymonclient_2.35.ps1 to C:\Utils\xymonclient_2.35.ps1<br>
> 2019-02-05 14:11:24 Using UTF8 encoding<br>
> 2019-02-05 14:11:24 Connecting to host 192.168.47.233<br>
> 2019-02-05 14:11:24 Sent 62 bytes to server<br>
> 2019-02-05 14:11:24 Wrote 0 bytes from server to C:\Utils\xymonclient_2.35.ps1<br>
> 2019-02-05 14:11:24 Launching update<br>
> 2019-02-05 14:11:24 Upgrading C:\Utils\xymonclient.ps1 to C:\Utils\xymonclient_2.35.ps1<br>
> 2019-02-05 14:11:24 Restarting service...<br>
> <br>
> The error message on the XymonD process indicates that the file was not found.<br>
> <br>
> Latest error messages:<br>
> Download file usr/local/xymon/server/xymonclient_2.35.ps1 not found<br>
> <br>
> Anybody have ideas about where the fault lies? Using file share or https is beyond where InfoSec wants to go. We currently manually copy in new clients to each PCI server, I'd like to have self-upgrading working.<br>
> <br>
> Tim Williams<br>
> Virginia Commonwealth University Computer Center<br>
</blockquote></div>