This document provides a quick guide to installing and configuring Nagios for basic network monitoring. It outlines steps to install Nagios and plugins, configure monitoring of hosts, services, contacts, and the web interface. The guide explains setting up monitoring of a sample network with one monitoring host and one NFS server to check connectivity and NFS service status.
Installing and Configuring Domino 10 on CentOS 7Devin Olson
Instructions on how to do a base-level installation of IBM / HCL's Domino 10 (10.0.1) server on a Debial-based (Red Hat, CentOS, etc) Linux Server.
Includes partitioning, network configuration, ssh installation & configuration, group and user creation, minimal packages, firewall configuration, sticky bits, and more.
Introduction to Stacki at Atlanta Meetup February 2016StackIQ
An introduction to Stacki-the fastest bare metal Linux server provisioning tool from the Stacki Atlanta kickoff meetup on 2/23/16 at the Microsoft Innovation Center. Greg Bruno is the VP Engineering at StackIQ.
Installing and Configuring Domino 10 on CentOS 7Devin Olson
Instructions on how to do a base-level installation of IBM / HCL's Domino 10 (10.0.1) server on a Debial-based (Red Hat, CentOS, etc) Linux Server.
Includes partitioning, network configuration, ssh installation & configuration, group and user creation, minimal packages, firewall configuration, sticky bits, and more.
Introduction to Stacki at Atlanta Meetup February 2016StackIQ
An introduction to Stacki-the fastest bare metal Linux server provisioning tool from the Stacki Atlanta kickoff meetup on 2/23/16 at the Microsoft Innovation Center. Greg Bruno is the VP Engineering at StackIQ.
Salesforce at Stacki Atlanta Meetup February 2016StackIQ
Dave Peterson's presentation on how Salesforce uses Stacki and Chef to provision and manage thousands of servers. Stacki Atlanta kickoff Meetup on 2/23/16 at the Microsoft Innovation Center. Dave is a Lead Systems Engineer at Salesforce.
In this white-paper we will explain how one can install and configure cloud storage software and use it for backup purposes. Document can be used by an individual or a company who wishes to become a cloud backup provider and utilize its own hardware for cloud object-based storage. We will use Cloudian object-storage software along with CloudBerry Lab products.
It's presentation for technet 2015 in korea.
I changed the format to pptx,
목차는 아래와 같습니다.
Openstack 인프라 구축 (4 node 구성) [ 30분]
Openstack 위에 VM 생성 [ 20분 ]
docker 구축 기초 [ 30분]
오픈스택에 docker를 연결 [ 30분]
Docker로 WEB서비스 구축 [ 15분]
Openstack 위에 Docker로 WEB서비스 구축 [ 15분]
Docker로 jenkins 구현 [30분]
Les défis des architectures cloud sur OpenStackOsones
Les défis des architectures cloud sur OpenStack.
Démonstration par Pierre Freund
Vous êtes administrateur système, développeur, décideur, et vous vous posez des questions sur le rôle et le fonctionnement d'OpenStack ?
• Quels besoins couvrent OpenStack ?
• Quels sont les différents composants ? Comment fonctionnent-ils ?
• Comment tirer partie d'une technologie cloud ?
Ces slides sont issues du meetup du mercredi 17 septembre dans les locaux de Mozilla à Paris.
> Des projets OpenStack ? Besoin de formations OpenStack intra- / inter- entreprise ?
Contactez-nous sur http://www.osones.com
Salesforce at Stacki Atlanta Meetup February 2016StackIQ
Dave Peterson's presentation on how Salesforce uses Stacki and Chef to provision and manage thousands of servers. Stacki Atlanta kickoff Meetup on 2/23/16 at the Microsoft Innovation Center. Dave is a Lead Systems Engineer at Salesforce.
In this white-paper we will explain how one can install and configure cloud storage software and use it for backup purposes. Document can be used by an individual or a company who wishes to become a cloud backup provider and utilize its own hardware for cloud object-based storage. We will use Cloudian object-storage software along with CloudBerry Lab products.
It's presentation for technet 2015 in korea.
I changed the format to pptx,
목차는 아래와 같습니다.
Openstack 인프라 구축 (4 node 구성) [ 30분]
Openstack 위에 VM 생성 [ 20분 ]
docker 구축 기초 [ 30분]
오픈스택에 docker를 연결 [ 30분]
Docker로 WEB서비스 구축 [ 15분]
Openstack 위에 Docker로 WEB서비스 구축 [ 15분]
Docker로 jenkins 구현 [30분]
Les défis des architectures cloud sur OpenStackOsones
Les défis des architectures cloud sur OpenStack.
Démonstration par Pierre Freund
Vous êtes administrateur système, développeur, décideur, et vous vous posez des questions sur le rôle et le fonctionnement d'OpenStack ?
• Quels besoins couvrent OpenStack ?
• Quels sont les différents composants ? Comment fonctionnent-ils ?
• Comment tirer partie d'une technologie cloud ?
Ces slides sont issues du meetup du mercredi 17 septembre dans les locaux de Mozilla à Paris.
> Des projets OpenStack ? Besoin de formations OpenStack intra- / inter- entreprise ?
Contactez-nous sur http://www.osones.com
Nagios Conference 2014 - Eric Mislivec - Getting Started With Nagios CoreNagios
Eric Mislivec's presentation on getting started with Nagios Core. The presentation was given during the Nagios World Conference North America held Oct 13th - Oct 16th, 2014 in Saint Paul, MN. For more information on the conference (including photos and videos), visit: http://go.nagios.com/conference.
NRPE - Nagios Remote Plugin Executor. NRPE plugin for Nagios Core 4 and others.Marc Trimble
Nrpe - Nagios Remote Plugin Executor.
NRPE gives users the option to execute Nagios plugins remotely on any of their Linux/Unix machines. This option enables users to oversee their machine metrics, remotely, giving insights into disk usage, CPU load, etc. NRPE also allows users to interact and communicate with Windows agent add-ons. These add-ons monitor metrics and execute scripts.
https://www.nagios.com/news/2015/09/nagios-named-top-it-monitoring-tool/
Nagios is a powerful monitoring system that enables organizations to identify and resolve IT infrastructure problems before they affect critical business processes.
Quick-Start Guide: Deploying Your Cloudian HyperStore Hybrid Storage ServiceCloudian
This document will help a new user deploy a 3-node Cloudian storage cluster in your data center for use with the Cloudian HyperStore Hybrid Cloud Service from AWS Marketplace.
While probably the most prominent, Docker is not the only tool for building and managing containers. Originally meant to be a "chroot on steroids" to help debug systemd, systemd-nspawn provides a fairly uncomplicated approach to work with containers. Being part of systemd, it is available on most recent distributions out-of-the-box and requires no additional dependencies.
This deck will introduce a few concepts involved in containers and will guide you through the steps of building a container from scratch. The payload will be a simple service, which will be automatically activated by systemd when the first request arrives.
5/13/13 presentation to Austin DevOps Meetup Group, describing our system for deploying 15 websites and supporting services in multiple languages to bare redhat 6 VMs. All system-wide software is installed using RPMs, and all application software is installed using GIT or Tarball.
2. 1 Install
1.1 Copy distribution and plug in
First, you must get the latest Nagios release (nagios-x.y.tar.gz) and the official Nagios plugins
(nagios-plugins-x.y.z) from http://www.nagios.org/download/. I also advise to get the official
Nagios documentation (http://www.nagios.org/docs/) if you plan to tune the configuration explained here.
Unpack the tarball :
tar xzf nagios-2.0.tar.gz tar xzf nagios-plugins-1.4.2.tar.gz 1.2
1.2 Create user
First, we need to create the user Nagios will run under :
adduser nagios mkdir /usr/local/nagios
chown nagios.nagios /usr/local/nagios
You will probably want to issue external commands from the web interface. So you need to identify the
user your web-server run as. For Apache, you can get it with :
grep "^User" /etc/httpd/conf/httpd.conf
By default, the user is Apache. See /etc/passwd file or report to you web-server installation if you
are running another web server. Also note that the path to httpd.conf can vary depending on your
system.
We need to create a group whose members include the user your web server is running as and the user
Nagios is running as.
/usr/sbin/groupadd nagcmd
/usr/sbin/usermod -G nagcmd apache
/usr/sbin/usermod -G nagcmd nagios
Recall to replace apache by the user name you obtained at last step.
1.3 Configuration and compilation
We can now configure and install Nagios. Go to the directory where you untared the distribution and
run :
./configure --prefix=/usr/local/nagios --with-nagios-user=nagios
--with-nagios-group=nagios --with-command-group=nagios
Depending on your system, you should get a configuration like the following :
2
3. Configuration summary for nagios 2.0 02-07-2006 ***:
General Options:
————————-
Nagios executable: nagios
Nagios user/group: nagios,nagios
Command user/group: nagios,nagios
Embedded Perl: no
Event Broker: yes
Install ${prefix}: /usr/local/nagios
Lock file: ${prefix}/var/nagios.lock
Init directory: /etc/rc.d/init.d
Host OS: linux-gnu
Web Interface Options:
————————
HTML URL: http://localhost/nagios/
CGI URL: http://localhost/nagios/cgi-bin/
Traceroute (used by WAP): /bin/traceroute
Now let’s compile and install :
make all
make install
make install-init
make install-config
make install-init allows to run nagios at startup (/etc/rc.d/init.d/nagios). This does
not always work (I had problems on Fedora Core 4) but we see another way to run it at startup later on.
make install-config installs the sample configuration files. This will be useful to setup a basic
configuration.
In order for nagios to be of any use to you, you need to install some plugins. First, install the official
plugins. Go to the directory where you untared nagios-plugin-x.y.z and run :
./configure
make
make install
3
4. 2 Configuration
Normally, you should already have some configuration sample files in /usr/local/nagios/etc.
Else, try to run again make install-config. Files should be called xxxx.cfg-sample, so you
need to rename them :
cd /usr/local/nagios/etc
mv bigger.cfg-sample bigger.cfg
(...)
The entry point is through nagios.cfg. This file is run first when nagios starts. You may not need a
lot of modifications in this file.
log_file=/usr/local/nagios/var/nagios.log
indicates where the logs will go. Set the appropriate owner of the log file :
chown nagios.nagios /usr/local/nagios/var/nagios.log
Other configuration files are called from nagios.cfg, for instance at lines :
cfg_file=/usr/local/nagios/etc/checkcommands.cfg
cfg_file=/usr/local/nagios/etc/misccommands.cfg
Those files contain commands definition.
And finally, our own configuration will be written in a new file (ma_conf.cfg for instance) so we need
to replace :
cfg_file=/usr/local/nagios/etc/minimal.cfg
By :
cfg_file=/usr/local/nagios/etc/ma_conf.cfg
To create our configuration, we will take minimal.cfg as the basis :
cp minimal.cfg ma_conf.cfg
And now let’s edit it to setup a configuration for a simple network with one monitoring station and one
NFSv4 server.
2.1 Time periods
Time periods are used to define some monitoring periods. For the time being we can keep 24*7 but you
may need to change it -for instance not to receive alarms if your NFS servers are down during night.
4
5. 2.2 Contacts
You will certainly need to add some contacts, which are persons in charge of monitoring the network. By
default they will receive notification in 24*7 by e-mail.
define contact{
contact_name adminNFS
alias Jonathan Lyard
service_notification_period 24x7
host_notification_period 24x7
service_notification_options w,u,c,r
host_notification_options d,r
service_notification_commands notify-by-email
host_notification_commands host-notify-by-email
email adminNFS@localhost
}
Now let’s create a contact group. This one will be used to indicate which contacts should be notified for
each issue. Here is only one group, but feel free to add all groups you need (for instance if the ones in
charge of NFS administration are different from network administrators).
define contactgroup{
contactgroup_name admins
alias Nagios Administrators
members nagios-admin,adminNFS
}
2.3 Hosts
In addition to localhost, you must specify all hosts your are monitoring. I assume they are all on-link
(in the same LAN as your monitoring station). Else, see Nagios official documentation to get it working
through routers (use parents option).
Here is what is required in order to monitor a machine called nfs2 with IP address 192.168.0.5. Alarms
from this host will be reported to the "admins" group.
5
6. define host{
use generic-host ; Name of host template to use
host_name nfs2
alias nfs2
address 192.168.0.5
check_command check-host-alive
max_check_attempts 10
notification_interval 120
notification_period 24x7
notification_options d,r
contact_groups admins
}
2.4 Hostgroups
In this basic configuration, we will only have one hostgroup. You can define several hostgroups to group
hosts together in Nagios interface.
define hostgroup{
hostgroup_name nfsv4config
alias NFSv4 test configuration
members localhost,nfs2
}
2.5 Services
Finally, one can find services definition. Services do not necessarily mean real services that run on host
(FTP, POP, HTTP...) but also some other types of metric associated with the host (response to ping,
number of logged-in user, free disk space...).
For instance, to monitor connectivity for localhost and our nfs2 server, we need the following service
definition :
define service{
use generic-service ; Name of service template to use
host_name localhost,nfs2
6
7. service_description PING
is_volatile 0
check_period 24x7
max_check_attempts 4
normal_check_interval 5
retry_check_interval 1
contact_groups admins
notification_options w,u,c,r
notification_interval 960
notification_period 24x7
check_command check_ping!100.0,20%!500.0,60%
}
Later on, we will also define a service to monitor NFSv4.
2.6 Web server configuration
In this step, you will learn how to configure the web-server. I assume you are using Apache, but the
configuration may be similar for other web-servers. Check your own web-server’s documentation to put
it at work.
Add the following lines in httpd.conf (in general /etc/httpd/conf/httpd.conf).
ScriptAlias /nagios/cgi-bin /usr/local/nagios/sbin
Directory /usr/local/nagios/sbin
# SSLRequireSSL
Options ExecCGI
AllowOverride None
Order allow,deny
Allow from all
# Order deny,allow
# Deny from all
# Allow from 127.0.0.1
7
8. AuthName Nagios Access
AuthType Basic
AuthUserFile /usr/local/nagios/etc/htpasswd.users
Require valid-user
/Directory
Alias /nagios /usr/local/nagios/share
Directory /usr/local/nagios/share
# SSLRequireSSL
Options None
AllowOverride None
Order allow,deny
Allow from all
# Order deny,allow
# Deny from all
# Allow from 127.0.0.1
AuthName Nagios Access
AuthType Basic
AuthUserFile /usr/local/nagios/etc/htpasswd.users
Require valid-user
/Directory
This configuration enable authentication. The first directory entry is for CGI scripts, the second for html
pages. Of course, you can tune this configuration to fit your requirements.
You can also disable authentication by setting use_authentication=0 in /usr/local/nagios/etc/cgi.cfg
but then, you will not be allowed to run remote commands. Use it only if you have a problem with au-
thentication.
You now need to create one or more users being able to authenticate. For the first one (-c to create the
file htpasswd.users) :
htpasswd -c /usr/local/nagios/etc/htpasswd.users nagiosadmin
and for (possible) next users :
htpasswd /usr/local/nagios/etc/htpasswd.users nagiosadmin2
Then, you need to give some rights to the users.
8
9. You can do it by editing the file /usr/local/nagios/etc/cgi.cfg.
For instance :
authorized_for_system_information=nagiosadmin,nagiosadmin2
And so on for all line you want to grant privilege to nagiosadmin and nagiosadmin2. I have uncommented
all authorized line and give access to nagiosadmin. I advised to at least do the same if want to be able to
configure everything from the web interface.
For more details on the access rights, read the chapter "Authentication and Authorization in the CGIs" in
Nagios official documentation.
Restart your web browser to take modifications into account :
/usr/sbin/httpd -k restart
You should be able to point http://localhost in your web browser proving that your web server is
up.
You should also be able to point http://localhost/nagios/ and authenticate yourself with one
of the user created previously (htpasswd). At this time, the CGI will not works since Nagios is not
running.
3 Run Nagios
To run Nagios, you can use the following command to make it start as a foreground process:
/usr/local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg &
If make install-init failed to make Nagios run at startup you can add this command to /etc/rc.d/rc.local
(here on FC4 but path and filename can vary depending on distribution).
To check that all configuration files are alright, you can issue :
/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
Finally, a useful command to restart Nagios and therefore consider modifications in the configuration
files :
killall -SIGHUP nagios
Enjoy monitoring systems with Nagios!
Jonathan Lyard {jonathan.lyard@bull.net}
9