Nagios Support Forum

Hi everybody,

I'm trying to install Nagios Core 4.0, presently nagios is installed and my Web page appear but I'm not able to monitor anything because I have a problem with nagios service.

In sudo mode terminal I type service nagios start but each time I receive this error message and I'm not able to resolve this situation.

superviseur-nagios:/usr/local/nagios/bin # service nagios start
Job for nagios.service failed. See 'systemctl status nagios.service' and 'journalctl -n' for details.

There's somebody who can help me about this problem?

Thanks

What version of linux are you installing to? Can you run "systemctl status nagios.service" and "journalctl -n" after trying to start the service, and provide us the output please.

Hi,

I installed Linux SUSE 12.3, I can run systemctl status nagios and journalctl -n.

There is the answer when I run systemctl status nagios;

superviseur-nagios:/home/nagios # systemctl status nagios.service
nagios.service - LSB: start and stop Nagios monitoring server
Loaded: loaded (/etc/init.d/nagios)
Active: failed (Result: exit-code) since Fri, 2013-10-18 07:39:05 EDT; 18s ago
Process: 1660 ExecStart=/etc/init.d/nagios start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/nagios.service

Oct 18 07:39:05 superviseur-nagios.entqmd systemd[1]: Starting LSB: start and stop Nagios monitoring server...
Oct 18 07:39:05 superviseur-nagios.entqmd nagios[1660]: /etc/init.d/nagios: line 20: /etc/rc.d/init.d/functions: No such file or directory
Oct 18 07:39:05 superviseur-nagios.entqmd systemd[1]: Failed to start LSB: start and stop Nagios monitoring server.
Oct 18 07:39:05 superviseur-nagios.entqmd systemd[1]: Unit nagios.service entered failed state

There is the answer when I run journalctl -n;

-- Logs begin at Fri, 2013-10-18 07:28:57 EDT, end at Fri, 2013-10-18 07:40:55 EDT. --
Oct 18 07:39:05 superviseur-nagios.entqmd nagios[1660]: /etc/init.d/nagios: line 20: /etc/rc.d/init.d/functions: No such file or directory
Oct 18 07:39:05 superviseur-nagios.entqmd systemd[1]: nagios.service: control process exited, code=exited status=1
Oct 18 07:39:05 superviseur-nagios.entqmd systemd[1]: Failed to start LSB: start and stop Nagios monitoring server.
Oct 18 07:39:05 superviseur-nagios.entqmd systemd[1]: Unit nagios.service entered failed state
Oct 18 07:39:17 superviseur-nagios.entqmd kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=33:33:00:00:00:fb:00:00:aa:dc:ce:81:86:dd SRC=fe80:0000:0000:0000aaff:fedc:ce81 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=208 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=168
Oct 18 07:39:47 superviseur-nagios.entqmd kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=33:33:00:00:00:fb:00:00:aa:dc:ce:81:86:dd SRC=fe80:0000:0000:0000aaff:fedc:ce81 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=201 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=161
Oct 18 07:39:56 superviseur-nagios.entqmd kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=33:33:00:00:00:fb:ec:35:86:0b:e9:3b:86:dd SRC=fe80:0000:0000:0000:ee35:86ff:fe0b:e93b DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=97 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=57
Oct 18 07:40:36 superviseur-nagios.entqmd kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=33:33:00:00:00:fb:ec:35:86:0b:e9:3b:86:dd SRC=fe80:0000:0000:0000:ee35:86ff:fe0b:e93b DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=97 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=57
Oct 18 07:40:38 superviseur-nagios.entqmd kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=33:33:00:00:00:fb:e0:f5:c6:95:73:62:86:dd SRC=fe80:0000:0000:000005fc:69b7:e1ba DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=240 TC=0 HOPLIMIT=255 FLOWLBL=859941 PROTO=UDP SPT=5353 DPT=5353 LEN=200
Oct 18 07:40:55 superviseur-nagios.entqmd kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=33:33:00:00:00:fb:00:00:aa:dc:ce:81:86:dd SRC=fe80:0000:0000:0000aaff:fedc:ce81 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=208 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=168
lines 1-11/11 (END)

I'm not a specialist of Linux and I'm lost with problem.

Thanks for your help.

Debian and its derivatives, and apparently suse as well, are having issues with the core init scripts. This mostly stems from the fact that there were some renaming of LSB stuff along with some changes to packages. This has broken many different package installs, not just nagios. The init script was hacked out to work on debian systems until a better init script is released from the core devs. I have no idea if the altered script will work for you, but you are having the same series of errors as the debian users, so it may be worth a try:
http://support.nagios.com/forum/viewtop ... =20#p64091
Just a heads up, the script requires the "daemon" package, though I have no idea if it is called that in suse land.

I am having this same issue running Debian 8 (Jessie) - I was able to get it working with Debian 7 but apparently not 8 -

sudo systemctl status nagios.service
● nagios.service - LSB: start and stop Nagios monitoring server
Loaded: loaded (/etc/init.d/nagios)
Active: failed (Result: resources) since Sun 2015-05-10 11:17:51 EDT; 37s ago
Process: 26251 ExecStart=/etc/init.d/nagios start (code=exited, status=0/SUCCESS)

May 10 11:17:51 otis nagios[26251]: is running.
May 10 11:17:51 otis systemd[1]: Failed to start LSB: start and stop Nagios monitoring server.
May 10 11:17:51 otis systemd[1]: Unit nagios.service entered failed state.



sudo journalctl -xn
-- Logs begin at Fri 2015-05-08 18:09:32 EDT, end at Sun 2015-05-10 11:19:49 EDT. --
May 10 11:17:51 otis sudo[26241]: pam_unix(sudo:session): session opened for user root by (uid=0)
May 10 11:17:51 otis nagios[26251]: is running.
May 10 11:17:51 otis systemd[1]: Failed to start LSB: start and stop Nagios monitoring server.
-- Subject: Unit nagios.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
--
-- Unit nagios.service has failed.
--
-- The result is failed.
May 10 11:17:51 otis systemd[1]: Unit nagios.service entered failed state.
May 10 11:17:51 otis sudo[26241]: pam_unix(sudo:session): session closed for user root
May 10 11:18:28 otis sudo[26292]: eric : TTY=pts/5 ; PWD=/usr/local/nagios ; USER=root ; COMMAND=/bin/systemctl status
May 10 11:18:28 otis sudo[26292]: pam_unix(sudo:session): session opened for user root by (uid=0)
May 10 11:18:28 otis sudo[26292]: pam_unix(sudo:session): session closed for user root
May 10 11:19:49 otis sudo[26332]: eric : TTY=pts/5 ; PWD=/usr/local/nagios ; USER=root ; COMMAND=/bin/journalctl -xn
May 10 11:19:49 otis sudo[26332]: pam_unix(sudo:session): session opened for user root by (uid=0)


I've been using nagios on my nix workstation for years and have never had so many problems.... definitely a clear case of if it ain't broke don't fix it! I got bored and decided to reload my wrkstn from scratch... what was I thinking....

I've had reasonable success with the following systemd script. It still calls the old init script so place (move) it in the location specified:

jdalrymple wrote:I've had reasonable success with the following systemd script. It still calls the old init script so place (move) it in the location specified:

Code: Select all

[Unit]
Description=Nagios Core Monitoring Daemon
After=network.target

[Service]
User=nagios
Group=nagios
Type=forking
ExecStart=/usr/lib/systemd/scripts/nagios start
ExecStop=/usr/lib/systemd/scripts/nagios stop
ExecReload=/usr/lib/systemd/scripts/nagios reload

[Install]
WantedBy=multi-user.target

I'm sorry, I'm new using linux and nagios. How do I exactly create this file and how do I execute it? should I edit a .service file with vi or nano and then systemctl enable it?

Thanks in advance.

What exactly are you trying to do?

hsmith wrote:What exactly are you trying to do?

I'm trying to create the script jdalrymple said he had reasonable success with.

You need to make a script in the following directory:
/etc/systemd/system/

For example, you might first use vim to create the file: Insert the following text into that service: Once generated, you should be capable of calling it via systemctl: