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

[eloyd]

The reason for doing the 1.1.5 upgrade however was to have a machine that we could use to demonstrate to a customer that this is a viable upgrade path. So if it doesn't work on our machine we don't expect it to work on their machine. Which is a problem.

[danderson]

You could try following the same strategy by adding the conflicting package to the .pref file. So you would, in total, add the following:

Code: Select all

Package: libzstd1
Pin: origin "deb.debian.org"
Pin-Priority: 700

Package: libopenjp2-7
Pin: origin "deb.debian.org"
Pin-Priority: 700

I wouldn't say this is officially supported, but it did allow the fullinstall to complete for me. I would definitely upgrade to 2024R1.2.1 afterwards though.

[eloyd]

Thanks. Will try tomorrow. Definitely upgrading is the end goal, but we have to prove viability at all versions for this customer to satisfy their security requirements. Stupid government contracts.

[Aliyaa]

Helpful discussion showing real-world Nagios issues in government setups and how practical configuration advice can solve them efficiently. Shala Darpan