How to Add Linux Host to Nagios Monitoring Server Using NRPE Plugin

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Use our Linode referral link if you plan to buy VPS (it starts at only $10/month).
  4. Support us via PayPal donate - Make a Donation
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Ravi Saive

I am Ravi Saive, creator of TecMint. A Computer Geek and Linux Guru who loves to share tricks and tips on Internet. Most Of My Servers runs on Open Source Platform called Linux. Follow Me: Twitter, Facebook and Google+

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

Receive Your Free Complimentary eBook NOW! -

Download Free Linux eBooks

Advanced Bash-Scripting Guide
Linux Bible
A Newbie's Getting Started Guide to Linux
Introduction to Linux - A Hands on Guide

You may also like...

401 Responses

  1. tvskish says:

    Hi Ravi,

    I followed your procedures for both Nagios server set up and a remote machine setup. I am getting following error for verify NRPE daemon remotely.

    [root@nagios-server]# /usr/local/nagios/libexec/check_nrpe -H nagios-client
    CHECK_NRPE: Receive header underflow – only 0 bytes received (4 expected).
    [root@nagios-server etc]#

    log message from Nagios-server as follows
    Aug 26 14:44:23 nagios-server check_nrpe: Remote nagios-client does not support Version 3 Packets
    Aug 26 14:44:23 nagios-server check_nrpe: Remote nagios-client accepted a Version 2 Packet

    log message from Nagios-client as follows
    Aug 26 14:46:00 nagios-client xinetd[62465]: START: nrpe pid=24359 from=::ffff:
    Aug 26 14:46:00 nagios-client nrpe[24359]: Error: Could not complete SSL handshake with : 1
    Aug 26 14:46:00 nagios-client xinetd[62465]: EXIT: nrpe status=0 pid=24359 duration=0(sec)

    I googled to get know more about the error, but couldn’t get the correct answer. You have any idea about the error?


    • Ravi Saive says:


      Make sure you have the same NRPE version installed on the both Nagios server and remote Linux client, and also make sure to add Nagios Server IP address in remote Linux nrpe.cfg file under Xinetd file..

      • tvskish says:

        Hi Ravi,

        They both(Nagios server and remote client) at same version.

        [root@kinagios-server]# /usr/local/nagios/libexec/check_nrpe -V

        NRPE Plugin for Nagios
        Copyright (c) 1999-2008 Ethan Galstad (
        Version: nrpe-3.0
        Last Modified: 07-12-2016
        License: GPL v2 with exemptions (-l for more info)
        [root@nagios-client ~]# /usr/local/nagios/libexec/check_nrpe -V

        NRPE Plugin for Nagios
        Copyright (c) 1999-2008 Ethan Galstad (
        Version: nrpe-3.0
        Last Modified: 07-12-2016
        License: GPL v2 with exemptions (-l for more info)
        SSL/TLS Available: OpenSSL 0.9.6 or higher required

        Also Nagios Server IP address existing in remote Linux nrpe.cfg file and in Xinetd file.

        I am wondering why its accepting only v2 packets even if they are at 3.0 version of NRPE


        • Ravi Saive says:


          Thanks for sharing the details about NRPE version on both servers, seems strange problem, let me check and get back to you…

  2. Jonus Joseph says:

    Hi Tecmint Team / Ravi,

    Do we have any tutorial for SNMP trap monitoring using Nagios ? if not, can we get this documented ?

    • Ravi Saive says:


      No we don’t have a artice for SNMP trip monitoring, but we will create a article on same, could you tell us more about SNMP trap monitoring? is there any tool to do so or it has Nagios plugin available to setup?

      • Jonus Joseph says:

        Definition of “variable bindings” SNMP Trap :

        An SNMP trap allows a network device or SNMP enabled devices to contact the network management(monitoring application) when there is a significant event.
        This is done via unsolicited SNMP messages.

        example of SNMP Trap:

        if a UPS is out of power, an SNMP trap will be sent to the network administrator’s computer with the message, “Out of power.” A door sensor can send messages when the door is open.

        The SNMP Trap allows the manager to be notified when there is a problem so he can respond to it quickly without having to manually check everything to see what the error is.
        The program can receive such SNMP messages (SNMP traps) and alert a network administrator about them using a variety of methods

    • Jonus Joseph says:

      Hi Ravi,

      As per the Nagios official portal(web site) the best Article to implement SNMP Trap using Nagios monitoring given in below link:

      The SNMP Trap Implementation given in below source or URL may be good and accurate, but as I am unable to understand it because this is not much descriptive as like as the tecmint articles are.

      I am too much confident and sure if tecmint publish article on SNMP Trap monitoring that could be understand by everyone or most of the people.

      • Ravi Saive says:


        Thanks for the information about SNMP, we take a look and write a detailed easy to understand article on same, just give us some time..

Got something to say? Join the discussion.

Your email address will not be published. Required fields are marked *

Join Over 150K+ Linux Users
  1. 100,756
  2. 5,113
  3. 36,418

Enter your email to get latest Linux Howto's