Debian 10 Upgrade Nagios Monitoring Engine Won't Start

[rpearson]

Are there any known issues after an OS update like this?

mwymore@mon-new:/etc/apt$ sudo systemctl status nagios
● nagios.service - Nagios Core 4.4.6
Loaded: loaded (/lib/systemd/system/nagios.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2021-01-08 14:27:00 CST; 46min ago
Docs: https://www.nagios.org/documentation
Process: 1226 ExecStartPre=/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
Process: 1236 ExecStart=/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
Process: 1657 ExecStopPost=/bin/rm -f /usr/local/nagios/var/rw/nagios.cmd (code=exited, status=0/SUCCESS)
Main PID: 1237 (code=exited, status=1/FAILURE)

Jan 08 14:26:58 mon-new nagios[1237]: wproc: Registry request: name=Core Worker 1278;pid=1278
Jan 08 14:26:58 mon-new nagios[1237]: wproc: Registry request: name=Core Worker 1282;pid=1282
Jan 08 14:26:58 mon-new nagios[1237]: wproc: Registry request: name=Core Worker 1286;pid=1286
Jan 08 14:26:58 mon-new nagios[1237]: wproc: Registry request: name=Core Worker 1284;pid=1284
Jan 08 14:26:58 mon-new nagios[1237]: wproc: Registry request: name=Core Worker 1285;pid=1285
Jan 08 14:26:58 mon-new nagios[1237]: Error: Could not load module '/usr/local/nagios/bin/ndo.so' -> file not found
Jan 08 14:26:58 mon-new nagios[1237]: Error: Failed to load module '/usr/local/nagios/bin/ndo.so'.
Jan 08 14:26:58 mon-new nagios[1237]: Error: Module loading failed. Aborting.
Jan 08 14:26:58 mon-new systemd[1]: nagios.service: Main process exited, code=exited, status=1/FAILURE
Jan 08 14:27:00 mon-new systemd[1]: nagios.service: Failed with result 'exit-code'.

The file in question very much exists, but...

mwymore@mon-new:/usr/local/nagios/bin$ ldd ndo.so
linux-vdso.so.1 (0x00007ffd1f9bb000)
libmariadbclient.so.18 => not found
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fbdfb9eb000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fbdfb7cd000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fbdfb64a000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fbdfb645000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fbdfb484000)
/lib64/ld-linux-x86-64.so.2 (0x00007fbdfbc71000)

Yeah, libmaridbclient.so.18 is gone. It should be using libmaridbclient.so instead.

[rpearson]

The engine is now starting, but Nagios XI is still reporting my last check was 2021-01-08. But if I look at the Nagios Core page it is showing that checks are happening now. What could cause the discrepancy?

[rpearson]

I also have a host in limbo through all this that cannot be deleted due to this error message.

Could not find a unique id for this host
Host cannot be deleted using this method

I have tried verifying the config and there are no errors just 2 warnings but after following the documentation I found it still persists.

[rpearson]

After following this everything seems fine now.

https://support.nagios.com/forum/viewto ... 16&t=61213

[tgriep]

Because the OS upgrade removed the libmaridbclient.so.18 library, the existing NDO3 broker stopped running and re-compiling it from the other post linked in the new library which fixed the issue.
Let us know if you have any further questions or that it is OK to lock the post.

[rpearson]

I think we are good for this issue.