7 steps to install Nagios Plugins and NRPE on the remote host. Download Nagios Plugins and NRPE Add-on. Download following files from Nagios.org and move to. Build Status. Nagios Remote Plugin Executor. For installation instructions and information on the design overview of the NRPE addon, please read the PDF documentation that is found in this directory: docs/NRPE.pdf. If you are upgrading from a previous version, you'll want to check the.

Using NSClient++ with check_nrpe NRPE is the most common way to connect to NSClient. NRPE works much like NRPE for unix (if you are familiar with it) and in short you can say it relays a plugin request to a remote server. NRPE acts like a simple transport layer allowing remote execution. The difference between regular NRPE and NSClient++ is that NSClient++ has built-in checks.

So with NSClient++ you get a lot of ready-to-use checks that wont require you to have scripts. But if you choose you can disable all “modules” and stick with a pure NRPE installation and only external scripts.

Overview of NRPE For those not familiar with NRPE (Nagios Remote Plugin Execution) here is a quick introduction. NRPE works much like SSH or telnet etc. It relays a command and awaits the result.

In the above diagram what happens is: • Nagios executes check_nrpe with the proper arguments. • NSClient++ receives the command to be executed • NSClient++ will execute the command and get a result on the form of, and optionally • NSClient++ sends the result back to Nagios • Nagios gets the result from check_nrpe (and uses it much like any other plugin) So in essence NRPE is merely a transport mechanism to send the result of a check command over the network. Nagios command line NRPE require you to install a special plug-in on your Nagios server called NRPE. The unix-side of NRPE consists of a server and a client on Nagios you only need the client so you can skip any “servers” or what not that it want to start when you install it. The client is (generally) called check_nrpe and works like so. NRPEServer = enabled.

If you have not already done so (above) you also need to set which computers are allowed to query the agent. This is set either under the /settings/default section (globally) or under the /settings/NRPE/server section (locally). If you when you configured NSClient above set this globally you are already set to go. If not the key you need to change is the allowed hosts. There is no password for NRPE.

• allowed hosts = A list of addresses that is allowed to ask questions (i.e. Your Nagios ip). Cara Mencari Serial Number Software Dengan Ollydbg 64.

The result should look like this (assuming your Nagios server ip address is 10.0.0.2). Launching test mode - client mode d NSClient++.cpp(1106) Enabling debug mode. D NSClient++.cpp(494) Attempting to start NSCLient++ - 0.3.7.7 2009-07-05 d NSClient++.cpp(897) Loading plugin: NRPE server (w/ SSL). D NRPEServer.cpp(121) Starting NRPE socket.

L NSClient++.cpp(600) NSCLient++ - 0.3.7.7 2009-07-05 Started! D Socket.h(675) Bound to: 0.0.0.0:5666 l NSClient++.cpp(402) Using settings from: INI-file l NSClient++.cpp(403) Enter command to inject or exit to terminate. Now you can run the command again from Nagios like so.

NSClient++.cpp(1034) Injecting: foobar: NSClient++.cpp(1085) No handler for command: 'foobar' NSCHelper.cpp(238) No handler for command 'foobar'. We shall get back a bit to this later on when we have configure NSClient++ more so lets leave this for now.

NSClient++ configuration (revisited) Settin up NSClient++ was previously pretty simple and there is a bit more to it then we have thus far visited. This is because we have not configured anything yet all we can do now is talk to NSClient++ but not actually use it. So in this section we shall cover the basics and first off are some of the configuration options available for NRPE. NRPE specific setting in NSClient++ • ssl If this is true we will use SSL encryption on the transport.

Notice this flag has to be the same on both ends or you will end up with strange errors. The flag is set on check_nrpe with the -n option (if you use -n no SSL will be used). • allow arguments Since arguments can be potentially dangerous (it allows your users to control the execution) there is a flag (which defaults to off) to enable arguments. So if you plan on configure NSClient++ from the Nagios end you need to enable this. But be warned this is a security issue you need to think about.

If you do not want to allow arguments you can instead configure all checks in the nsclient.ini file and just execute the aliases from Nagios. One important issue with the allow arguments is that there are more then one! Yes, more then one! The reason for this is that you can allow arguments from NRPE and you can allow arguments for external scripts (it is not the same option) which might seem a bit confusing at first.

But actually quite nice. Using arguments for external scripts can potentially be more dangerous than allowing them from NRPE (internal commands).

• allow nasty characters This flag allows arguments to contain “dangerous” characters such as redirection and pipe ( ) and makes things a tad more dangerous. But if you decide to use arguments you most likely want to use this flag as well. But again this is a security risk.

Please also note this is also available for both NRPE and external scripts.S • insecure Allow legacy check_nrpe to connect. Activethreed 2 01 Downloads there. So this if you enable this in the INI file you will end up with something like this (extract). [/settings/NRPE/server] allow arguments = true allow nasty characters = false allowed hosts = 192.168.0.1/24 port = 5666 There are a lot of other options as well but these are the most used ones for details please refer to the. Modules The other thing which you should configure is which modules to use. There is several modules which can be used to check various aspects of your system.

So choosing which you need can be a bit of work. Here we shall start out with the basic ones and for details on the rest check out the [references section]/./references). Module Description Commands CheckSystem Handles many system checks check_cpu, check_memory etc CheckDisk Handles Disk related checks check_drivesize CheckExternalScripts Handles aliases (which is what we will use) and external scripts. N/A NRPEServer Listens and responds to incoming requests from Nagios via NRPE N/A There are a lot more modules The finished modules section from the INI file will look like so.

[/modules] CheckSystem = enabled CheckDisk = enabled CheckExternalScripts = enabled NRPEServer = enabled Now we have done some basic setup of NSClient++ and we can continue to try using it a bit more before we continue with configuring Nagios. Nagios command line (revisited) Now that we have the agent up and running (if not probably want to go back over the previous sections to get it up and running before reading on) what can we do with it?

From here on we will assume you have allow arguments and metachars enabled since it makes it simpler to try things out BEWARE that there are security implications to this so you might wanna read up before rolling this configuration into production. As we stated before check_nrpe is a lot more powerful than the legacy check_nt and there is a lot of built in commands as well as a lot of external ones you can use. Lets start with a simple one CheckCPU and see how to use it.

If we check the docs for it it has an example like so. -c CheckCPU -a warn=80 crit=90 time=20m time=10s time=4 CPU Load ok. '20m average'=11%;80;90; '10s average'=7%;80;90; '4 average'=10%;80;90; And that is as hard as it gets all you need to do is figure out which arguments you want to use for the command and stack them all in a long line. Nagios configuration Nagios configuration is in itself a whole chapter and this is just a quick peek on how you can do things. First off there are a few concepts to understand: • templates are the same as the corresponding item but they have a flag register = 0 which prevents them from being listed • services are essentially checks (is check CPU) • hosts are essentially computers • groups are an important concept which I ignore here for simplicity (I recommend you use it) The configuration is at the end layer quite simple you have a “check” and a “host” and you connect them with a service.

Like I show at the bottom line in the diagram above. Whats makes this a tad more complicated is that you can inherit things from a “parent” definition. Which is what I show with arrows (bottom to top) above. The templates with dashed lines are the base templates which all services and hosts inherit. Template First, its best practice to create a new template for each different type of host you’ll be monitoring. Let’s create a new template for windows servers.

So we are using Nagios to monitor our Windows Server environment for system resources, as well as services. We have several servers that have 3rd party services installed that contain spaces in the service name such as 'ColdFusion 8.NET Service'. Once Nagios runs the check we get the following 'Warning' Error. ColdFusion: Unknown 2nd issue - Services with special characters such as '$' hold up the entire Nagios program and we are unable to even start Nagios when these characters are in the configuration.

Any workarounds? Sorry Guys, Yes WizRd-Linux I tried your suggestion with no success. Kosarajudeepak - I did try the command line entry and recieved the same error MSSQL: Unknown At this point I am still open to suggestions but find it not to be a mission critical service in our environment and have decided to comment out the command on the linux box.

As for my 'poor behavior' by closing the question, - I was attempting to award kosarajudeepak half of the points created for this question as he solved half of the problem and leaving the other half on the table. If I did something wrong by requesting the question closed and awarding half points then let me know - as I will not try to jilt anyone out of points.