{"id":24011,"date":"2015-07-31T17:16:38","date_gmt":"2015-07-31T11:46:38","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=24011"},"modified":"2017-03-30T09:41:40","modified_gmt":"2017-03-30T04:11:40","slug":"using-nagios-core-and-nrpe-to-monitor-remote-linux-hosts","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/using-nagios-core-and-nrpe-to-monitor-remote-linux-hosts\/","title":{"rendered":"Using Nagios Core and NRPE to monitor remote linux hosts"},"content":{"rendered":"

Prerequisites: <\/strong><\/p>\n

This tutorial requires existing Nagios server to be up and running and root privileges for Nagios server and remote Linux host. Please follow this<\/a> blog for its setup.<\/p>\n

Most of the system administrators write custom shell scripts \u00a0to do basic monitoring and sends email in case services crosses defined thresholds, but those scripts can’t provide complete insights of the host being monitored. To achieve this you will need to deploy a robust monitoring system that can provide features like Comprehensive Monitoring, Notification System, Reporting, Escalations, Event Handlers for Automation.<\/p>\n

I am writing this blog for continuing adding remote Linux hosts for monitoring in the Nagios server using NRPE daemon. This blog doesn’t include monitoring for Windows host or Network devices.<\/p>\n

What is NRPE?<\/strong><\/p>\n

NRPE is a Nagios Remote Plugin Executor, it is used for monitoring remote Linux host services like CPU Load, Current Users, Disk Utilization, Swap Utilization, Memory Utilization. For monitoring, remote hosts, we need to install NRPE agent and update ‘\/etc\/nagios\/nrpe.cfg’ file to allow access to Nagios server on port 5666. By default communication between Nagios server and NRPE agent is secure and uses the SSL tunnel for communication.
\n\"13_NRPE_Setup\"<\/p>\n

NRPE Checks<\/strong>
\n\"14_Direct_Indrect_npre_checks\"<\/p>\n

a. Direct checks:<\/strong> Nagios server directly checks, remote Linux host for local resources like load, disk, swap usage etc. (as shown above)<\/p>\n

b. Indirect checks:<\/strong> If Nagios server can not access target remote Linux host, then we can install NRPE on other Linux host and use it to check remote services.\u00a0(as shown above)<\/p>\n

Install NRPE server on Linux Host and NRPE Plugin on Nagios server<\/strong><\/p>\n

1. On Linux Host (Ubuntu)
\nFirst of all we will list down nagios-nrpe-server packages available, next install nagios-nrpe-server package as shown below and to check details about the package use the dpkg command as shown below:<\/p>\n

[js]aptitude search nagios-nrpe-server
\naptitude install nagios-nrpe-server
\ndpkg -L nagios-nrpe-server[\/js]<\/p>\n

\"1_search-nrpe-plugin\"<\/p>\n

2. On Nagios server (Ubuntu)
\nAs mentioned above, install nagios-nrpe-plugin on Nagios server, it will install nrpe command on the Nagios server.<\/p>\n

[js]aptitude search nagios-nrpe-plugin
\naptitude install nagios-nrpe-plugin
\ndpkg -L nagios-nrpe-plugin[\/js]<\/p>\n

\"2_nrpe-client-on-nagios-server\"<\/p>\n

In order to allow access to Nagios server, add a Nagios server IP to the allowed host (line no 81) in nrpe.cfg located in \/etc\/nagios\/nrpe.cfg. After making changes, restart nagios-nrpe-server on remote Linux host to update changes.
\n\"3_modify-nrpe-cfg-nagios-server-ip\"<\/p>\n

[js]service nagios-nrpe-server reload[\/js]<\/p>\n

To validate changes, manually run check_nrpe command from the Nagios server with an IP of remote Linux host to check the version of NRPE installed on a remote Linux host. Commands to try:<\/p>\n

[js]\/usr\/lib\/nagios\/plugins\/check_nrpe -H 10.1.13.249 [\/js]<\/p>\n

[js]\/usr\/lib\/nagios\/plugins\/check_nrpe -H 10.1.13.249 -c check_load [\/js]<\/p>\n

Note: H argument is for specifying Host and c for specifying command to be executed on remote Linux host<\/strong><\/span><\/h6>\n

\"4_ns_manual_nrpe_commands\"<\/p>\n

Example of NRPE Direct check:<\/span><\/strong><\/p>\n

By default nrpe.cfg configurations check disk using check_hda1. In my case drive name is \/dev\/sda1. So copy and paste above line and update command with the correct drive name(in my case \/dev\/sda1) and comment out the old line.<\/p>\n

[js] command[check_sda1]=\/usr\/lib\/nagios\/plugins\/check_disk -w 20% -c 10% -p \/dev\/sda1 [\/js]<\/p>\n

Note: In the above command arguments w is for warning, c is for critical and p is for partition, we will get warning alert if free space left reaches 20% and critical alert if it reaches 10%.\u00a0<\/strong><\/span><\/h6>\n

\"nrpr_cfg_new\"<\/p>\n

To execute nrpe commands using check_nrpe_1arg and “!” is used for passing arguments and in an argument we are passing check_sda1 (command defined on remote Linux host nrpe.cfg to check disk utilization)
\n\"7_add-nrpe-config-ns-disk-sda\"<\/p>\n

After making all the changes, restart Nagios service to make the changes effective.<\/p>\n

\"8_nagios-server-sda1-monitoring\"<\/p>\n

Example of NRPE In-direct check:<\/span><\/strong><\/p>\n

We can monitor www.google.com URL directly from the Nagios server using check_http, but in order to demonstrate nrpe indirect check I will be monitoring URL from another Linux host as shown below. For this we will update nrpe.cfg on remote Linux host and add new command check_http_indirect.
\n\"9_configure-indirect-http-on-linuxhost\"<\/p>\n

Once you update nrpe.cfg, try to run the command from terminal to validate we are getting desired output:
\n\"10_check-indirect-check-cmd-linux-host\"<\/p>\n

After checking manually, add indirect check configuration to the demo.cfg and restart Nagios3 daemon to update changes.
\n\"11_add-indirect-check-to-nagios-server\"<\/p>\n

Based upon the check interval defined, in my case 2 minutes, check Nagios3 GUI for updated statistics:
\n\"12_nagios-gui-check-indirect-check\"<\/p>\n

So this is how you can create multiple checks. In coming posts I will demonstrate how to enable custom checks using Nagios NRPE<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Prerequisites: This tutorial requires existing Nagios server to be up and running and root privileges for Nagios server and remote Linux host. Please follow this blog for its setup. Most of the system administrators write custom shell scripts \u00a0to do basic monitoring and sends email in case services crosses defined thresholds, but those scripts can’t […]<\/p>\n","protected":false},"author":216,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":36},"categories":[1],"tags":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/24011"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/216"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=24011"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/24011\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=24011"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=24011"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=24011"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}