[Xymon] Windows PS xymonclient

Kris Springer kspringer at innovateteam.com
Wed Feb 20 22:33:32 CET 2019


I recall having purple issues when I moved from BBwin to the PSclient.  
I upped our acceptable size to 1024 and haven't had issues since.

Kris Springer


On 2/20/19 2:23 PM, Timothy Williams wrote:
> On the problem machines, check the xymonclient.log file on the server, 
> or in console if you load it up. Check the size of the data file. We 
> had to go to 1024.
>
> 2019-02-20 16:16:58  Sending to server
> 2019-02-20 16:16:58  Using ASCII encoding
> 2019-02-20 16:16:59  Connecting to host
> 2019-02-20 16:16:59  Sent 101438 bytes to server
> 2019-02-20 16:17:00  Received 436 bytes from server
>
> Tim
>
>
> On Wed, Feb 20, 2019 at 4:18 PM Root, Paul T 
> <Paul.Root at centurylink.com <mailto:Paul.Root at centurylink.com>> wrote:
>
>     Thanks.I was on github, it’s only up to 2.34.
>
>     So I upped my MAXMSG_DATA, and MAXMSG_STATUS to 768. It was 648.
>     That cleared up the cisco ASA through devmon. But didn’t help
>     here. So my xymond test for the server is now green.
>
>     A 3^rd machine dropped to red, but came green again, about the
>     time I increased the message sizes. So maybe that’s something.
>
>     Dropping down to 2.28 didn’t help. Ports is still empty. As is who.
>
>     I’ll give 2.37 a try.
>
>     *From:*Kris Springer <kspringer at innovateteam.com
>     <mailto:kspringer at innovateteam.com>>
>     *Sent:* Wednesday, February 20, 2019 2:40 PM
>     *To:* Root, Paul T <Paul.Root at CenturyLink.com>
>     *Cc:* xymon at xymon.com <mailto:xymon at xymon.com>
>     *Subject:* Re: [Xymon] Windows PS xymonclient
>
>     Here's the download location of the latest XymonPSclient.
>     https://sourceforge.net/p/xymon/code/HEAD/tree/sandbox/WinPSClient/
>
>
>     Kris Springer
>
>     On 2/20/19 11:55 AM, Root, Paul T wrote:
>
>         Nope, 2.34. That was what was on github, or where ever it was
>         that I got it.
>
>         I’m not a developer, and don’t really get how to use git.  I
>         poked and prodded until I got the file.
>
>         I’ll try to find 2.28 and try it on those 2 machines.
>
>         *From:* SebA <spah at syntec.co.uk> <mailto:spah at syntec.co.uk>
>         *Sent:* Wednesday, February 20, 2019 12:10 PM
>         *To:* Root, Paul T <Paul.Root at CenturyLink.com>
>         <mailto:Paul.Root at CenturyLink.com>
>         *Cc:* Kris Springer <kspringer at innovateteam.com>
>         <mailto:kspringer at innovateteam.com>; xymon at xymon.com
>         <mailto:xymon at xymon.com>
>         *Subject:* Re: [Xymon] Windows PS xymonclient
>
>         Hi Paul,
>
>         Do you mean v2.37 (that's the latest)?  If so, I had the same
>         issue on one of our servers.  Downgrading to v2.28 fixed it,
>         restarting the new version fixed it multiple times for just
>         the 1st cycle, I got it working in a powershell admin prompt
>         (running for at least an hour), then closed it and restarted
>         the service on the new version, and it's been fine since
>         then!  I'm not touching it now!  ;-)
>
>         Clutching at straws a little bit, but I wonder if it might be
>         related to not much memory being available. On the first run,
>         it's using less memory so it works...  (We have a process
>         hogging almost all the RAM on that server.)
>
>         BTW, the empty sections I was getting are:
>
>         [netstat]
>         [ports]
>         [ipconfig]
>         [route]
>
>         Kind regards,
>
>         SebA
>
>         On Wed, 20 Feb 2019 at 18:06, Root, Paul T
>         <Paul.Root at centurylink.com <mailto:Paul.Root at centurylink.com>>
>         wrote:
>
>             Old version was 2.19, not 2.18.
>
>             I put it back in on one of the machines and ports and who
>             are back to normal.
>
>             *From:* Xymon <xymon-bounces at xymon.com
>             <mailto:xymon-bounces at xymon.com>> *On Behalf Of *Root, Paul T
>             *Sent:* Wednesday, February 20, 2019 12:03 PM
>             *To:* 'Kris Springer' <kspringer at innovateteam.com
>             <mailto:kspringer at innovateteam.com>>; xymon at xymon.com
>             <mailto:xymon at xymon.com>
>             *Subject:* Re: [Xymon] Windows PS xymonclient
>
>             Thanks Kris,
>
>                             No, these are all 2008R2 servers.   Both
>             ports and who worked with the 2.18 version, that I was using.
>
>             Paul.
>
>             *From:* Kris Springer <kspringer at innovateteam.com
>             <mailto:kspringer at innovateteam.com>>
>             *Sent:* Wednesday, February 20, 2019 12:01 PM
>             *To:* Root, Paul T <Paul.Root at CenturyLink.com
>             <mailto:Paul.Root at CenturyLink.com>>; xymon at xymon.com
>             <mailto:xymon at xymon.com>
>             *Subject:* Re: [Xymon] Windows PS xymonclient
>
>             Not sure if it's your issue or not, but I've found that
>             'who' is blank for Windows Home editions. Only Pro
>             editions or Servers shows me 'who' output.  Also, Windows
>             Home editions don't have RDP, so it wouldn't be there
>             anyway.  Also, I've seen these sorts of issues on my
>             servers before, and a reboot usually fixes it.
>
>             Kris Springer
>
>             On 2/20/19 10:47 AM, Root, Paul T wrote:
>
>                 So I only have 6 windows servers that I’m concerned
>                 with in my xymon installation.
>
>                 Today, I decided to upgrade the service. So I
>                 downloaded the v2.34 ps1 file. And I copied the file
>                 in place and restarted via the services window.
>
>                 This worked just fine on 4 machines.   But on 2
>                 machines, I get the ports test gone red because I’m
>                 looking for RDP, but I’m getting no output at all. 
>                 Going into who, it is also blank.
>
>                 Processes and SVCS are both fine.
>
>                 So next I started the powershell as an administrator,
>                 and did the ‘Set-ExecutablePolicy RemoteSigned” and
>                 then did a .\xymonclient.ps1 install. Then a stop and
>                 start.
>
>                 Still stays the same blank page.
>
>                 Does anyone have any ideas?
>
>                 Paul Root
>
>                 Lead Operations Engineer    - IT Managed Services
>
>                 390 Commerce Dr
>
>                 Woodbury, Mn 55125
>
>                 651-312-5207 paul.root at centurylink.com
>                 <mailto:paul.root at centurylink.com>
>
>                 This communication is the property of CenturyLink and
>                 may contain confidential or privileged information.
>                 Unauthorized use of this communication is strictly
>                 prohibited and may be unlawful. If you have received
>                 this communication in error, please immediately notify
>                 the sender by reply e-mail and destroy all copies of
>                 the communication and any attachments.
>
>                 _______________________________________________
>
>                 Xymon mailing list
>
>                 Xymon at xymon.com <mailto:Xymon at xymon.com>
>
>                 http://lists.xymon.com/mailman/listinfo/xymon
>
>             This communication is the property of CenturyLink and may
>             contain confidential or privileged information.
>             Unauthorized use of this communication is strictly
>             prohibited and may be unlawful. If you have received this
>             communication in error, please immediately notify the
>             sender by reply e-mail and destroy all copies of the
>             communication and any attachments.
>
>             This communication is the property of CenturyLink and may
>             contain confidential or privileged information.
>             Unauthorized use of this communication is strictly
>             prohibited and may be unlawful. If you have received this
>             communication in error, please immediately notify the
>             sender by reply e-mail and destroy all copies of the
>             communication and any attachments.
>
>             _______________________________________________
>             Xymon mailing list
>             Xymon at xymon.com <mailto:Xymon at xymon.com>
>             http://lists.xymon.com/mailman/listinfo/xymon
>
>         This communication is the property of CenturyLink and may
>         contain confidential or privileged information. Unauthorized
>         use of this communication is strictly prohibited and may be
>         unlawful. If you have received this communication in error,
>         please immediately notify the sender by reply e-mail and
>         destroy all copies of the communication and any attachments.
>
>     This communication is the property of CenturyLink and may contain
>     confidential or privileged information. Unauthorized use of this
>     communication is strictly prohibited and may be unlawful. If you
>     have received this communication in error, please immediately
>     notify the sender by reply e-mail and destroy all copies of the
>     communication and any attachments.
>     _______________________________________________
>     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/20190220/4acbae81/attachment.html>


More information about the Xymon mailing list