Help? 'service nagios start' locks up on Fedora 18

[Blatwurst]

Greetings,

I have installed Nagios 4.0.3rc1 on Fedora 18. I've done so following this guide:

http://nagios.sourceforge.net/docs/3_0/ ... edora.html

Everything goes as expected, right up to where I try to start Nagios. Then I get:

[admin@monitor ~]$ sudo service nagios start
Starting nagios (via systemctl):

And the prompt locks up with the cursor at the end of the second line above.

After this, Nagios seems to be running fine. I can get to the web interface and log in, and the GUI seems to be operational. I'm just using Nagios for the first time, and I haven't gotten far yet, so I don't know if it's REALLY working, but it seems to be. But having the 'service' call lock up is troubling. I wonder what effects this will have on administration down the line, if this will cause a problem on reboot, and also wonder if all parts of Nagios have actually started.

I see no clues in either the nagios.log file or /var/log/messages. I've googled around, and saw some suggestions that restarting rsyslog might resolve a similar problem, but that doesn't help in my case. Nor does restarting the box (I haven't set nagios to start on bootup yet).

Can anyone tell me what's going on here and how to fix this? TIA for any help.

[slansing]

Do you run into the same issue when you start it as the root user? Does this fedora install have a GUI/frontend installed on it?

[Blatwurst]

Logging in as root vs using 'sudo' doesn't change anything. This install does not have a GUI on it. It's a fairly generic Fedora server install.

I didn't think before to run a 'status' on the failed start. Here's what I get when I do so, after the start attempt has timed out:

[admin@monitor nagios-4.0.2]$ sudo service nagios status
nagios.service - LSB: start and stop Nagios monitoring server
Loaded: loaded (/etc/rc.d/init.d/nagios)
Active: failed (Result: timeout) since Mon 2014-02-17 12:03:48 PST; 39min ago
Process: 19489 ExecStop=/etc/rc.d/init.d/nagios stop (code=exited, status=0/SUCCESS)
Process: 19712 ExecStart=/etc/rc.d/init.d/nagios start (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/nagios.service
├─19665 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
├─19667 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
├─19668 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
├─19669 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
├─19670 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
└─19671 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

Feb 17 11:58:48 monitor.vpc3.ftaws.net nagios[19712]: nagios (pid 19671 19670 19669 19668 19667 19665) is running...
Feb 17 11:58:48 monitor.vpc3.ftaws.net systemd[1]: PID file /var/nagios/nagios.pid not readable (yet?) after start.
Feb 17 12:03:48 monitor.vpc3.ftaws.net systemd[1]: nagios.service operation timed out. Terminating.
Feb 17 12:03:48 monitor.vpc3.ftaws.net systemd[1]: Failed to start LSB: start and stop Nagios monitoring server.
Feb 17 12:03:48 monitor.vpc3.ftaws.net systemd[1]: Unit nagios.service entered failed state.

[slansing]

Hmm, looks like this was an upgrade from 4.0.2 correct? At least the host name of your system says that. Was it working fine before? Have you tried the following?:

Code: Select all

killall -9 nagios

service nagios start

Does nagios start properly when using just the init script?:

Code: Select all

/etc/rc.d/init.d/nagios/restart