[Xymon] XymonPSclient

Wed Nov 5 13:05:37 CET 2014

Greg,

I really hope your company will to allow you to share your improvements.  It would really help the Xymon community.  I have no experience with powershell or I would try it myself.

In the meantime I started working on a script that will report what it can gather from SNMP polling, in case you’re not able to share your efforts.  It can’t do nearly as much as a client, but it can get the basics like procs, load, uptime, disk space, etc.  I will be sharing it when I finish.

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Gregory DeCecco
Sent: Tuesday, November 04, 2014 6:41 PM
To: xymon at xymon.com
Subject: Re: [Xymon] XymonPSclient

Scot,

I've had a chance to go through the PS client in a semi-thorough manor and have decided that it is not supportable in our enterprise environment.  Therefore, I and one or two other developers/admins I work with will be restructuring, rewriting the PS client for internal use.  Our bosses have engaged our legal teams about the possibility of releasing our version of the client back to the community.

I can tell you that we have identified several inefficient methods of data collection in the existing PS client and have re-engineered them.  They run much faster now.

Greg DeCecco

Sent from my iPhone

On Nov 4, 2014, at 6:25 PM, "Phil Crooker" <Phil.Crooker at orix.com.au<mailto:Phil.Crooker at orix.com.au>> wrote:

I don't know the PS client at all, but if you consider that the client is accessing quite a bit of system info, including event logs I presume, and considering how poorly PS performs (compared to Linux/Unix equivalents - I know, they aren't equivalent, but...), the CPU use is not surprising. We have had the same issue with BBWin (on virtual machines) - the systems became actually unresponsive for brief periods when BBWin was collecting its data - and had to add a second CPU. These montiors do collect a lot.

BBWin is a dinosaur but it mostly gets the (simple monitoring) job done. We still have to look out for when it mysteriously dies on win 2012 and restart it - no fix for this as I understand.

________________________________
From: Xymon <xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com>> on behalf of Scot Kreienkamp <SKreien at la-z-boy.com<mailto:SKreien at la-z-boy.com>>
Sent: Wednesday, 5 November 2014 5:55 AM
To: Gregory DeCecco; xymon at xymon.com<mailto:xymon at xymon.com>
Subject: Re: [Xymon] XymonPSclient

Thanks for the recommendation Greg.

When I loaded the PowerGUI it would not let me run the powershell client, it keeps returning errors about "execution of scripts is disabled on this system" despite trying unrestricted, bypass, etc, and confirming with get-executionpolicy that those settings were indeed set correctly.   Never did figure that one out.

I did finally get it to work running it from a powershell command line.  On an otherwise Idle system the powershell client was taking 30-40% of CPU for 2-3 minutes at a time.  That's too heavy of an impact to justify putting any effort into it.

BBWin is really showing issues with the newer versions of windows, it's getting hard to monitor windows clients anymore.

Scot Kreienkamp

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Gregory DeCecco
Sent: Tuesday, November 04, 2014 6:49 AM
To: xymon at xymon.com<mailto:xymon at xymon.com>
Subject: Re: [Xymon] XymonPSclient

Scott,

The first thing I would do if I were in your position is make sure the client machine is listed in the hosts config file on the xymon server.  Then I would restart the xymond service to force it to reread the hosts config file.  Next, I would load up PowerGUI (a free PowerShell editor) and open the xymon PowerShell client.  Scroll down to the bottom of he file and find the lines of code that will build the string of report data that will be uploaded to the xymon server.  Also find the function call that uploads the data to xymon.  Set breakpoints that allow you to pause the execution of the code and make sure the report string is populated with valid data.  Also step line-by-line through the uploading process and keep an eye open for any errors that might get thrown.

This is as far as I can take you without actually being there and seeing what happens.

Greg DeCecco

On Nov 3, 2014, at 4:12 PM, "Scot Kreienkamp" <SKreien at la-z-boy.com<mailto:SKreien at la-z-boy.com>> wrote:
Hey everyone,

I'm trying out the PS client again after using it 1-2 years ago and it causing too many problems.  I'm hoping the impact on the clients will have been lessened since I tried it last.

I have the PS client installed and configured, but I never show any connection to the xymon server while monitoring with tcpdump.  Also, I never get any files created in the temp directory.  Here's the dump of the config below:

PS C:\Xymon> .\xymonclient.ps1 config
XymonPSClient config:

servers      : xymon.internal.hq
loopinterval : 60
maxlogage    : 30
clientlower  : 1

Settable Params and values:
    clientbbwinmembug=1
    clientconfigfile=C:\Users\skreien\AppData\Local\Temp\xymonconfig.cfg
    clientfqdn=1
    clientlogfile=C:\Users\skreien\AppData\Local\Temp\xymonclient.log
    clientlower=1
    clientname=corpvskreien.na.lzb.hq
    clientremotecfgexec=0
    loopinterval=60
    maxlogage=30
    reportevt=1
    servers= xymon.internal.hq
    slowscanrate=72
    wanteddisks=3
    wantedlogs=Application System Security

The Xymon server is running as it is receiving messages from hundreds of other clients.  This is an internal only server so iptables is off, Windows firewall is off, and I can successfully telnet from the client to the Xymon server port so there is nothing standing in the way.

The server is Redhat 5.5, client is Win7.  Any ideas?

Scot Kreienkamp

This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
_______________________________________________
Xymon mailing list
Xymon at xymon.com<mailto:Xymon at xymon.com>
http://lists.xymon.com/mailman/listinfo/xymon
_______________________________________________
Xymon mailing list
Xymon at xymon.com<mailto:Xymon at xymon.com>
http://lists.xymon.com/mailman/listinfo/xymon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20141105/ee6635ec/attachment.html>