Hi Everyone,

Just thought we'd flag this - on some tests when the status is red the XML being returned has an invalid character.

I've tried (unsuccessfully) checking for release notes to see if this has been addressed previously but couldn't find anything (apologies in advance if it has been fixed previously).

See the XML below - the issue is on the CDATA line just after the € symbol

<ServerStatus> <ServerName>[hostname]</ServerName> <Type>http</Type> <Status>red</Status> <TestFlags></TestFlags> <LastChange>Fri Feb 13 17:08:14 2015</LastChange> <LogTime>Fri Feb 13 17:11:14 2015</LogTime> <ValidTime>Fri Feb 13 17:41:14 2015</ValidTime> <AckTime>N/A</AckTime> <DisableTime>N/A</DisableTime> <Sender>10.1.1.200</Sender> <Cookie>148280</Cookie> <MessageSummary> <![CDATA[status+30 [hostname].http red Fri Feb 13 17:11:14 2015: €]]> </MessageSummary> </ServerStatus>

We are currently running 4.3.18. If you need any more information please let us know.

Kind Regards, Jason.

Jason Jones Senior Analyst/Developer

Codel Software Ltd Unit 1C Charnwood Park Bridgend CF31 3PL

+44 (0)1656 750 858 +44 (0)1656 648 649 info at codelsoftware.com http://www.codelsoftware.com

Follow Us: @codel_software at activabsence Linkedin http://www.activabsence.co.uk

Registered in Wales No. 5838660

DELIVERING QUALITY: At Codel Software we are committed to delivering quality software, services and client interactions. We have demonstrated this through quality audits and customer satisfaction. Codel Software is an ISO 9001:2008 certified company.

CONFIDENTIALITY NOTICE: This message is confidential and for the use only of the intended recipient. If you receive the message in error you are not entitled to disseminate, copy or use the contents in any way. In such circumstances please forward the message back to the sender.

WARNING :While Codel Software takes steps to prevent computer viruses from being transmitted via electronic mail attachments we cannot guarantee that attachments do not contain computer virus code. You are therefore strongly advised to undertake anti virus checks prior to accessing the attachment to this electronic mail.
Codel Software grants no warranties regarding performance use or quality of any attachment and undertakes no liability for loss or damage howsoever caused.

If you do not want to receive similar communications by e-mail from Codel Software, please reply to this e-mail with 'remove' in the subject line. Help the environment –please don't print this email unless you really need to!

This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com

I suggest going to:

http://lists.xymon.com/mailman/listinfo/xymon

and following the unsubscribe instructions.

Bruce White

Senior Enterprise Systems Engineer | Phone: 1-630-671-5169 | bewhite at fellowes.com | www.fellowes.com<http://www.fellowes.com>

[cid:image603379.JPG at 3647e188.4985d9ca]

Disclaimer: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc.

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of SNYDER, HOWARD Sent: Wednesday, February 18, 2015 6:43 AM To: Jason Jones; xymon at xymon.com Subject: Re: [Xymon] Invalid XML

Please remove me from this mailing list.

Howard Snyder Principal – Advanced Technical Support Cisco / Adjunct Mobility EMS-AT

Rethink Possible®

AT&T Technology Operations 5600 Glenridge Drive Atlanta, GA 30342 P: 404.531.5325 M: 404.219.1104 hs3082 at att.com<mailto:hs3082 at att.com>

Mobility ATS website: https://operations.web.att.com/sites/EMS/default.aspx EMS-AT website: http://ems-at.sst.att.com/ EMS trouble tickets http://atsemsatticket.web.att.com<http://atsemsatticket.web.att.com/>

"This e-mail and any files transmitted with it are AT&T property, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other uses, retention, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited."

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Jason Jones Sent: Wednesday, February 18, 2015 5:15 AM To: xymon at xymon.com<mailto:xymon at xymon.com> Subject: [Xymon] Invalid XML

Hi Everyone,

Just thought we'd flag this - on some tests when the status is red the XML being returned has an invalid character.

I've tried (unsuccessfully) checking for release notes to see if this has been addressed previously but couldn't find anything (apologies in advance if it has been fixed previously).

See the XML below - the issue is on the CDATA line just after the € symbol

<ServerStatus> <ServerName>[hostname]</ServerName> <Type>http</Type> <Status>red</Status> <TestFlags></TestFlags> <LastChange>Fri Feb 13 17:08:14 2015</LastChange> <LogTime>Fri Feb 13 17:11:14 2015</LogTime> <ValidTime>Fri Feb 13 17:41:14 2015</ValidTime> <AckTime>N/A</AckTime> <DisableTime>N/A</DisableTime> <Sender>10.1.1.200</Sender> <Cookie>148280</Cookie> <MessageSummary> <![CDATA[status+30 [hostname].http red Fri Feb 13 17:11:14 2015: €]]> </MessageSummary> </ServerStatus>

We are currently running 4.3.18. If you need any more information please let us know.

Kind Regards, Jason.

Jason Jones Senior Analyst/Developer

Codel Software Ltd Unit 1C Charnwood Park Bridgend CF31 3PL

[http://www.codelsoftware.com/wp-content/uploads/2014/06/miniicon-tel.gif] +44 (0)1656 750 858 [http://www.codelsoftware.com/wp-content/uploads/2014/06/miniicon-fax.gif] +44 (0)1656 648 649 [http://www.codelsoftware.com/wp-content/uploads/2014/06/miniicon-email.gif] info at codelsoftware.com<mailto:info at codelsoftware.com> [http://www.codelsoftware.com/wp-content/uploads/2014/06/miniicon-home.gif] http://www.codelsoftware.com<http://www.codelsoftware.com/>

Follow Us: [http://www.codelsoftware.com/wp-content/uploads/2014/06/miniicon-twitter.gif] @codel_software<http://twitter.com/codel_software>@activabsence<http://twitter.com/activabsence> [http://www.codelsoftware.com/wp-content/uploads/2014/06/miniicon-linkedin.gi...] Linkedin<http://www.linkedin.com/company/codel-software-ltd> [http://www.codelsoftware.com/wp-content/uploads/2014/06/miniicon-aac.gif] http://www.activabsence.co.uk<http://www.activabsence.co.uk/>

Registered in Wales No. 5838660

DELIVERING QUALITY: At Codel Software we are committed to delivering quality software, services and client interactions. We have demonstrated this through quality audits and customer satisfaction. Codel Software is an ISO 9001:2008 certified company.

CONFIDENTIALITY NOTICE: This message is confidential and for the use only of the intended recipient. If you receive the message in error you are not entitled to disseminate, copy or use the contents in any way. In such circumstances please forward the message back to the sender.

WARNING :While Codel Software takes steps to prevent computer viruses from being transmitted via electronic mail attachments we cannot guarantee that attachments do not contain computer virus code. You are therefore strongly advised to undertake anti virus checks prior to accessing the attachment to this electronic mail. Codel Software grants no warranties regarding performance use or quality of any attachment and undertakes no liability for loss or damage howsoever caused.

If you do not want to receive similar communications by e-mail from Codel Software, please reply to this e-mail with 'remove' in the subject line.

Help the environment –please don't print this email unless you really need to!

This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com

Hi

Thanks for the bug report - I've committed a patch which should fix the multiple servers issue, please try it.

There should be a single <servers> element in your config, containing the list of servers, space delimited:

<servers>server1.domain.com server2.domain.com</servers>

Re: mountpoints, if you add this to your XML config, you will get mountpoints.

<wanteddisks>3 4</wanteddisks>

By default, wanteddisks = 3 - possible settings below, and you can combine settings with spaces:

2=USB

3=Local disks

4=Network shares

5=CD

But you will need the latest patch with the config fix for this to work properly.

Regards,

Zak

From: Gavin Stone-Tolcher [mailto:g.stone-tolcher at its.uq.edu.au] Sent: 17 February 2015 00:09 To: Beck, Zak; xymon-developer at lists.sourceforge.net; xymon at xymon.com Subject: RE: Xymon Powershell Windows client

Just a quick FYI:

I was just trying a test install on a 32bit windows 7 client and got this:

Cannot set "servers" because only strings can be used as values to set XmlNode p

At C:\Program Files\xymon\xymonclient.ps1:644 char:26

•         $script:XymonSettings. <<<< servers =

  $script:XymonSettings.server

  • CategoryInfo : InvalidOperation: (:) [], RuntimeException

  • FullyQualifiedErrorId : PropertyAssignmentException

I had multiple IP in the <servers> etry in the config.

Changing the <servers> entry in xymonclient_config.xml to have a single entry rather than multiple whitespace entries allows the client to install with no error.

After installation adding a second IP to <servers> entry also does not seem to work with it just reporting to the first entry?

Also just another quick one, I have a mountpoint defined on this system that does not seem to be collected. Are mountpoints supported?

I re-ran the bbwin client on the same system and the mountpoint is detected and displayed.

Cheers,

Gavin Stone-Tolcher, IT Support Officer, Network Operations and Incident Response

Information Technology Services

The University of Queensland

Level 4, Prentice Building, St Lucia 4072

T: +61 7 334 66645, M: +61 401 140 838

E: <mailto:g.stone-tolcher at its.uq.edu.au> g.stone-tolcher at its.uq.edu.au W: <http://www.its.uq.edu.au> www.its.uq.edu.au

ITS: Service. Team. Accountability. Results.

IMPORTANT: This email and any attachments are intended solely for the addressee(s), contain copyright material and are confidential. We do not waive any legal privilege or rights in respect of copyright or confidentiality. Except as intended addressees are otherwise permitted, you do not have permission to use, disclose, reproduce or communicate any part of this email or its attachments. Statements, opinions and information not related to the official business of The University of Queensland are neither given nor endorsed by us. By using this email (including accessing any attachments or links) you agree we are not liable for any loss or damage of any kind arising in connection with any electronic defect, virus or other malicious code we did not intentionally include.

Please consider the environment before printing this email.

CRICOS Code 00025B

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of zak.beck at accenture.com <mailto:zak.beck at accenture.com> Sent: Friday, 13 February 2015 7:53 PM To: xymon-developer at lists.sourceforge.net <mailto:xymon-developer at lists.sourceforge.net> ; xymon at xymon.com <mailto:xymon at xymon.com> Subject: [Xymon] Xymon Powershell Windows client

Hi all,

Today I have uploaded a new version of the Xymon Powershell client to SVN (in sandbox/WinPSClient). We (Accenture) are very pleased to be contributing these changes to the open source community. I've been working on this now for around 8 months on and off and hopefully the changes made will be of benefit to everyone!

Whilst making changes, we have focussed mainly on making it work, improving reliability and most importantly improving performance.

In most cases, on our 64 bit OS virtual machines, a data collection now takes around 5 seconds. On heavily loaded (CPU load or event log load) servers, the script is now considerably faster than originally. Key to this has been reducing the amount of WMI usage as this was a major culprit.

We have also implemented some new features, largely based on our in-house requirements but hopefully useful to others:

•     Showing the process owner and command line in [procs]. This has

  been implemented using c# code, compiled at runtime.

•     Adding Active Directory replication test, Terminal Services

  sessions test

•     Ability to restart any stopped Windows service

•     Client self-update

•     Dirsize and dirtime checks (which were originally external

  scripts)

Some things have changed slightly; for example, the local configuration which was registry-based is now XML-based (you can still use registry settings if you prefer). In the SVN repository I have also uploaded a Word document which describes how to install and the configuration options.

I have uploaded all the revisions we have made to SVN so there is a history of development. Whilst we will endeavour to continue contributing changes and improvements in coming months, this is an open source project and as such we are not offering any formal support. If anyone wishes to bugfix, branch or whatever, please do so!

Zak Beck Accenture

I am wondering if the "disk" code in the powershell client might need some tweaks to collect MountPoint info?

For reference to client data chunks for the different clients are:

Powershell v1.97:

[disk] Filesystem 1K-blocks Used Avail Capacity Mounted Summary(Total\Avail GB) C 104753148 42705800 62047348 41% /FIXED/C 99.90\59.17

Bbwin v0.13

[disk] Filesystem 1K-blocks Used Avail Capacity Total Size Free Space Type Mount Point C 104753148 42706904 62046244 40% 99.90 GB 59.17 GB FIXED N/A MountPointTest 104753148 42706904 62046244 40% 99.90 GB 59.17 GB FIXED C:\MountPointTest\

Cheers, Gavin Stone-Tolcher, IT Support Officer, Network Operations and Incident Response Information Technology Services The University of Queensland Level 4, Prentice Building, St Lucia 4072 T: +61 7 334 66645, M: +61 401 140 838 E: g.stone-tolcher at its.uq.edu.au<mailto:g.stone-tolcher at its.uq.edu.au> W: www.its.uq.edu.au<http://www.its.uq.edu.au>

ITS: Service. Team. Accountability. Results.

IMPORTANT: This email and any attachments are intended solely for the addressee(s), contain copyright material and are confidential. We do not waive any legal privilege or rights in respect of copyright or confidentiality. Except as intended addressees are otherwise permitted, you do not have permission to use, disclose, reproduce or communicate any part of this email or its attachments. Statements, opinions and information not related to the official business of The University of Queensland are neither given nor endorsed by us. By using this email (including accessing any attachments or links) you agree we are not liable for any loss or damage of any kind arising in connection with any electronic defect, virus or other malicious code we did not intentionally include.

Please consider the environment before printing this email.

CRICOS Code 00025B

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Gavin Stone-Tolcher Sent: Wednesday, 18 February 2015 11:19 AM To: 'zak.beck at accenture.com'; xymon-developer at lists.sourceforge.net; xymon at xymon.com Subject: Re: [Xymon] Xymon Powershell Windows client

Many many thanks for the quick fix for multiple servers. V1.97 is working OK now for me in this respect!

I still am not seeing a windows MountPoint on my test Win 7 32bit client in the "disk" output with v1.97 and "wanteddisks" set to "3 4".

Quickly looking at the client's code, it appears that "Get-WmiObject -Class Win32_LogicalDisk" is used to collect disk info? Several google clicks later, various sites seem to suggest windows MountPoint info is not really available using that class? e.g. http://learn-powershell.net/2012/08/10/locating-mount-points-using-powershel...

Another good site with code examples suggests using the "Win32_Volume" class to collect the info http://blogs.lessthandot.com/index.php/sysadmins/os/windows/getting-remote-m...

While yet another site seems to be using the "Win32_MountPoint" class in his code to get MountPoint info from what I can see: http://www.powershelladmin.com/wiki/PowerShell_Get-MountPointData_Cmdlet#Sho...

I tried looking at the C++ code of winbb client but I'm afraid I can't make much sense of it.

I am wondering if the "disk" code in the powershell client might need some tweaks to collect MountPoint info?

Cheers, Gavin Stone-Tolcher, IT Support Officer, Network Operations and Incident Response Information Technology Services The University of Queensland Level 4, Prentice Building, St Lucia 4072 T: +61 7 334 66645, M: +61 401 140 838 E: g.stone-tolcher at its.uq.edu.au<mailto:g.stone-tolcher at its.uq.edu.au> W: www.its.uq.edu.au<http://www.its.uq.edu.au>

ITS: Service. Team. Accountability. Results.

IMPORTANT: This email and any attachments are intended solely for the addressee(s), contain copyright material and are confidential. We do not waive any legal privilege or rights in respect of copyright or confidentiality. Except as intended addressees are otherwise permitted, you do not have permission to use, disclose, reproduce or communicate any part of this email or its attachments. Statements, opinions and information not related to the official business of The University of Queensland are neither given nor endorsed by us. By using this email (including accessing any attachments or links) you agree we are not liable for any loss or damage of any kind arising in connection with any electronic defect, virus or other malicious code we did not intentionally include.

Please consider the environment before printing this email.

CRICOS Code 00025B

From: zak.beck at accenture.com [mailto:zak.beck at accenture.com] Sent: Tuesday, 17 February 2015 9:00 PM To: Gavin Stone-Tolcher; xymon-developer at lists.sourceforge.net; xymon at xymon.com Subject: RE: Xymon Powershell Windows client

Hi

Thanks for the bug report - I've committed a patch which should fix the multiple servers issue, please try it.

There should be a single <servers> element in your config, containing the list of servers, space delimited:

<servers>server1.domain.com server2.domain.com</servers>

Re: mountpoints, if you add this to your XML config, you will get mountpoints.

<wanteddisks>3 4</wanteddisks>

By default, wanteddisks = 3 - possible settings below, and you can combine settings with spaces:

2=USB 3=Local disks 4=Network shares 5=CD

But you will need the latest patch with the config fix for this to work properly.

Regards, Zak

From: Gavin Stone-Tolcher [mailto:g.stone-tolcher at its.uq.edu.au] Sent: 17 February 2015 00:09 To: Beck, Zak; xymon-developer at lists.sourceforge.net; xymon at xymon.com Subject: RE: Xymon Powershell Windows client

Just a quick FYI:

I was just trying a test install on a 32bit windows 7 client and got this:

Cannot set "servers" because only strings can be used as values to set XmlNode p At C:\Program Files\xymon\xymonclient.ps1:644 char:26

•         $script:XymonSettings. <<<< servers = $script:XymonSettings.server

  + CategoryInfo : InvalidOperation: (:) [], RuntimeException
  • FullyQualifiedErrorId : PropertyAssignmentException

I had multiple IP in the <servers> etry in the config. Changing the <servers> entry in xymonclient_config.xml to have a single entry rather than multiple whitespace entries allows the client to install with no error.

After installation adding a second IP to <servers> entry also does not seem to work with it just reporting to the first entry?

Also just another quick one, I have a mountpoint defined on this system that does not seem to be collected. Are mountpoints supported? I re-ran the bbwin client on the same system and the mountpoint is detected and displayed.

Cheers, Gavin Stone-Tolcher, IT Support Officer, Network Operations and Incident Response Information Technology Services The University of Queensland Level 4, Prentice Building, St Lucia 4072 T: +61 7 334 66645, M: +61 401 140 838 E: g.stone-tolcher at its.uq.edu.au<mailto:g.stone-tolcher at its.uq.edu.au> W: www.its.uq.edu.au<http://www.its.uq.edu.au>

ITS: Service. Team. Accountability. Results.

IMPORTANT: This email and any attachments are intended solely for the addressee(s), contain copyright material and are confidential. We do not waive any legal privilege or rights in respect of copyright or confidentiality. Except as intended addressees are otherwise permitted, you do not have permission to use, disclose, reproduce or communicate any part of this email or its attachments. Statements, opinions and information not related to the official business of The University of Queensland are neither given nor endorsed by us. By using this email (including accessing any attachments or links) you agree we are not liable for any loss or damage of any kind arising in connection with any electronic defect, virus or other malicious code we did not intentionally include.

Please consider the environment before printing this email.

CRICOS Code 00025B

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of zak.beck at accenture.com<mailto:zak.beck at accenture.com> Sent: Friday, 13 February 2015 7:53 PM To: xymon-developer at lists.sourceforge.net<mailto:xymon-developer at lists.sourceforge.net>; xymon at xymon.com<mailto:xymon at xymon.com> Subject: [Xymon] Xymon Powershell Windows client

Hi all,

Today I have uploaded a new version of the Xymon Powershell client to SVN (in sandbox/WinPSClient). We (Accenture) are very pleased to be contributing these changes to the open source community. I've been working on this now for around 8 months on and off and hopefully the changes made will be of benefit to everyone!

Whilst making changes, we have focussed mainly on making it work, improving reliability and most importantly improving performance.

In most cases, on our 64 bit OS virtual machines, a data collection now takes around 5 seconds. On heavily loaded (CPU load or event log load) servers, the script is now considerably faster than originally. Key to this has been reducing the amount of WMI usage as this was a major culprit.

We have also implemented some new features, largely based on our in-house requirements but hopefully useful to others:

•     Showing the process owner and command line in [procs]. This has been implemented using c# code, compiled at runtime.

•     Adding Active Directory replication test, Terminal Services sessions test

•     Ability to restart any stopped Windows service

•     Client self-update

•     Dirsize and dirtime checks (which were originally external scripts)

Some things have changed slightly; for example, the local configuration which was registry-based is now XML-based (you can still use registry settings if you prefer). In the SVN repository I have also uploaded a Word document which describes how to install and the configuration options.

I have uploaded all the revisions we have made to SVN so there is a history of development. Whilst we will endeavour to continue contributing changes and improvements in coming months, this is an open source project and as such we are not offering any formal support. If anyone wishes to bugfix, branch or whatever, please do so! Zak Beck Accenture

Thanks for the mountpoint info, I'll need to look at this in some detail. I'll put it on the todo list.

Zak

From: Gavin Stone-Tolcher [mailto:g.stone-tolcher at its.uq.edu.au] Sent: 18 February 2015 01:19 To: Beck, Zak; xymon-developer at lists.sourceforge.net; xymon at xymon.com Subject: RE: Xymon Powershell Windows client

Many many thanks for the quick fix for multiple servers. V1.97 is working OK now for me in this respect!

I still am not seeing a windows MountPoint on my test Win 7 32bit client in the "disk" output with v1.97 and "wanteddisks" set to "3 4".

Quickly looking at the client's code, it appears that "Get-WmiObject -Class Win32_LogicalDisk" is used to collect disk info?

Several google clicks later, various sites seem to suggest windows MountPoint info is not really available using that class?

e.g.

http://learn-powershell.net/2012/08/10/locating-mount-points-using-powershel l/

Another good site with code examples suggests using the "Win32_Volume" class to collect the info

http://blogs.lessthandot.com/index.php/sysadmins/os/windows/getting-remote-m ount-point-information/

While yet another site seems to be using the "Win32_MountPoint" class in his code to get MountPoint info from what I can see:

http://www.powershelladmin.com/wiki/PowerShell_Get-MountPointData_Cmdlet#Sho wing_Used.2FFree_Space_On_Mount_Points

I tried looking at the C++ code of winbb client but I'm afraid I can't make much sense of it.

I am wondering if the "disk" code in the powershell client might need some tweaks to collect MountPoint info?

Cheers,

Gavin Stone-Tolcher, IT Support Officer, Network Operations and Incident Response

Information Technology Services

The University of Queensland

Level 4, Prentice Building, St Lucia 4072

T: +61 7 334 66645, M: +61 401 140 838

E: <mailto:g.stone-tolcher at its.uq.edu.au> g.stone-tolcher at its.uq.edu.au W: <http://www.its.uq.edu.au> www.its.uq.edu.au

ITS: Service. Team. Accountability. Results.

IMPORTANT: This email and any attachments are intended solely for the addressee(s), contain copyright material and are confidential. We do not waive any legal privilege or rights in respect of copyright or confidentiality. Except as intended addressees are otherwise permitted, you do not have permission to use, disclose, reproduce or communicate any part of this email or its attachments. Statements, opinions and information not related to the official business of The University of Queensland are neither given nor endorsed by us. By using this email (including accessing any attachments or links) you agree we are not liable for any loss or damage of any kind arising in connection with any electronic defect, virus or other malicious code we did not intentionally include.

Please consider the environment before printing this email.

CRICOS Code 00025B

From: zak.beck at accenture.com <mailto:zak.beck at accenture.com> [mailto:zak.beck at accenture.com] Sent: Tuesday, 17 February 2015 9:00 PM To: Gavin Stone-Tolcher; xymon-developer at lists.sourceforge.net <mailto:xymon-developer at lists.sourceforge.net> ; xymon at xymon.com <mailto:xymon at xymon.com> Subject: RE: Xymon Powershell Windows client

Hi

Thanks for the bug report - I've committed a patch which should fix the multiple servers issue, please try it.

There should be a single <servers> element in your config, containing the list of servers, space delimited:

<servers>server1.domain.com server2.domain.com</servers>

Re: mountpoints, if you add this to your XML config, you will get mountpoints.

<wanteddisks>3 4</wanteddisks>

By default, wanteddisks = 3 - possible settings below, and you can combine settings with spaces:

2=USB

3=Local disks

4=Network shares

5=CD

But you will need the latest patch with the config fix for this to work properly.

Regards,

Zak

From: Gavin Stone-Tolcher [mailto:g.stone-tolcher at its.uq.edu.au] Sent: 17 February 2015 00:09 To: Beck, Zak; xymon-developer at lists.sourceforge.net <mailto:xymon-developer at lists.sourceforge.net> ; xymon at xymon.com <mailto:xymon at xymon.com> Subject: RE: Xymon Powershell Windows client

Just a quick FYI:

I was just trying a test install on a 32bit windows 7 client and got this:

Cannot set "servers" because only strings can be used as values to set XmlNode p

At C:\Program Files\xymon\xymonclient.ps1:644 char:26

•         $script:XymonSettings. <<<< servers =

  $script:XymonSettings.server

  • CategoryInfo : InvalidOperation: (:) [], RuntimeException

  • FullyQualifiedErrorId : PropertyAssignmentException

I had multiple IP in the <servers> etry in the config.

Changing the <servers> entry in xymonclient_config.xml to have a single entry rather than multiple whitespace entries allows the client to install with no error.

After installation adding a second IP to <servers> entry also does not seem to work with it just reporting to the first entry?

Also just another quick one, I have a mountpoint defined on this system that does not seem to be collected. Are mountpoints supported?

I re-ran the bbwin client on the same system and the mountpoint is detected and displayed.

Cheers,

Gavin Stone-Tolcher, IT Support Officer, Network Operations and Incident Response

Information Technology Services

The University of Queensland

Level 4, Prentice Building, St Lucia 4072

T: +61 7 334 66645, M: +61 401 140 838

E: <mailto:g.stone-tolcher at its.uq.edu.au> g.stone-tolcher at its.uq.edu.au W: <http://www.its.uq.edu.au> www.its.uq.edu.au

ITS: Service. Team. Accountability. Results.

IMPORTANT: This email and any attachments are intended solely for the addressee(s), contain copyright material and are confidential. We do not waive any legal privilege or rights in respect of copyright or confidentiality. Except as intended addressees are otherwise permitted, you do not have permission to use, disclose, reproduce or communicate any part of this email or its attachments. Statements, opinions and information not related to the official business of The University of Queensland are neither given nor endorsed by us. By using this email (including accessing any attachments or links) you agree we are not liable for any loss or damage of any kind arising in connection with any electronic defect, virus or other malicious code we did not intentionally include.

Please consider the environment before printing this email.

CRICOS Code 00025B

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of zak.beck at accenture.com <mailto:zak.beck at accenture.com> Sent: Friday, 13 February 2015 7:53 PM To: xymon-developer at lists.sourceforge.net <mailto:xymon-developer at lists.sourceforge.net> ; xymon at xymon.com <mailto:xymon at xymon.com> Subject: [Xymon] Xymon Powershell Windows client

Hi all,

Today I have uploaded a new version of the Xymon Powershell client to SVN (in sandbox/WinPSClient). We (Accenture) are very pleased to be contributing these changes to the open source community. I've been working on this now for around 8 months on and off and hopefully the changes made will be of benefit to everyone!

Whilst making changes, we have focussed mainly on making it work, improving reliability and most importantly improving performance.

In most cases, on our 64 bit OS virtual machines, a data collection now takes around 5 seconds. On heavily loaded (CPU load or event log load) servers, the script is now considerably faster than originally. Key to this has been reducing the amount of WMI usage as this was a major culprit.

We have also implemented some new features, largely based on our in-house requirements but hopefully useful to others:

•     Showing the process owner and command line in [procs]. This has

  been implemented using c# code, compiled at runtime.

•     Adding Active Directory replication test, Terminal Services

  sessions test

•     Ability to restart any stopped Windows service

•     Client self-update

•     Dirsize and dirtime checks (which were originally external

  scripts)

Some things have changed slightly; for example, the local configuration which was registry-based is now XML-based (you can still use registry settings if you prefer). In the SVN repository I have also uploaded a Word document which describes how to install and the configuration options.

I have uploaded all the revisions we have made to SVN so there is a history of development. Whilst we will endeavour to continue contributing changes and improvements in coming months, this is an open source project and as such we are not offering any formal support. If anyone wishes to bugfix, branch or whatever, please do so!

Zak Beck Accenture

Hmm, I think this might be a difference between different versions of Powershell. I think this is why it works for Gavin but not you, Scot.

I could replicate your error on Powershell 2; I've committed a new revision which I have tested on Powershell 2 and Powershell 4.

The intended usage is <servers> per my original email. Also, multiple <servers> elements containing one IP/FQDN per element should also work.

Zak

From: Scot Kreienkamp [mailto:Scot.Kreienkamp at la-z-boy.com] Sent: 18 February 2015 03:16 To: Beck, Zak; g.stone-tolcher at its.uq.edu.au; xymon-developer at lists.sourceforge.net; xymon at xymon.com Subject: RE: Xymon Powershell Windows client

With the latest version I get "Property 'serversList' cannot be found on this object;". If I change servers to serversList it seems to work ok.

If it really did change to serversList you should update the doc or everyone that tries to install it will be emailing you. :)

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of zak.beck at accenture.com <mailto:zak.beck at accenture.com> Sent: Tuesday, February 17, 2015 6:00 AM To: g.stone-tolcher at its.uq.edu.au <mailto:g.stone-tolcher at its.uq.edu.au> ; xymon-developer at lists.sourceforge.net <mailto:xymon-developer at lists.sourceforge.net> ; xymon at xymon.com <mailto:xymon at xymon.com> Subject: Re: [Xymon] Xymon Powershell Windows client

Hi

Thanks for the bug report - I've committed a patch which should fix the multiple servers issue, please try it.

There should be a single <servers> element in your config, containing the list of servers, space delimited:

<servers>server1.domain.com server2.domain.com</servers>

Re: mountpoints, if you add this to your XML config, you will get mountpoints.

<wanteddisks>3 4</wanteddisks>

By default, wanteddisks = 3 - possible settings below, and you can combine settings with spaces:

2=USB

3=Local disks

4=Network shares

5=CD

But you will need the latest patch with the config fix for this to work properly.

Regards,

Zak

From: Gavin Stone-Tolcher [mailto:g.stone-tolcher at its.uq.edu.au] Sent: 17 February 2015 00:09 To: Beck, Zak; xymon-developer at lists.sourceforge.net <mailto:xymon-developer at lists.sourceforge.net> ; xymon at xymon.com <mailto:xymon at xymon.com> Subject: RE: Xymon Powershell Windows client

Just a quick FYI:

I was just trying a test install on a 32bit windows 7 client and got this:

Cannot set "servers" because only strings can be used as values to set XmlNode p

At C:\Program Files\xymon\xymonclient.ps1:644 char:26

•         $script:XymonSettings. <<<< servers =

  $script:XymonSettings.server

  • CategoryInfo : InvalidOperation: (:) [], RuntimeException

  • FullyQualifiedErrorId : PropertyAssignmentException

I had multiple IP in the <servers> etry in the config.

Changing the <servers> entry in xymonclient_config.xml to have a single entry rather than multiple whitespace entries allows the client to install with no error.

After installation adding a second IP to <servers> entry also does not seem to work with it just reporting to the first entry?

Also just another quick one, I have a mountpoint defined on this system that does not seem to be collected. Are mountpoints supported?

I re-ran the bbwin client on the same system and the mountpoint is detected and displayed.

Cheers,

Gavin Stone-Tolcher, IT Support Officer, Network Operations and Incident Response

Information Technology Services

The University of Queensland

Level 4, Prentice Building, St Lucia 4072

T: +61 7 334 66645, M: +61 401 140 838

E: <mailto:g.stone-tolcher at its.uq.edu.au> g.stone-tolcher at its.uq.edu.au W: <http://www.its.uq.edu.au> www.its.uq.edu.au

ITS: Service. Team. Accountability. Results.

IMPORTANT: This email and any attachments are intended solely for the addressee(s), contain copyright material and are confidential. We do not waive any legal privilege or rights in respect of copyright or confidentiality. Except as intended addressees are otherwise permitted, you do not have permission to use, disclose, reproduce or communicate any part of this email or its attachments. Statements, opinions and information not related to the official business of The University of Queensland are neither given nor endorsed by us. By using this email (including accessing any attachments or links) you agree we are not liable for any loss or damage of any kind arising in connection with any electronic defect, virus or other malicious code we did not intentionally include.

Please consider the environment before printing this email.

CRICOS Code 00025B

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of zak.beck at accenture.com <mailto:zak.beck at accenture.com> Sent: Friday, 13 February 2015 7:53 PM To: xymon-developer at lists.sourceforge.net <mailto:xymon-developer at lists.sourceforge.net> ; xymon at xymon.com <mailto:xymon at xymon.com> Subject: [Xymon] Xymon Powershell Windows client

Hi all,

Today I have uploaded a new version of the Xymon Powershell client to SVN (in sandbox/WinPSClient). We (Accenture) are very pleased to be contributing these changes to the open source community. I've been working on this now for around 8 months on and off and hopefully the changes made will be of benefit to everyone!

Whilst making changes, we have focussed mainly on making it work, improving reliability and most importantly improving performance.

In most cases, on our 64 bit OS virtual machines, a data collection now takes around 5 seconds. On heavily loaded (CPU load or event log load) servers, the script is now considerably faster than originally. Key to this has been reducing the amount of WMI usage as this was a major culprit.

We have also implemented some new features, largely based on our in-house requirements but hopefully useful to others:

•     Showing the process owner and command line in [procs]. This has

  been implemented using c# code, compiled at runtime.

•     Adding Active Directory replication test, Terminal Services

  sessions test

•     Ability to restart any stopped Windows service

•     Client self-update

•     Dirsize and dirtime checks (which were originally external

  scripts)

Some things have changed slightly; for example, the local configuration which was registry-based is now XML-based (you can still use registry settings if you prefer). In the SVN repository I have also uploaded a Word document which describes how to install and the configuration options.

I have uploaded all the revisions we have made to SVN so there is a history of development. Whilst we will endeavour to continue contributing changes and improvements in coming months, this is an open source project and as such we are not offering any formal support. If anyone wishes to bugfix, branch or whatever, please do so!

Zak Beck Accenture

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.

Hi

I'm not sure I understand the question fully, I'm sure there will be other people on the list who can help.

The client runs as a Windows service and monitors the space and processes running on that one server. It then reports back those results every 5 minutes (by default) to the Xymon server.

If you're asking whether this client can be running on server 1 and monitor server 2, no, it cannot. As far as I know, Xymon is not really designed like that.

However, if each node is attached to shared storage, and the storage is presented as a mapped drive, then yes, it can monitor that. You'd need to use in the local config:

<wanteddisks>3 4</wanteddisks>

and use the update I committed earlier today.

Thanks

Zak

From: Dito [mailto:dito74 at gmail.com] Sent: 17 February 2015 13:53 To: Beck, Zak; xymon-developer at lists.sourceforge.net; xymon at xymon.com Subject: Re: [Xymon] Xymon Powershell Windows client

can it be used in a MS cluster resource? can I monitor sql resource and space on it, independently of which node it is running on?

On Fri, Feb 13, 2015, 06:35 null <zak.beck at accenture.com <mailto:zak.beck at accenture.com> > wrote:

Hi all,

Today I have uploaded a new version of the Xymon Powershell client to SVN (in sandbox/WinPSClient). We (Accenture) are very pleased to be contributing these changes to the open source community. I've been working on this now for around 8 months on and off and hopefully the changes made will be of benefit to everyone!

Whilst making changes, we have focussed mainly on making it work, improving reliability and most importantly improving performance.

In most cases, on our 64 bit OS virtual machines, a data collection now takes around 5 seconds. On heavily loaded (CPU load or event log load) servers, the script is now considerably faster than originally. Key to this has been reducing the amount of WMI usage as this was a major culprit.

We have also implemented some new features, largely based on our in-house requirements but hopefully useful to others:

•     Showing the process owner and command line in [procs]. This has been 

  implemented using c# code, compiled at runtime.

•     Adding Active Directory replication test, Terminal Services sessions 

  test

•     Ability to restart any stopped Windows service

•     Client self-update

•     Dirsize and dirtime checks (which were originally external scripts)

Some things have changed slightly; for example, the local configuration which was registry-based is now XML-based (you can still use registry settings if you prefer). In the SVN repository I have also uploaded a Word document which describes how to install and the configuration options.

I have uploaded all the revisions we have made to SVN so there is a history of development. Whilst we will endeavour to continue contributing changes and improvements in coming months, this is an open source project and as such we are not offering any formal support. If anyone wishes to bugfix, branch or whatever, please do so!

Zak Beck Accenture

Xymon mailing list Xymon at xymon.com <mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon

Where is the zip file for distribution?

On Tue, Feb 17, 2015 at 11:07 AM, Scot Kreienkamp < Scot.Kreienkamp at la-z-boy.com> wrote:

Yes it can monitor a cluster, just not like dito is thinking.

Have the client setup on both nodes, configure xymon to monitor both nodes and the cluster address, and use combo tests to get a cluster status. Setup the combo tests so they show status on the cluster address, and configure the combo tests so that as long as one of the two nodes is green then the cluster is green as well. That is the best way, I do the same thing with Linux clusters here.

The other (less desirable) way is to hard code the cluster name in the config of the client, then set that service to failover and start with the cluster.

Scot Kreienkamp

*From:* Xymon [mailto:xymon-bounces at xymon.com] *On Behalf Of * zak.beck at accenture.com *Sent:* Tuesday, February 17, 2015 10:22 AM *To:* dito74 at gmail.com; xymon-developer at lists.sourceforge.net; xymon at xymon.com

*Subject:* Re: [Xymon] Xymon Powershell Windows client

Hi

I'm not sure I understand the question fully, I'm sure there will be other people on the list who can help.

The client runs as a Windows service and monitors the space and processes running on that one server. It then reports back those results every 5 minutes (by default) to the Xymon server.

If you're asking whether this client can be running on server 1 and monitor server 2, no, it cannot. As far as I know, Xymon is not really designed like that.

However, if each node is attached to shared storage, and the storage is presented as a mapped drive, then yes, it can monitor that. You'd need to use in the local config:

<wanteddisks>3 4</wanteddisks>

and use the update I committed earlier today.

Thanks

Zak

*From:* Dito [mailto:dito74 at gmail.com <dito74 at gmail.com>] *Sent:* 17 February 2015 13:53 *To:* Beck, Zak; xymon-developer at lists.sourceforge.net; xymon at xymon.com *Subject:* Re: [Xymon] Xymon Powershell Windows client

can it be used in a MS cluster resource? can I monitor sql resource and space on it, independently of which node it is running on?

On Fri, Feb 13, 2015, 06:35 null <zak.beck at accenture.com> wrote:

Hi all,

Today I have uploaded a new version of the Xymon Powershell client to SVN (in sandbox/WinPSClient). We (Accenture) are very pleased to be contributing these changes to the open source community. I've been working on this now for around 8 months on and off and hopefully the changes made will be of benefit to everyone!

Whilst making changes, we have focussed mainly on making it work, improving reliability and most importantly improving performance.

In most cases, on our 64 bit OS virtual machines, a data collection now takes around 5 seconds. On heavily loaded (CPU load or event log load) servers, the script is now considerably faster than originally. Key to this has been reducing the amount of WMI usage as this was a major culprit.

We have also implemented some new features, largely based on our in-house requirements but hopefully useful to others:

· Showing the process owner and command line in [procs]. This has been implemented using c# code, compiled at runtime.

· Adding Active Directory replication test, Terminal Services sessions test

· Ability to restart any stopped Windows service

· Client self-update

· Dirsize and dirtime checks (which were originally external scripts)

Some things have changed slightly; for example, the local configuration which was registry-based is now XML-based (you can still use registry settings if you prefer). In the SVN repository I have also uploaded a Word document which describes how to install and the configuration options.

I have uploaded all the revisions we have made to SVN so there is a history of development. Whilst we will endeavour to continue contributing changes and improvements in coming months, this is an open source project and as such we are not offering any formal support. If anyone wishes to bugfix, branch or whatever, please do so!

Zak Beck Accenture

---

Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon

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 http://lists.xymon.com/mailman/listinfo/xymon

Adding the label stuff to the todo list.

Nothing bad should happen (other than display glitches) if the value overflows the 9 length - it's just used for alignment. I can have a look at this when I do the mountpoint and label stuff.

Thanks

Zak

From: Gavin Stone-Tolcher [mailto:g.stone-tolcher at its.uq.edu.au] Sent: 23 February 2015 01:01 To: Beck, Zak; xymon at xymon.com Subject: RE: Xymon Powershell Windows client

Just a comment, the field widths for the display of 1K blocks for the "disk" output should probably be increased from "9" to "10" or "11" to allow for terabyte class devices?

Also the old BB client used to display the volume name enclosed in "()" after the "Mounted" field.

e.g.

Filesystem 1K-blocks Used Avail Capacity Mounted

C 142632960 43665264 98967696 30% /FIXED/C ()

D 142734336 56339072 86395264 39% /FIXED/D (DATA)

F 314572800 6421984 308150816 2% /FIXED/F (AUDIT)

G 314572800 264085248 50487548 83% /FIXED/G (SHARED)

I 629145600 608879424 20266156 96% /FIXED/I (PROJECTS1)

J 629145600 234245312 394900288 37% /FIXED/J (PROJECTS2)

K 629145600 267088320 362057280 42% /FIXED/K (USERS)

Some of the Windows guys at my site would like to see that info in the powershell client test output.

I wonder if a new field "Label" or "Volume" column could be added between the "Mounted" and "Summary" fields with that information.

The "VolumeName" field from Win32_LogicalDisk class could be used for the data?

I have added it locally and it does not seem to effect RRD collection or graphing for the test.

This is what I currently have being generated using a locally modified version of the client.

Filesystem 1K-blocks Used Avail Capacity Mounted Label Summary(Total\Avail GB)

C 104753148 42324428 62428720 40% /FIXED/C (SYSTEM) 99.90\59.54

I am using the "Label" field from Win32_Volume class for the data in this particular case.

Cheers,

Gavin Stone-Tolcher, IT Support Officer, Network Operations and Incident Response

Information Technology Services

The University of Queensland

Level 4, Prentice Building, St Lucia 4072

T: +61 7 334 66645, M: +61 401 140 838

E: <mailto:g.stone-tolcher at its.uq.edu.au> g.stone-tolcher at its.uq.edu.au W: <http://www.its.uq.edu.au> www.its.uq.edu.au

ITS: Service. Team. Accountability. Results.

IMPORTANT: This email and any attachments are intended solely for the addressee(s), contain copyright material and are confidential. We do not waive any legal privilege or rights in respect of copyright or confidentiality. Except as intended addressees are otherwise permitted, you do not have permission to use, disclose, reproduce or communicate any part of this email or its attachments. Statements, opinions and information not related to the official business of The University of Queensland are neither given nor endorsed by us. By using this email (including accessing any attachments or links) you agree we are not liable for any loss or damage of any kind arising in connection with any electronic defect, virus or other malicious code we did not intentionally include.

Please consider the environment before printing this email.

CRICOS Code 00025B

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of zak.beck at accenture.com <mailto:zak.beck at accenture.com> Sent: Friday, 13 February 2015 7:53 PM To: xymon-developer at lists.sourceforge.net <mailto:xymon-developer at lists.sourceforge.net> ; xymon at xymon.com <mailto:xymon at xymon.com> Subject: [Xymon] Xymon Powershell Windows client

Hi all,

Today I have uploaded a new version of the Xymon Powershell client to SVN (in sandbox/WinPSClient). We (Accenture) are very pleased to be contributing these changes to the open source community. I've been working on this now for around 8 months on and off and hopefully the changes made will be of benefit to everyone!

Whilst making changes, we have focussed mainly on making it work, improving reliability and most importantly improving performance.

In most cases, on our 64 bit OS virtual machines, a data collection now takes around 5 seconds. On heavily loaded (CPU load or event log load) servers, the script is now considerably faster than originally. Key to this has been reducing the amount of WMI usage as this was a major culprit.

We have also implemented some new features, largely based on our in-house requirements but hopefully useful to others:

•     Showing the process owner and command line in [procs]. This has

  been implemented using c# code, compiled at runtime.

•     Adding Active Directory replication test, Terminal Services

  sessions test

•     Ability to restart any stopped Windows service

•     Client self-update

•     Dirsize and dirtime checks (which were originally external

  scripts)

Some things have changed slightly; for example, the local configuration which was registry-based is now XML-based (you can still use registry settings if you prefer). In the SVN repository I have also uploaded a Word document which describes how to install and the configuration options.

I have uploaded all the revisions we have made to SVN so there is a history of development. Whilst we will endeavour to continue contributing changes and improvements in coming months, this is an open source project and as such we are not offering any formal support. If anyone wishes to bugfix, branch or whatever, please do so!

Zak Beck Accenture

Dirk,

I don't read German, but I can guess what might be wrong. When I downloaded the script it was blocked from executing by Windows. I had to right click on the script, select properties, and there was an unblock button. It only had to be done once. That property stays with the script when you copy it to other computers.

Scot Kreienkamp

-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Dirk Kastens Sent: Thursday, March 12, 2015 4:50 AM To: xymon at xymon.com Subject: Re: [Xymon] Xymon Powershell Windows client

Hi,

I just downloaded the latest version of the Powershell client. I tried to install ist on a 64bit Windows 7 machine. The installation works, but I can't get the service to start. The first thing is, that powershell complains about the xymonclient.ps1 not being digitally signed. So I set the execution policy to unrestricted. When I try to start the service I get the following message:

PS C:\Program Files\xymon> .\xymonclient.ps1 start start-service : Fehler beim Starten des Diensts "XymonPSClient (XymonPSClient)". In C:\Program Files\xymon\xymonclient.ps1:2708 Zeichen:60

• if((get-service $xymonsvcname).Status -ne "Running") {

  start-service $xymons ...

     + CategoryInfo          : OpenError:
(System.ServiceProcess.ServiceController:ServiceController)
[Start-Service], ServiceCommandException
     + FullyQualifiedErrorId :
StartServiceFailed,Microsoft.PowerShell.Commands.StartServiceCommand
--------------------------------------------

When I try to start the service manually with start-service I get:

--------------------------------------------
PS C:\Program Files\xymon> Start-Service XymonPSClient
Start-Service : Fehler beim Starten des Diensts "XymonPSClient
(XymonPSClient)".
In Zeile:1 Zeichen:1
+ Start-Service XymonPSClient
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
     + CategoryInfo          : OpenError:
(System.ServiceProcess.ServiceController:ServiceController)
[Start-Service], ServiceCommandException
     + FullyQualifiedErrorId :
StartServiceFailed,Microsoft.PowerShell.Commands.StartServiceCommand
--------------------------------------------

Any ideas what could be wrong?

Dirk

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.