Nagios Service not starting

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Post Reply
greenman123
Posts: 7
Joined: Thu Mar 26, 2020 3:54 am

Nagios Service not starting

Post by greenman123 »

Hi,

For some reason the nagios service is not starting, meaning the website is down.

RHEL9

Code: Select all

systemctl status nagios
× nagios.service - Nagios Core 4.4.13
     Loaded: loaded (/usr/lib/systemd/system/nagios.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Tue 2024-07-02 08:37:22 BST; 15s ago
   Duration: 11ms
       Docs: https://www.nagios.org/documentation
    Process: 3127 ExecStartPre=/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
    Process: 3128 ExecStart=/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
    Process: 3148 ExecStopPost=/bin/rm -f /usr/local/nagios/var/rw/nagios.cmd (code=exited, status=0/SUCCESS)
   Main PID: 3129 (code=exited, status=1/FAILURE)
        CPU: 158ms

Jul 02 08:37:20 clancy nagios[3127]:         Checked 0 service dependencies
Jul 02 08:37:20 clancy nagios[3127]:         Checked 0 host dependencies
Jul 02 08:37:20 clancy nagios[3127]:         Checked 49 timeperiods
Jul 02 08:37:20 clancy nagios[3127]: Checking global event handlers...
Jul 02 08:37:20 clancy nagios[3127]: Checking obsessive compulsive processor commands...
Jul 02 08:37:20 clancy nagios[3127]: Checking misc settings...
Jul 02 08:37:20 clancy nagios[3127]: Total Warnings: 2701
Jul 02 08:37:20 clancy nagios[3127]: Total Errors:   0
Jul 02 08:37:20 clancy nagios[3127]: Things look okay - No serious problems were detected during the pre-flight check
Jul 02 08:37:22 clancy systemd[1]: nagios.service: Failed with result 'exit-code'.

I've run 'journalctl -xe' and get a successful output:

Code: Select all

░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit session-178.scope has successfully entered the 'dead' state.
Jul 02 08:32:01 clancy systemd[1]: session-174.scope: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit session-174.scope has successfully entered the 'dead' state.
Jul 02 08:32:01 clancy systemd[1]: session-179.scope: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit session-179.scope has successfully entered the 'dead' state.
Jul 02 08:32:01 clancy CROND[2726]: (nagios) CMDEND (/usr/bin/php -q /usr/local/nagiosxi/cron/eventman.php >> /usr/local/nagiosxi/var/eventman.log 2>&1)
Jul 02 08:32:01 clancy systemd[1]: session-181.scope: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit session-181.scope has successfully entered the 'dead' state.
Jul 02 08:32:01 clancy systemd[1]: session-182.scope: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit session-182.scope has successfully entered the 'dead' state.
Jul 02 08:32:01 clancy systemd[1]: session-180.scope: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit session-180.scope has successfully entered the 'dead' state.
Jul 02 08:32:01 clancy systemd[1]: session-176.scope: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit session-176.scope has successfully entered the 'dead' state.
Jul 02 08:32:01 clancy systemd[1]: session-177.scope: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit session-177.scope has successfully entered the 'dead' state.
Jul 02 08:32:01 clancy systemd[1]: session-175.scope: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit session-175.scope has successfully entered the 'dead' state.
Jul 02 08:32:01 clancy CROND[2765]: (nagios) CMD (/usr/bin/php -q /usr/local/nagiosxi/cron/sysstat.php >> /usr/local/nagiosxi/var/sysstat.log 2>&1)
Jul 02 08:32:01 clancy CROND[2728]: (nagios) CMDEND (/usr/bin/php -q /usr/local/nagiosxi/cron/sysstat.php >> /usr/local/nagiosxi/var/sysstat.log 2>&1)
Jul 02 08:32:01 clancy systemd[1]: session-183.scope: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit session-183.scope has successfully entered the 'dead' state.
Jul 02 08:32:01 clancy systemd[1]: session-184.scope: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit session-184.scope has successfully entered the 'dead' state.

What else can I check?
greenman123
Posts: 7
Joined: Thu Mar 26, 2020 3:54 am

Re: Nagios Service not starting

Post by greenman123 »

Rolled the server back, autopatch removed a lot of services for some reason.
swolf

Re: Nagios Service not starting

Post by swolf »

Hi @greenman123, thanks for reaching out!

I'm glad to hear your server is working again. If this happens again, I'd recommend looking at /usr/local/nagios/var/nagios.log. If you have an automated system that removes a lot of files, you might not be able to resolve it directly, but it should give an indication of why the monitoring engine is refusing to start.

Feel free to let me know if you have any further questions or concerns.

-Sebastian
Post Reply