Failed to load module '/opt/omd/versions/2.0.0p4.cfe/lib/mk-livestatus/livestatus.o'

Hi,

I am running thruk 2.42.2 on CentOS Linux release 8.3.2011. The details are as below.

#rpm -qa | grep thruk
thruk-plugin-reporting-2.42.2-10942.1.x86_64
libthruk-2.40-0.x86_64
thruk-2.42.2-10942.1.x86_64
thruk-base-2.42.2-10942.1.x86_64
#

#/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

Nagios Core 4.4.6
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 2020-04-28
License: GPL

Website: https://www.nagios.org
Reading configuration data…
Read main config file okay…
Read object config files okay…

Running pre-flight check on configuration data…

Checking objects…
Checked 8 services.
Checked 1 hosts.
Checked 1 host groups.
Checked 0 service groups.
Checked 1 contacts.
Checked 1 contact groups.
Checked 24 commands.
Checked 5 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths…
Checked 1 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 5 timeperiods
Checking global event handlers…
Checking obsessive compulsive processor commands…
Checking misc settings…

Total Warnings: 0
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check

I have enabled broker_module in /usr/local/nagios/etc/nagios.cfg. while restarting nagios service I am encountering the Error: Failed to load module. Details are as below.

broker_module=/opt/omd/versions/2.0.0p4.cfe/lib/mk-livestatus/livestatus.o /var/tmp/live.sock

# systemctl status nagios
● nagios.service - Nagios Core 4.4.6
   Loaded: loaded (/usr/lib/systemd/system/nagios.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2021-05-18 19:06:26 UTC; 6s ago
     Docs: https://www.nagios.org/documentation
  Process: 199308 ExecStopPost=/bin/rm -f /usr/local/nagios/var/rw/nagios.cmd (code=exited, status=0/SUCCESS)
  Process: 199300 ExecStart=/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
  Process: 199298 ExecStartPre=/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
 Main PID: 199302 (code=exited, status=1/FAILURE)

May 18 19:06:24 nagios nagios[199302]: wproc: Successfully registered manager as @wproc with query handler
May 18 19:06:24 nagios nagios[199302]: wproc: Registry request: name=Core Worker 199306;pid=199306
May 18 19:06:24 nagios nagios[199302]: wproc: Registry request: name=Core Worker 199303;pid=199303
May 18 19:06:24 nagios nagios[199302]: wproc: Registry request: name=Core Worker 199304;pid=199304
May 18 19:06:24 nagios nagios[199302]: wproc: Registry request: name=Core Worker 199305;pid=199305
May 18 19:06:24 nagios nagios[199302]: Error: Could not load module '/opt/omd/versions/2.0.0p4.cfe/lib/mk-livestatus/livestatus.o' -> /opt/omd/versions/2.0.0p4.cfe/lib/mk-livestatus/livestatus.o: cannot >
May 18 19:06:24 nagios nagios[199302]: Error: Failed to load module '/opt/omd/versions/2.0.0p4.cfe/lib/mk-livestatus/livestatus.o'.
May 18 19:06:24 nagios nagios[199302]: Error: Module loading failed. Aborting.
May 18 19:06:24 nagios systemd[1]: nagios.service: Main process exited, code=exited, status=1/FAILURE
May 18 19:06:26 nagios systemd[1]: nagios.service: Failed with result 'exit-code'.

Please guide. Thanks in Advance.

Best Regards,

Kaushal

You cannot load the livestatus broker module from a checkmk 2.0 installation into a separately installed Nagios 4.4

Hi,
I’ve got a standalone nagios and epel-installed livestatus running… 1.4
adding sites running omd with livestatus are perfectly added in cmk2.0 but the ones running that 1.4 version and standalone nagios are not.
So basically, a ditributed monitoring setup without OMD.

you say, it is not possible? but there must be a way, no?
Is there no livestatus 2.0 available? (or 1.6, because aparently, if ran via omd, those are mappable to)

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.