Scribd
Upload
27 views3 pages

Project 6: Configure Nagios To Manage Servers: Group-11 B15207, B15107, B15219, B15104, B15125 May 6, 2018

This document outlines how to configure Nagios to monitor servers and resolve problems. It describes setting up Nagios to monitor server statistics like RAM usage, disk usage, and CPU load. Nagios can detect issues and take actions like restarting servers, removing files to free disk space, or blocking ports if CPU load is too high. It provides examples of how a system administrator can use Nagios to view health information and be notified of problems so they can be addressed.

Uploaded by

Rahul Singh Rajput
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
27 views3 pages

Project 6: Configure Nagios To Manage Servers: Group-11 B15207, B15107, B15219, B15104, B15125 May 6, 2018

This document outlines how to configure Nagios to monitor servers and resolve problems. It describes setting up Nagios to monitor server statistics like RAM usage, disk usage, and CPU load. Nagios can detect issues and take actions like restarting servers, removing files to free disk space, or blocking ports if CPU load is too high. It provides examples of how a system administrator can use Nagios to view health information and be notified of problems so they can be addressed.

Uploaded by

Rahul Singh Rajput
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Project 6: Configure Nagios to manage servers

Group-11 B15207,B15107,B15219,B15104,B15125

May 6, 2018

Contents
1 Introduction : 1
1.1 Purpose : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Scope of Project : . . . . . . . . . . . . . . . . . . . . . . . . . 1

2 Use cases : 2
2.1 System Admin : . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1.1 Monitoring health of server : . . . . . . . . . . . . . . 2
2.1.2 Detecting problem with server : . . . . . . . . . . . . . 2

3 Description of actions to resolve problems: 3

4 References : 3

1 Introduction :
1.1 Purpose :
This document is meant for someone setting up Nagios server monitoring
services for their servers. It will explain the cases where Nagios can be
configured to handle problems with the server. Nagios can’t always find out
the cause of the problem but it can take some actions to resolve the issue,
and if that does not work, it can notify the admin.

1.2 Scope of Project :


The project consists of setting up Nagios for monitoring different statistics
related to the server like RAM usage, disk usage, CPU Load, users logged

1
in, ping, etc. Also, we will set up the same services for an Institute server.

Managing the network consists error control also. Thus, in case a ser-
vice fails, it will try to resolve it by taking different actions. They can be
restarting the server, in case it crashes, removing some old files, in case the
disk becomes full, killing or restarting some processes/daemons, which may
be affecting the server performance. And finally, we can block traffic from
some ports in case the server is getting too many requests.

2 Use cases :
2.1 System Admin :
2.1.1 Monitoring health of server :
1. Brief Description : The admin can view graphs and statistics related
to health of the server.

2. Initial step-by-step Description:

(a) Nagios runs on the admin machine and maintains graphs/data


related to services running on different servers.
(b) Admin can use ip of the nagios machine and view different
graphs/data.

2.1.2 Detecting problem with server :


1. Brief Description : Whenever the service goes into critical/warning
state, the problem can be reported.

2. Step-by-step Description:

(a) Services written in Nagios can have different thresholds for criti-
cal/warning state(as per the needs).
(b) When the critical/warning state is reached, Nagios will try to
take different actions to correct the problem. This will be done
by executing scripts on the server through NRPE.
(c) If the error persists, the admin may be contacted through e-mail.
(d) The e-mail will contain data about service that failed and different
statistics related to it.

2
3 Description of actions to resolve problems:
In case a critical/warning state is reached, the NRPE plugin of Nagios
tries to perform one of the following actions:

1. Restarting the server: In case is server crashes, it can be restarted and


then checked if the problem persists.

2. Remove files : In case the disk has more than x% storage occupied,
older/redundant files can be removed. These files can be those in tmp
folder or older content from log files. Thus freeing disk usage.

3. Block ports : If the number of requests are too many, and the server
CPU load is above critical/warning, nagios can block the ports of the
server for some time through NRPE.

4 References :
1. NRPE - Nagios Remove Plugin Extractor

2. Nagios Core documentation

3. NRPE Documentation

You might also like