Configuring Nagios Client : NRPE Plugin

-
                                                                           
We have discussed how to "Install Nagios Core on Amazon Linux Instance ". Please check the link for reference : http://linuxhotcoffee.blogspot.in/2016/03/installing-nagios-core-on-amazon-linux.html

My current Infrastructure details is given below : OS & Private IP

Monitoring Server : Amazon Linux Instance (10.10.1.100)
Client Server : Ubuntu (10.10.1.10)


Create User nagios and install below mentioned package

sudo useradd -m nagios
sudo apt-get install libssl-dev openssl xinetd build-essential


Now lets configure Monitoring server . Install NRPE on monitoring server.You can download the latest version of NRPE from Official Download page.Current latest version is NRPE 2.15 .Download the latest release using wget

cd ~
wget http://downloads.sourceforge.net/project/nagios/nrpe-2.x/nrpe-2.15/nrpe-2.15.tar.gz
wget http://nagios-plugins.org/download/nagios-plugins-2.1.1.tar.gz
Extract the tar file

tar -xvzf  nrpe-2.15.tar.gz
tar xzf nagios-plugins-2.1.1.tar.gz
Change the directory to

 cd nagios-plugins-2.1.1/

 Compile and install Plugin

 ./configure --with-nagios-user=nagios --with-nagios-group=nagios --with-openssl
make
make install
Change the directory to

cd nrpe-2.15/

Compile and install NRPE

./configure --with-ssl=/usr/bin/openssl --with-ssl-lib=/usr/lib/x86_64-linux-gnu
make install-plugin
make install-daemon
make install-daemon-config
make install-xinetd

Now modify the "only_from"  line in  /etc/xinetd.d/nrpe

vi /etc/xinetd.d/nrpe
only_from = 127.0.0.1 10.10.1.1000

Restart the xinetd service

service xinetd restart

Configuration on Nagios Monitor server is completed ,now we can move with configuration of Client Server

Install Nagios plugin and NRPE on Client Server

apt-get install nagios-plugins nagios-nrpe-server


Configure the Monitor Server ip on client nrpe.cfg file

vi /etc/nagios/nrpe.cfg

find allowed_hosts section in the file and add like the following

allowed_hosts=127.0.0.1,10.10.1.100


Restart then NRPE Service

service nagios-nrpe-server restart 











Comments

  1. for ict 9910 August 2020 at 11:55

    Great Article
    Cloud Computing Projects


    Networking Projects

    Final Year Projects for CSE


    JavaScript Training in Chennai

    JavaScript Training in Chennai

    The Angular Training covers a wide range of topics including Components, Angular Directives, Angular Services, Pipes, security fundamentals, Routing, and Angular programmability. The new Angular TRaining will lay the foundation you need to specialise in Single Page Application developer. Angular Training

    ReplyDelete

Post a Comment

Popular posts from this blog

Datastax Error : Cassandra - Saved cluster name Test Cluster != configured name

-
Image
While changing existing cluster name in datastax, i got name mismatch exception in log file. Process i followed was changed the cluster name in cassandra.yaml configuration file. $ nano /etc/dse/cassandra/cassandra.yaml     cluster_name: 'Test Cluster1' Solution :  Change the cluster name  to "New Cluster Name" : $ cqlsh `hostname -I` cqlsh> UPDATE system.local SET cluster_name = 'New Cluster Name' where key='local'; cqlsh> exit; $ nodetool flush system Stop the cluster : $ sudo service dse stop;sudo service datastax-agent stop Edit the file : $ sudo vi /etc/dse/cassandra/cassandra.yaml     cluster_name: ' New Cluster Name ' Start the cluster : $ sudo service dse start;sudo service datastax-agent start Check Installation log :  $ cat /var/log/cassandra/output.log Reference  : https://support.datastax.com/hc/en-us/articles/205289825-Change-Cluster-Name-
Continue Reading »»»»

Datastax Error : Cannot start node if snitch's data center (dc1) differs from previous data center (dc2)

-
Image
This error occurs when the node try to start and see it has snitch information which differ from previous data center. In my case, i was using DseSimpleSnitch which name the datacenter based on workload type. Previously i had enabled solr in dse default configuration file ( /etc/default/dse ) and datasenter name was Solr. Now i tried to start the dse with graph enabled, which change the name to datacenter SearchGraph which is default workload type name. CassandraDaemon.java:698 - Cannot start node if snitch's data center (Solr) differs from previous data center (SearchGraph). Please fix the snitch configuration, decommission and rebootstrap this node or use the flag -Dcassandra.ignore_dc=true Solution : 1) In the last line of  cassandra-env.sh  set in the jvm opts as given below : JVM_OPTS="$JVM_OPTS -Dcassandra.ignore_dc=true" 2) If it starts successfully, execute: nodetool repair nodetool cleanup
Continue Reading »»»»

Datastax Error : Error initializing cluster data

-
Image
I was getting the following error in Opscenter continuously and it get resolved automatically after some time. Error initializing cluster data: The request to /APP_Live/keyspaces?ksfields=column_families%2Creplica_placement_strategy%2Cstrategy_options%2Cis_system%2Cdurable_writes%2Cskip_repair%2Cuser_types%2Cuser_functions%2Cuser_aggregates&cffields=solr_core%2Ccreate_query%2Cis_in_memory%2Ctiers timed out after 10 seconds.. If you continue to see this error message, you can workaround this timeout by setting [ui].default_api_timeout to a value larger than 10 in opscenterd.conf and restarting opscenterd. Note that this is a workaround and you should also contact DataStax Support to follow up. Solution : Workaround of this timeout is by setting [ui].default_api_timeout to a value larger than 10 in opscenterd.conf and restarting opscenterd. 
Continue Reading »»»»

Popular posts from this blog

Datastax Error : Cassandra - Saved cluster name Test Cluster != configured name

-
Image
While changing existing cluster name in datastax, i got name mismatch exception in log file. Process i followed was changed the cluster name in cassandra.yaml configuration file. $ nano /etc/dse/cassandra/cassandra.yaml     cluster_name: 'Test Cluster1' Solution :  Change the cluster name  to "New Cluster Name" : $ cqlsh `hostname -I` cqlsh> UPDATE system.local SET cluster_name = 'New Cluster Name' where key='local'; cqlsh> exit; $ nodetool flush system Stop the cluster : $ sudo service dse stop;sudo service datastax-agent stop Edit the file : $ sudo vi /etc/dse/cassandra/cassandra.yaml     cluster_name: ' New Cluster Name ' Start the cluster : $ sudo service dse start;sudo service datastax-agent start Check Installation log :  $ cat /var/log/cassandra/output.log Reference  : https://support.datastax.com/hc/en-us/articles/205289825-Change-Cluster-Name-
Continue Reading »»»»

Datastax Error : Cannot start node if snitch's data center (dc1) differs from previous data center (dc2)

-
Image
This error occurs when the node try to start and see it has snitch information which differ from previous data center. In my case, i was using DseSimpleSnitch which name the datacenter based on workload type. Previously i had enabled solr in dse default configuration file ( /etc/default/dse ) and datasenter name was Solr. Now i tried to start the dse with graph enabled, which change the name to datacenter SearchGraph which is default workload type name. CassandraDaemon.java:698 - Cannot start node if snitch's data center (Solr) differs from previous data center (SearchGraph). Please fix the snitch configuration, decommission and rebootstrap this node or use the flag -Dcassandra.ignore_dc=true Solution : 1) In the last line of  cassandra-env.sh  set in the jvm opts as given below : JVM_OPTS="$JVM_OPTS -Dcassandra.ignore_dc=true" 2) If it starts successfully, execute: nodetool repair nodetool cleanup
Continue Reading »»»»

Datastax Error : Error initializing cluster data

-
Image
I was getting the following error in Opscenter continuously and it get resolved automatically after some time. Error initializing cluster data: The request to /APP_Live/keyspaces?ksfields=column_families%2Creplica_placement_strategy%2Cstrategy_options%2Cis_system%2Cdurable_writes%2Cskip_repair%2Cuser_types%2Cuser_functions%2Cuser_aggregates&cffields=solr_core%2Ccreate_query%2Cis_in_memory%2Ctiers timed out after 10 seconds.. If you continue to see this error message, you can workaround this timeout by setting [ui].default_api_timeout to a value larger than 10 in opscenterd.conf and restarting opscenterd. Note that this is a workaround and you should also contact DataStax Support to follow up. Solution : Workaround of this timeout is by setting [ui].default_api_timeout to a value larger than 10 in opscenterd.conf and restarting opscenterd. 
Continue Reading »»»»