Nagios Support Forum

Performed upgrade from 2012R2.9 to NagiosXI 5.4.0 and now the monitoring engine is not running. If you click on restart, it says command submitted successfully. Audit log has no logged errors. The engine does not start.

Any help would be very appreciated.

Thank you.
Lansol

@lansol

What os are you on? Please prepare your system profile, Nagios support will probably ask for it.

Are you using a ramdisk? Somewhere around 5.3 there was an upgrade which changed some stuff in the way the ramdisk was initialized. If so I think this thread has some extra info: https://support.nagios.com/forum/viewto ... sk#p199715

Grt

Hello,

The system is:
Nagios XI Version : 5.4.0
2.6.32-642.13.1.el6.i686 i686
CentOS release 6.8 (Final)
Gnome Installed

I was looking at the log and below is last few lines if its any indicative:
[1484863769] Nagios 4.2.4 starting... (PID=19477)
[1484863769] Local time is Thu Jan 19 17:09:29 EST 2017
[1484863769] LOG VERSION: 2.0
[1484863769] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
[1484863769] qh: core query handler registered
[1484863769] nerd: Channel hostchecks registered successfully
[1484863769] nerd: Channel servicechecks registered successfully
[1484863769] nerd: Channel opathchecks registered successfully
[1484863769] nerd: Fully initialized and ready to rock!
[1484863769] wproc: Successfully registered manager as @wproc with query handler
[1484863769] wproc: Registry request: name=Core Worker 19479;pid=19479
[1484863769] wproc: Registry request: name=Core Worker 19480;pid=19480
[1484863769] wproc: Registry request: name=Core Worker 19484;pid=19484
[1484863769] wproc: Registry request: name=Core Worker 19482;pid=19482
[1484863769] wproc: Registry request: name=Core Worker 19483;pid=19483
[1484863769] wproc: Registry request: name=Core Worker 19481;pid=19481
[1484863769] Error: Could not load module '/usr/lib/check_mk/livestatus.o' -> /usr/lib/check_mk/livestatus.o: undefined symbol: last_command_check
[1484863769] Error: Failed to load module '/usr/lib/check_mk/livestatus.o'.
[1484863769] ndomod: NDOMOD 2.1.2 (11-14-2016) Copyright (c) 2009 Nagios Core Development Team and Community Contributors
[1484863769] ndomod: Successfully connected to data sink. 0 queued items to flush.
[1484863769] ndomod registered for process data
[1484863769] ndomod registered for log data'
[1484863769] ndomod registered for system command data'
[1484863769] ndomod registered for event handler data'
[1484863769] ndomod registered for notification data'
[1484863769] ndomod registered for comment data'
[1484863769] ndomod registered for downtime data'
[1484863769] ndomod registered for flapping data'
[1484863769] ndomod registered for program status data'
[1484863769] ndomod registered for host status data'
[1484863769] ndomod registered for service status data'
[1484863769] ndomod registered for adaptive program data'
[1484863769] ndomod registered for adaptive host data'
[1484863769] ndomod registered for adaptive service data'
[1484863769] ndomod registered for external command data'
[1484863769] ndomod registered for aggregated status data'
[1484863769] ndomod registered for retention data'
[1484863769] ndomod registered for contact data'
[1484863769] ndomod registered for contact notification data'
[1484863769] ndomod registered for acknowledgement data'
[1484863769] ndomod registered for state change data'
[1484863769] ndomod registered for contact status data'
[1484863769] ndomod registered for adaptive contact data'
[1484863769] Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully.
[1484863769] Error: Module loading failed. Aborting.

Thank you.

I believe the issue is here - We're unable to support livestatus as it isn't our product. I have heard of customers running it, and your issue may be that you just need to recompile it, but again, this isn't something that we can help with. There is a thread from one of our community members, Steve, which you may find useful here - https://support.nagios.com/forum/viewto ... 07#p209307

Hello,

The link worked and the issue is resolved. GCC package had to be upgraded but once done, the instructions worked perfectly.

Many thanks.

Awesome - going to close this one up!

Feel free to create a new thread if you have questions in the future.