[Xymon] Windows PS xymonclient

[Timothy Williams]

Another issue I had with missing data categories was the size of the data
file exceeding the buffer size set in Xymon. File got truncated leading to
missing data to analyse. Check the size of MAXMSG_STATUS, MAXMSG_CLIENT and
MAXMSG_DATA.
Also, on one server, a user had installed a service with square brackets as
part of the name [ xx ], which Xymon interpreted as a section, then would
not read the rest of the data file. Got that service name changed..

Tim Williams


On Wed, Feb 20, 2019 at 1:55 PM Root, Paul T <Paul.Root at centurylink.com>
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>
> *Sent:* Wednesday, February 20, 2019 12:10 PM
> *To:* Root, Paul T <Paul.Root at CenturyLink.com>
> *Cc:* Kris Springer <kspringer at innovateteam.com>; 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>
> 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> *On Behalf Of *Root, Paul T
> *Sent:* Wednesday, February 20, 2019 12:03 PM
> *To:* 'Kris Springer' <kspringer at innovateteam.com>; 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>
> *Sent:* Wednesday, February 20, 2019 12:01 PM
> *To:* Root, Paul T <Paul.Root at CenturyLink.com>; 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
>
>
>
> 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
>
> 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
> 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.
> _______________________________________________
> Xymon mailing list
> 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/51a5df8c/attachment.html>