Nagios Support Forum

Greetings,

I am running NagiosXI 5.8.6 on a RHEL 8 server (4.18.0-348.el8.x86_64)

After performing a yum upgrade, every one of my Windows server checks turned red. (Return code of 127 is out of bounds. Check if plugin exists)

Since they were green before I performed the upgrade, I assumed they existed, unless there is some type of horrible new RHEL "feature" that upgrades Windows when I do a yum . . . anything.

I rolled back the snapshot (smart of me) and started upgrading individual packages. The package that is breaking NCPA is;

python36-3.6.8-38.module+el8.5.0+12207+5c5719bc.x86_64
or
chkconfig -1.19.1-1.el8.x86_64 (dependency)

As an added bonus, this system is in a disconnected (completely) network. I have to sneaker-net everything in for any upgrade, or package addition.

I am hoping the problem is something stupid I'm doing, but I am not familiar enough with XI to be able to find where the problem can be, so any help would be greatly appreciated.

Thank you, in advance,


Darryl

Hi Darryl,

Always wise to have a snapshot : ). It may be the case that the python update is changing the softlink to the python interpreter.

Can you run the following so we can get a look at how the soft links are setup for python ?
Thanks and Best Regards,
Keith

Keith,

I am not quite that wise. I had to roll back to a snapshot from before I fixed a bunch of of things, because I forgot to create a new one. Another lesson re-learned.

Here is my long list of python files:

[root@muce-nag-01 ~]# ls -laF /usr/bin/python*
lrwxrwxrwx. 1 root root 16 Nov 17 12:55 /usr/bin/python -> /usr/bin/python3*
lrwxrwxrwx. 1 root root 25 Nov 17 12:54 /usr/bin/python3 -> /etc/alternatives/python3*
lrwxrwxrwx. 1 root root 31 Jun 7 2019 /usr/bin/python3.6 -> /usr/libexec/platform-python3.6*
lrwxrwxrwx. 1 root root 32 Jun 7 2019 /usr/bin/python3.6m -> /usr/libexec/platform-python3.6m*

The only one that loops back to another end is /etc/alternatives/python3*, and it is:

lrwxrwxrwx. 1 root root 25 Nov 17 12:54 /etc/alternatives/python3* -> /usr/bin/python3.6

Doing an "rpm -qa |grep python3" reveals (amongst other things):

python36-3.6.8-2.module+e18.1.0+3334+5cb623d7.x86_64

It looks right to me, but I have been known to miss a thing or two.

Thank you, very much, for your help,


Darryl

Hi Darryl,

I do that most of (all) the time as well. So the link path looks like:

/usr/bin/python -> /usr/bin/python3* -> /etc/alternatives/python3* -> /usr/bin/python3.6 -> /usr/libexec/platform-python3.6

Sometimes the /usr/bin/python link gets removed or is left pointing to the old binary during upgrade; a few distributions/packages still have dependencies on python2 and the handling of the link can vary. So when you add those two packages back in (after taking a fresh snapshot) one of the things you'll want to do is take take a look and make sure the link is there and the link path points to the correct binary. You can also verify the interpreter is working by invoking it as it's called in most of our scripts:


If this fails and you can tolerate a few minutes to generate and offload a system profile it would be helpful for further troubleshooting. You can PM it to me or it may also be preferable to open a formal ticket so our team can discuss your configuration in more detail.

Login to the Nagios XI GUI using a web browser.
Click the "Admin" (Top) -> "System Profile" Menu (Left)
Click the "Download Profile" button


Thanks and Best Regards,
Keith

Keith,

You were right. I was blinded by the Python3 part of it, and totally missed the python pointer being removed.

I am fat, dumb and happy, now! Thank you, very much! It is greatly appreciated.

I do love the product (core) and my management loves the pretty, so everyone is all in on NagiosXI.

Thank you, again,


Darryl

Hi Darryl,

We're glad to hear you got it working -- it's not an intuitive problem and manifests inconsistently. Sometimes the link is set "properly" for the system and sometimes not.

Good luck with your XI rollout and please feel free to reach out if you have any more questions or encounter problems.

Thanks and Best Regards,
Keith