[Xymon] clientconfig.cfg not getting updated

[Colin Coe]

HI Brandon

I appreciate your help with this.

The log file (c:\xymonclient.log) is being written to and I can see
"Using new remote config, saving locally" however the clientconfig.cfg
while the files time stamp updates, the content doesn't change.  I
ended up putting that section of code in a try catch block but no
error was generated.

Doing the XymonSend resulted in the whole file being downloaded being
downloaded from the Xymon server.

I've done the Windows equiv of chmod 777 on the client-local.cfg to
run out permission problems.

It looks

On Tue, Dec 15, 2015 at 1:12 PM, Brandon Dale <BDale at kitchengroup.com.au> wrote:
> It should be writing a log file when it runs c:\xymonclient.log, do you see that log file being written, does it contain any errors?
> And in xymon are you seeing any of the data make it to your xymon server, you should see all the data in the clientlog column.
>
>
> One thing I have done in the past when having issues is use xymonsend from http://sourceforge.net/p/xymon/code/HEAD/tree/sandbox/WinPSClient/xymonsend.ps1  to confirm I can talk to the xymon server. You can dot source this into powershell and run something like
>
> XymonSend "config client-local.cfg" "xymonservername" > c:\temp\client-local.cfg
>
> At least then you can see if you can actually pull down the files on that server or not.
>
> Regards,
>
>
> Brandon
>
>
> -----Original Message-----
> From: Colin Coe [mailto:colin.coe at gmail.com]
> Sent: Tuesday, 15 December 2015 12:59 PM
> To: Brandon Dale
> Cc: xymon at xymon.com
> Subject: Re: [Xymon] clientconfig.cfg not getting updated
>
> Hi Brandon
>
> Thanks for the reply.
>
> Yep, read through the doco a couple of times now trying to get this working.
>
> 1. Yep, c:\program files\xymon\xymonclient_config.xml exists (and
> xymonclient.ps1 is in this directory) and contains:
> ---
> <XymonSettings>
>
>   <servers>xxx.xx.106.11 xxx.xx.176.11</servers>
>
>   <clientlogfile>c:\xymonclient.log</clientlogfile>
>   <clientconfigfile>c:\program files\xymon\clientconfig.cfg</clientconfigfile>
>
>   <clientfqdn>0</clientfqdn>
>   <clientlower>1</clientlower>
>
>   <clientremotecfgexec>1</clientremotecfgexec>
> </XymonSettings>
> ---
>
> 2. On the server (RHEL6.7, Teribithia RPM 4.3.24), /etc/xymon/client-local.cfg contains:
> ---
> [powershell]
> clientversion:2.04:http://http.url.to.file/pub/
> tssessions
> adreplicaton
> ---
>
> I've changed "[os=powershell]" to just "[powershell]" and removed all but the above (for the powershell client)
>
> 3. I've stopped/started the powershell client and waited for a while with no joy.
>
> I've confirmed that the clients can manually download the file.
>
> Not sure what I'm missing here...
>
> Thanks
>
> On Mon, Dec 14, 2015 at 12:30 PM, Brandon Dale <BDale at kitchengroup.com.au> wrote:
>> If you haven't already I would read through http://sourceforge.net/p/xymon/code/HEAD/tree/sandbox/WinPSClient/XymonPSClient.doc it's pretty decent documentation.
>>
>> Try double checking this stuff:
>>
>> 1. Make sure you have copied the .xml file that contains the
>> configuration for the client to the local machine into the same
>> directory where the xymonclient.ps1 script lives
>> http://sourceforge.net/p/xymon/code/HEAD/tree/sandbox/WinPSClient/xymo
>> nclient_config.xml and that this contains a path for the
>> client-local.cfg file and has clientremotecfgexec set to 1 (this is
>> already done by default in the .xml file in that link)
>>
>> 2. Put your settings into the client-local.cfg file on your xymon
>> server, I have put an example below, the valid commands are listed in
>> XymonPSClient.doc
>>
>> [powershell]
>> eventlogswanted:*:250000:warning,critical,error
>> ifstat:ipv4
>> clientversion:2.04:\\somepath\goes\here
>>
>> 3. Wait for or manually run the PowerShell client (by restarting the XymonPSClient Service in windows), you need to do this at least twice as the first time you run it, it will get the commands you have in your client-local.cfg file on your xymon server and write them to the clientconfig.cfg (or whatever you called it in the .xml file) the second time it runs it will start reading it.
>>
>> Note: make sure you read the documentation for the eventlog ignore rules, the syntax is different. You can still use the IGNORE PATTERN but the way you select which eventlogs to check has changed in the powershell client compared to bbwin.
>>
>> Personally I ignore eventlogs in the analysis.cfg on the xymon server rather the in client-local.cfg as you can use regex to match on eventid + Source rather than just the description.
>>
>>
>> Regards,
>>
>>
>> Brandon
>>
>>
>>
>>
>> -----Original Message-----
>> From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Colin Coe
>> Sent: Monday, 14 December 2015 2:48 PM
>> To: xymon at xymon.com
>> Subject: [Xymon] clientconfig.cfg not getting updated
>>
>> Hi all
>>
>> I'm noticing that the Windows Powershell Xymon client isn't being updated to reflect changes in client-local.cfg.  I had thought that changes on the Xymon server to client-local.cfg would result in changes on the Windows clients.  Am I wrong here, and if so, what's the correct way to get these changes propagated out?
>>
>> I'm wanting the following to be pushed out to the clients:
>> ---
>> tail -n 2 /etc/xymon/client-local.cfg
>> [os=powershell]
>> clientversion:2.04:http://benmon1p.scada.horizonpower.com.au/pub/
>> ---
>>
>> clientlocal.cfg contains:
>> ---
>> eventlog:security
>> ignore success
>> ignore Success
>> ignore "The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer"
>> eventlog:system
>> ignore "Contact the administrator to install the driver before you log in again"
>> tssessions
>> adreplicaton
>> ---
>>
>> Thanks
>>
>> CC
>> _______________________________________________
>> Xymon mailing list
>> Xymon at xymon.com
>> http://lists.xymon.com/mailman/listinfo/xymon