[Xymon] [xymon] About Windows PS Client
David Baldwin
david.baldwin at ausport.gov.au
Fri Feb 25 01:28:31 CET 2011
My replies are inline to various questions below.
>
> -----Original Message-----
> From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of dOCtoR MADneSS
> Sent: Friday, 25 February 2011 8:27 AM
> To: xymon at xymon.com
> Subject: Re: [Xymon] [xymon] About Windows PS Client
>
> Le 24/02/2011 20:46, Shea, Graeme A a écrit :
>> Are you using a 64 bit or a 32 bit copy of Windows? WOW6432Node should only exist on Windows 64 bit though some programs write the registry entries anyway.
>>
>> The HKLM/Software/Wow6432Node can be a trap but should not be hidden, if you are running 64 bit then are you using a 32 version of RegEdit? If you use a 32 bit program to address the registry then the program sees this key instead of HKLM/Software and does not see a separate Wow6432Node at all. You can see this if you go the windows\SysWOW64 directory and run regedt32 (the 32 bit version). WOW stands for Windows On Windows as in running Windows 32 bit on Windows 64 bit.
>>
>> This is much the same as in the file system. 32 bit programs see \Windows\SysWOW64 as \Windows\System32. All the 32 bit utilities are in \Windows\SysWOW64 and for compatibility reasons the 64 bit ones are in \Windows\System32.
>>
>> Regards
>> Graeme
>>
>> -----Original Message-----
>> From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of dOCtoR MADneSS
>> Sent: Friday, 25 February 2011 2:40 AM
>> To: xymon at xymon.com
>> Subject: Re: [Xymon] [xymon] About Windows PS Client
>>
>> Le 24/02/2011 06:05, David Baldwin a écrit :
>>> On 23/02/11 10:10 PM, dOCtoR MADneSS wrote:
>>>> Le 25/01/2011 01:28, David Baldwin a écrit :
>>>>> On 25/01/11 8:05 AM, dOCtoR MADneSs wrote:
>>>>>> Le 24/01/2011 07:10, David Baldwin a écrit :
>>>>>>> On 24/01/11 3:55 AM, dOCtoR MADneSs wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I found this Xymon client :
>>>>>>>> http://xymon.svn.sourceforge.net/viewvc/xymon/sandbox/WinPSClient/
>>>>>>>> I tried to install it the way I found logical.
>>>>>>>>
>>>>>>>> 1st : I fought with Windows 7 Home Premium to allow execution on
>>>>>>>> PowerShell scripts. I finally edited registry and allow it manually.
>>>>>>>> 2nd : As administrator, I ran "powershell", then tried to install the
>>>>>>>> service this way :
>>>>>>>> .\xymonclient.ps1 install
>>>>>>>>
>>>>>>>> But I got many errors about adding service and modifying registry (all
>>>>>>>> errors are related to permission denial).
>>>>>>>>
>>>>>>>> Can D Baldwin, or anyone else informed about powershell and Xymon client
>>>>>>>> installation, help me ?
>>>>>>>>
>>>>>>> You'd need to have Administrator access to install I'm pretty sure.
>>>>>>>
>>>>>>> Please send me the errors and I'll see what I can do. I can probably
>>>>>>> find a Windows 7 box to test on.
>>>>>>>
>>>>>>> Thanks, David.
>>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Can you give me informations about XymonPSClient.exe ?
>>>>> XymonPSClient.exe is just a renamed copy of ABC_SRVANY.EXE which is just
>>>>> the service runner that spawns the powershell process to run the script
>>>>> - it is xymonclient.ps1 that is the actual client code.
>>>>>> Where logs and temporary files are stored ?
>>>>> %TEMP%\xymonclient.log - contains date stamp and a copy of the last
>>>>> client report - written out as a debugging aid, the script doesn't
>>>>> actually need any temporary files
>>>>> %TEMP%\xymonconfig.cfg - contains the config returned from the server
>>>>> after each report is sent (i.e client-local.cfg section).
>>>>>
>>>>> Note that value of %TEMP% - or in PS $env:TEMP - will depend on whether
>>>>> you are running the service as specific user or just as a local service,
>>>>> and on the version of Windows you are using.
>>>>>
>>>>> David.
>>>>>
>>>> Hi,
>>>>
>>>> I finally installed XymonPSClient in following the readme. The logfile
>>>> is generated in c:\windows\temp. But I can't see anything sent to xymon
>>>> server. The following command :
>>>> xymonsend "ping" "xymonserver"
>>>> reports me the xymon version running on server. But nothing else. The
>>>> windows client is defined in bb-hosts file. All I can see is "conn",
>>>> "info" and "trends".
>>>>
>>>> Any idea ? I'm new to windows 7 (home premium), and don't understand
>>>> everything about how it works (or how it doesn't)
>>>> _______________________________________________
>>>> Xymon mailing list
>>>> Xymon at xymon.com
>>>> http://lists.xymon.com/mailman/listinfo/xymon
>>> In the file xymonclient.log the section at the top has the config values
>>> - most of these can be overridden in the registry as per README
>>>
>>> Two values to check:
>>> clientname is the name that is being reported to the server in the
>>> client report - it needs to match an entry in hosts.cfg/bb-hosts
>>> (probably exact case match) - check "Ghost Clients" report.
>>> servers is the address or list of addresses the client should be
>>> reporting to.
>>>
>>> The fact that you can "ping" the xymon server means you're pretty close
>>> to it working.
>>>
>>> David.
>>>
>> Thank you for your support .It seems that HKLM/Software/Wow6432Node is
>> an hidden registry key, as I can't see it, nor create it with that name
>> (error tells me that another key has the same name). In log file,
>> everything was OK, but nothing was sent to Xymon servers. I set it
>> manually with ".\xymonclient.ps1 set servers "1.2.3.4 2.3.4.5"". And
>> it's OK ! I can see reports on the xymon servers.
So was there any value for "servers" before you explicitly set it?
Whatever client you're installing you need to tell it which servers to
report to.
The default value is "xymonhost" - if you have a DNS record (CNAME ro A
record) set up then no config would be required. The client will also
respect multiple A records if configured and report to each of them
(seemed like a good idea at the time ;)
>> I had to change a few
>> things in xymonclient.ps1 file, to get "usual" format for disk space
>> (used/total instead of total\used). Everything is OK now !
What the client reports is as much as possible character-for-character
compatible with BBWin to maintain compatibility with the server-side
processing of the client report. As far as I can tell, the disk report
for XymonPSClient, BBWin and BBNT are all the same order of columns.
>> Is there any docs on using/creating plugins for your windows client ?
What sort of plugin? Adding an extra section to the client report
wouldn't be hard. In principle it could also send status messages as
well as the client message, but you'd need to be careful.
There is no support for running external scripts at present and doing
that from Powershell would be really messy and vulnerable to causing the
whole client to fail. It would be better architecturally to have a
launcher that ran both the client and also any other external scripts
and managed them independently, even to the extent of having the
existing client save state between runs to reduce the risk of memory
leaks. There was one in development by Neil Franken, but nothing was
released. If anyone has any suggestions, it's the main barrier to
getting this client to a proper release state.
On one of my servers I run BBWin to run external scripts only and
XymonPSClient to do the client reporting. I've changed BBWin.cfg to do a
client report once per day and all loadable sections other than
externals commented out!
<setting name="autoreload" value="true" />
<setting name="timer" value="1d" />
<!-- load name="cpu" value="cpu.dll"/>
<load name="disk" value="disk.dll"/ -->
<load name="externals" value="externals.dll"/>
<!-- load name="filesystem" value="filesystem.dll"/>
<load name="memory" value="memory.dll"/>
<load name="msgs" value="msgs.dll"/>
<load name="procs" value="procs.dll"/>
<load name="stats" value="stats.dll"/>
<load name="svcs" value="svcs.dll"/>
<load name="uptime" value="uptime.dll"/>
<load name="who" value="who.dll"/ -->
>> _______________________________________________
>> Xymon mailing list
>> Xymon at xymon.com
>> http://lists.xymon.com/mailman/listinfo/xymon
>>
>
>
> -----Original Message-----
> From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of dOCtoR MADneSS
> Sent: Friday, 25 February 2011 8:27 AM
> To: xymon at xymon.com
> Subject: Re: [Xymon] [xymon] About Windows PS Client
>
> Le 24/02/2011 20:46, Shea, Graeme A a écrit :
>> Are you using a 64 bit or a 32 bit copy of Windows? WOW6432Node should only exist on Windows 64 bit though some programs write the registry entries anyway.
>>
>> The HKLM/Software/Wow6432Node can be a trap but should not be hidden, if you are running 64 bit then are you using a 32 version of RegEdit? If you use a 32 bit program to address the registry then the program sees this key instead of HKLM/Software and does not see a separate Wow6432Node at all. You can see this if you go the windows\SysWOW64 directory and run regedt32 (the 32 bit version). WOW stands for Windows On Windows as in running Windows 32 bit on Windows 64 bit.
>>
>> This is much the same as in the file system. 32 bit programs see \Windows\SysWOW64 as \Windows\System32. All the 32 bit utilities are in \Windows\SysWOW64 and for compatibility reasons the 64 bit ones are in \Windows\System32.
>>
I love the naming convention ;)
>> Regards
>> Graeme
>>
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>
>
> I'm sure my windows is 64bits. And I start registry editor with
> "regedit" command from powershell with admins rights. And in c:\windows
> I can't see any Wow64 directory. I remember you that I use windows 7
> home premium (don't know if it's important).
>
32-bit programs won't see SysWOW64, they will just see the keys inside
as their only view of the world. I have seen it on a 32-bit system where
some program had tried to create keys in there (must have thought it was
running on a 64-bit system).
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>
> If you go to control panel\system there will be an entry beside "System Type". This will say if it is 32 or 64 bit.
>
Another way is to enter the following in PowerShell - this is what the
client does to determine what it's running on.
[System.IntPtr]::Size*8
David.
--
David Baldwin - IT Unit
Australian Sports Commission www.ausport.gov.au
Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616
david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617
-------------------------------------------------------------------------------------
Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
-------------------------------------------------------------------------------------
More information about the Xymon
mailing list