You are reading the documentation for Statusengine 3.x - Switch to Version 2.x for old stable

Install Naemon Core on Ubuntu Bionic 18.04

Related topics:

Prepare your system

In this how to, we are going to install all files to /opt/naemon.

If you want to delete Naemon Core, just remove this folder and the systemd config.

All commands needs to run as user root or via sudo.

addgroup --system naemon
adduser --system naemon
adduser naemon naemon

Install dependencies

apt-get update
apt-get install build-essential automake gperf help2man libtool libglib2.0-dev

Download and install Naemon Core

Naemon ≥ 1.0.7 required

Ubuntu Bionic comes with GCC 7 by default. For this reason only Naemon ≥ 1.0.7 can be build on Ubuntu Bionic.

Check for new versions

In this how to I use Naemon 1.1.0. Check if there is a new version available!

cd /tmp/
tar xfv v1.1.0.tar.gz
cd naemon-core-1.1.0/

./ --prefix=/opt/naemon --with-naemon-user=naemon --with-naemon-group=naemon --with-pluginsdir=/usr/lib/nagios/plugins
make all
make install

mkdir -p /opt/naemon/var/
mkdir -p /opt/naemon/var/cache/naemon
mkdir -p /opt/naemon/var/spool/checkresults
chown naemon:naemon /opt/naemon/var -R

mkdir /opt/naemon/etc/naemon/module-conf.d
chown naemon:naemon /opt/naemon/etc -R

Start Naemon Core (through systemd - recommended)

Due to I had some issues using the default Naemon systemd service configuration I modified the original a bit.

Copy the following to the file /lib/systemd/system/naemon.service using your favorite editor.


If you want to use Naemon with the Statusengine Broker Module, it is required that the Gearman Job Server is running, BEFORE your Naemon gets started!
So you need to make sure that systemd will start the Gearman Job Server first.
To configure this, replace the AFTER= line in the following systemd configuration with this: gearman-job-server.service
If not already done, install the Gearman Job Server now!
apt-get install gearman-job-server

Description=Naemon Monitoring Daemon

ExecStartPre=/opt/naemon/bin/naemon --verify-config /opt/naemon/etc/naemon/naemon.cfg
ExecStart=/opt/naemon/bin/naemon --daemon /opt/naemon/etc/naemon/naemon.cfg
ExecReload=/bin/kill -HUP $MAINPID


systemctl daemon-reload
systemctl start naemon

Now you can check if your Naemon Core is running using systemctl status naemon:

root@bionic:/tmp/naemon-core-1.1.8# systemctl status naemon
● naemon.service - Naemon Monitoring Daemon
   Loaded: loaded (/lib/systemd/system/naemon.service; disabled; vendor preset: enabled)
   Active: active (running) since Wed 2018-08-29 11:06:15 UTC; 4s ago
  Process: 17807 ExecStart=/opt/naemon/bin/naemon --daemon /opt/naemon/etc/naemon/naemon.cfg (code=exited, status=0/SUCCESS)
  Process: 17804 ExecStartPre=/opt/naemon/bin/naemon --verify-config /opt/naemon/etc/naemon/naemon.cfg (code=exited, status=0/SUCCESS)
 Main PID: 17809 (naemon)
    Tasks: 6 (limit: 1152)
   CGroup: /system.slice/naemon.service
           ├─17809 /opt/naemon/bin/naemon --daemon /opt/naemon/etc/naemon/naemon.cfg
           ├─17810 /opt/naemon/bin/naemon --worker /opt/naemon/var/naemon.qh
           ├─17812 /opt/naemon/bin/naemon --worker /opt/naemon/var/naemon.qh
           ├─17813 /opt/naemon/bin/naemon --worker /opt/naemon/var/naemon.qh
           ├─17814 /opt/naemon/bin/naemon --worker /opt/naemon/var/naemon.qh
           └─17820 /opt/naemon/bin/naemon --daemon /opt/naemon/etc/naemon/naemon.cfg

Aug 29 11:06:15 bionic naemon[17804]:         Checked 0 service dependencies
Aug 29 11:06:15 bionic naemon[17804]:         Checked 0 host dependencies
Aug 29 11:06:15 bionic naemon[17804]:         Checked 5 timeperiods
Aug 29 11:06:15 bionic naemon[17804]: Checking global event handlers...
Aug 29 11:06:15 bionic naemon[17804]: Checking obsessive compulsive processor commands...
Aug 29 11:06:15 bionic naemon[17804]: Checking misc settings...
Aug 29 11:06:15 bionic naemon[17804]: Total Warnings: 0
Aug 29 11:06:15 bionic naemon[17804]: Total Errors:   0
Aug 29 11:06:15 bionic naemon[17804]: Things look okay - No serious problems were detected during the pre-flight check
Aug 29 11:06:15 bionic systemd[1]: Started Naemon Monitoring Daemon.

To make sure that you Naemon will start automatically on boot, you need to enable the systemd configuration:

systemctl enable naemon.service

Install Monitoring Plugins

By default, Naemon will install a sample config with some basic checks. So you need to install the monitoring plugins to get them to work.

apt-get install monitoring-plugins

Setup Logrotate

To avoid, that the size of your naemon.log grows up in the sky you should configure the logrotate daemon.

Modify the file /opt/naemon/etc/logrotate.d/naemon until it fulfill your needs.

Than copy it to /etc/logrotate.d/ to enable the configuration

Congrats! You installed Naemon Core!

Load Statusengine Broker Module

Now you are ready to install and load the Statusengine Broker Module.

Start Naemon in foreground (expert or debugging)

For some reasons it can be useful to run Naemon in foreground.

You can do this with this command /opt/naemon/bin/naemon /opt/naemon/etc/naemon/naemon.cfg

root@bionic:/opt/naemon# sudo -u naemon /bin/bash
naemon@bionic:/opt/naemon$ /opt/naemon/bin/naemon /opt/naemon/etc/naemon/naemon.cfg

Naemon Core 1.1.0.source
Copyright (c) 2013-present Naemon Core Development Team and Community Contributors
Copyright (c) 2009-2013 Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
License: GPL

Naemon 1.1.0.source starting... (PID=17851)
Local time is Wed Aug 29 11:07:43 UTC 2018
qh: Socket '/opt/naemon/var/naemon.qh' successfully initialized
nerd: Channel hostchecks registered successfully
nerd: Channel servicechecks registered successfully
nerd: Fully initialized and ready to rock!
Successfully launched command file worker with pid 17856
^CCaught 'Interrupt', shutting down...
Successfully shutdown... (PID=17851)
Event broker module 'NERD' deinitialized successfully.
Successfully reaped command worker (PID = 17856)