summaryrefslogtreecommitdiffstats
path: root/network/nagios/README.SLACKWARE
blob: 58c3afe45b1e84bc44a5944a4d41dfa9a4d964bd (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
README.Slackware
================

This file contains some basic instructions to get nagios installed and 
running on your computer.

0) Before running the SlackBuild Script
---------------------------------------

0.1) Create nagios group & user

Before even running the SlackBuild script, create the necessary 'nagios'
user and group. The SlackBuild script won't run if these do not exist.

The suggested UID and GID is 213, but you can change this as needed:

  # groupadd -g 213 nagios
  # useradd -u 213 -d /dev/null -s /bin/false -g nagios nagios

0.2) Add 'apache' to 'nagios' group

For several nagios scripts to run without problems, you need to add the 
'apache' user to the 'nagios' group, so that it can write to the 
/var/nagios/rw directory:

  # usermod -G nagios apache

0.3) Select DOCROOT

The standard SlackBuild script puts the nagios files in /var/www/htdocs
This is fine for a stock Slackware installation, but if your 'DOCROOT' 
lives in another directory, you can specify it when starting the SlackBuild 
script like this:

# DOCROOT=/your/docroot/dir ./nagios.SlackBuild

1) Post-installation
--------------------

After building & installing the nagios package, there are some additional 
steps to take.

1.1) Check /etc/nagios/nagios.cfg & /etc/nagios/cgi.cfg

These are the basic configuration files for the nagios server. Do read the
documentation to understand what all the different settings mean.

1.2) Edit /etc/httpd/extra/nagios.conf

To be able to view the documentation, edit this file.
After the "<Directory "/var/www/htdocs/nagios">" line, change:

	Options None

to read:

	Options FollowSymLinks

1.3) Edit /etc/httpd/httpd.conf

Now you need to add the extra/nagios.conf file as an included file. To
accomplish this, after the "DocumentRoot /srv/httpd/htdocs" line, add:

	Include /etc/httpd/extra/nagios.conf

1.4) Create access file

The /etc/httpd/extra/nagios.conf file defines /etc/nagios/htpasswd.users
as the file with the authorized users.
To create this file with a standard user called 'nagiosadmin', type:

  # htpasswd -c /etc/nagios/htpasswd.users nagiosadmin

then type the password you choose twice.

To add other users, delete users, etc., check the man page for htpasswd:

  # man htpasswd

1.5) Restart httpd

  # /etc/rc.d/rc.httpd restart

1.6) Put startup command in /etc/rc.d/rc.local:

	# Start nagios:
	if [ -x /etc/rc.d/rc.nagios ]; then
	        echo "Starting nagios..."
	        /etc/rc.d/rc.nagios start
	fi

1.7) Put shutdown command in /etc/rc.d/rc.local_shutdown:

	# Stop nagios:
	if [ -x /etc/rc.d/rc.nagios ]; then
	        echo "Stopping nagios..."
	        /etc/rc.d/rc.nagios stop
	fi

1.8) Make /etc/rc.d/rc.nagios executable:

  # chmod +x /etc/rc.d/rc.nagios

1.9) Start nagios:

  # /etc/rc.d/rc.nagios start

2) Adding hosts, routers, switches, etc.
----------------------------------------

Lot of documentation is included in this package and should be read to fully
understand how to add hosts, routers, switches, etc.

To add functionality, build & install the nagios-plugins on your server.

To monitor external Linux hosts, install the nrpe package on them, together
with the nagios-plugins.

To monitor Windows hosts, install NSClient++ on them.

Do check the http://wiki.nagios.org pages for some useful information.

3) Growing log files
--------------------

If you are monitoring several items, your log files can grow considerably.
Nagios keeps a history of all logs in /var/nagios/archives/.
After a few months this can be quite a bit of information, so consider
creating some kind of clean-up or compacting script (Left as an exercise to
the reader :) )