NagiosXI offline upgrade script issues

[brandondash]

ACK.

Just LMK if you need any additional info from me.

[gsmith]

Hey there,

I am seeing installation issues myself.

Please answer these:
1. what version of perl does perl -v show?
2. what version of php does php -v show?
3. Regarding this requirement:

Code: Select all

RHEL 7
Offline server must still have access to RHEL Base & Optional Channel Repo (actual or clone) for installation/upgrade

RHEL 7 Optional Channel Packages
dejavu-lgc-sans-fonts.noarch
dejavu-lgc-sans-mono-fonts.noarch
graphviz-gd.x86_64
perl-Crypt-DES.x86_64
perl-Parse-RecDescent.noarch
php-mbstring.x86_64
php-snmp.x86_64

I found that the RHEL 7 Optional Channel Packages were already installed.
Did you clone the RHEL Base repo locally?

Thanks

[brandondash]

Code: Select all

[root@nagios1 ~]# perl -v
This is perl 5, version 16, subversion 3 (v5.16.3) built for x86_64-linux-thread-multi
(with 41 registered patches, see perl -V for more detail)
Copyright 1987-2012, Larry Wall

Code: Select all

[root@nagios1 ~]# php -v
PHP 5.4.16 (cli) (built: Oct 29 2019 09:56:22)
Copyright (c) 1997-2013 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-2013 Zend Technologies

In our test lab we have a cloned RHEL repository.

[gsmith]

Hey there,

I was able to perform the upgrade from 5.7.3 to 5.8.4. However Nagios XI only works
properly with SELinux disabled.

With SELinux enabled I see error messages about workers not starting, files can't be found etc.

According to the dev guys we do not support running with SELinux enabled.

I am curious: How were you able to get 5.7.3 running under SELinux? Did you go through all the errors
in all the logs and make accommodations?

Thanks

[brandondash]

According to the dev guys we do not support running with SELinux enabled.

I am curious: How were you able to get 5.7.3 running under SELinux? Did you go through all the errors
in all the logs and make accommodations?

I believe I misspoke before. We have SELinux disabled at the moment because of this exact issue. If I remember correctly the /tmp issue is an unrelated STIG lockdown.

I was able to perform the upgrade from 5.7.3 to 5.8.4.

So your "out of the box" XI upgraded without issue? Was this on a STIG lockdown machine? Did you have anything implemented in your monitoring config?

[gsmith]

Hi,

I don't know much about STIG but during the install a selected a STIG security model. When I go to
login I see this:

Image4.jpg

Is there a command I can run to display what "level" of STIG I am running? Because
I am able to use the /tmp directory. Is it possible your /tmp directory is mounted with the
-noexec option?

My monitoring config was minimal - localhost basically. I do know that if there are
config errors in your existing installation they could cause an upgrade to fail.

If the /tmp business is unworkable I believe you were using something like a
/data/rpms/nagiosxi directory

Go to that directory and run:

Code: Select all

./upgrade 2>&1 | tee /data/tpms/upgrade.log

Then send me the upgrade.log, via a pm for security reasons.

Thanks

[brandondash]

Just a ping to keep the thread open. I know you are waiting for a response. I'll get it to you when possible.

[gsmith]

Hi,

No worries... I'll be here. I don't think the threads "auto-lock" due to inactivity, but if it
does I can always re-open it.

Thanks