Nagios 2024R1.1.5 -> R1.2 upgrade failed (Can't locate mysql headers)

[eloyd]

Ruh-roh!

Code: Select all

UPGRADE: Nagios Plugins upgraded OK.
UPGRADE: NDO is being upgraded...
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for a BSD-compatible install... /usr/bin/install -c
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for stdlib.h... (cached) yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for string.h... (cached) yes
checking mysql/mysql.h usability... no
checking mysql/mysql.h presence... no
checking for mysql/mysql.h... no
configure: error: Can't locate mysql headers

This was starting from a relatively pristine 2024R1.1.5 install on Ubuntu 22.04.4 LTS, downloading the tarball and running ./upgrade from the command line as root. Something we do almost every day for many, many, many customers.

Unfortunately, this has also left our Nagios box in an unusable state, since the core engine won't start and throws Seg faults in the log:

Code: Select all

[1723641477] Successfully launched command file worker with pid 3524684
[1723641477] NDO-3: Ended contact_status thread
[1723641477] Caught SIGSEGV, shutting down...
[1723641477] Caught SIGTERM, shutting down...

Bad Nagios XI. Bad! Need to restore at this point and can only hope our customers haven't hit the "upgrade" button yet.

[danderson]

Thanks for reaching out @eloyd,

Can you check to see if this package is installed?
https://ubuntu.pkgs.org/22.04/ubuntu-ma ... 4.deb.html

You may have to run ldconfig to make sure the headers can be found.

[danderson]

Okay, I see, that package isn't installed because it's dependency conflicts with one required by chromium, which comes from debian. This issue is noted and I'll try to find a fix for it.

[eloyd]

Chromium is the problem for 99.05% of our complaints in life. Including the 2024R1.1.5 install on a new box (see some other note regarding that in these forums).

[danderson]

It's a hard situation, because chromium on ubuntu is installed as a snap, and snap doesn't let users without "/home" in their home directory use snaps. Which is unfortunate because apache has a home directory of "/var/www/html". I am actively looking into a resolution and I'll keep you updated.

[eloyd]

Yah. We have some synthetic web transactions that use Chromium and we have a million things to clean up every time because the /tmp/snap... directories don't get cleaned up properly. I hate snap.

[danderson]

I hate snap!

[gouldwp]

Any updates on this? I am having the same issue.

[DoubleDoubleA]

Hi @gouldwp,

We will be releasing a patch for this hopefully early next week.

Aaron

[gouldwp]

Was a patch or new version released?