winrpe - Nagios NRPE for Windows
Winrpe is a Nagios NRPE implementation for windows systems. It is a packaging of Nagios NRPE addon, Xinet, Cygwin and a collection of windows specific NRPE plugins for monitoring cpu, disk, memory, eventlog, services and performance counters. It can easily be expanded by other plugins.
The Nagios NRPE addon allows you to execute Nagios plugins on remote machines, enabling you to monitor local resources like CPU load, memory and disk usage. Since these resources are not usually exposed to other machines, an agent like Winrpe must be installed on the remote Windows machines. Xinetd is an open source super server daemon, which features a variety of access control (tcp wrappers) and configuration mechanisms (time and connection limits) and extensive logging. Cygwin is a Linux-like environment for Windows. It consists of a DLL (cygwin1.dll), which emulates substantial Linux API functionality, and a collection of tools.
Size: 8.0 MB
Size: 8.0 MB
Supported platforms : 2000/XP/2003/Vista/2008/7/2012/8.
Winrpe is available as a zip file containing an installer. Simply unzip your downloaded copy and run the package "winrpe_x.x.x_Installer.exe" or "winrpe_x.x.x_FullSSL_Installer.exe" :
- Accept License agreement.
- Specify an installation location.
- Specify a service account for the Xinet service.
- Installation starts. By clicking 'Details' button, you can get more detailed information about installation. Check if everything seems ok.
Winrpe is now installed and Xinet is activated as a manual service with a proper configuration to serve nrpe requests. Consult documentation from start menu for more information about components installed.
You need to update the configuration file nrpe.cfg (available from start menu) according to your needs and change the start mode to automatic. You can also enhance your Winrpe installation by other NRPE plugins from NagiosExchange or SourceForge.
For Winrpe with Full SSL patch:
- You need to create/supply a CA root certificate (cacert.pem as example) for your whole implementation. In addition, create a host certificate (hostname.pem) and the corresponding private key (hostname-key.pem) for each host you want to communicate with. Be aware of that Common name field should correspond to the FQDN of the host name as the best practice. You can find a well written and descriptive guideline here.
At Winrpe side:
- Copy all three files (cacert.pem, hostname.pem and hostname-key.pem) to the root directory of your Winrpe installation and add following directives to nrpe.cfg:
At server side:
- For Nagwin: Copy hostname.pem, hostname-key.pem and cacert.pem to a location appropriate for certificates (say /certs). Copy bin/check_nrpe.exe from Winrpe FullSSL distribution to plugins directory as check_nrpe_fullssl.exe and use the following syntax for your check definitions (assuming that all certificate files are located at the root directory):
check_nrpe_fullssl -H <host name> -C /certs/hostname.pem -k /certs/hostname-key.pem -r /certs/cacert.pem -c command .....
- For Unix hosts, you need to compile check_nrpe with the FullSSL patch and follow same steps as above.
This package contains components with different terms of licensing:
|GPL v2 contact Itefix for sources|
|Cygwin and GNU Tools||
|CYGWIN license contact Itefix for sources|
This one is easy too:
- Make sure that no monitors are connected.
- Choose Uninstall from Start menu. Again, you can monitor uninstallation process by clicking 'Details' button.
Let me emphasize that I play a very small role in this big game. I would like to thank to all people that make nagios nrpe+cygwin a powerful and flexible solution for monitoring of Windows systems.