error:1408F10B:SSL while updating to 2024R1.3.4

[steph007]

Hi,

After updating from 2024R1.3.3 to 2024R1.3.4, I go this error at the end. Is it normal?

Total Warnings: 0
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check
> Return Code: 0
--------------------------------------
error:1408F10B:SSL routines:ssl3_get_record:wrong version number
Checking php.ini defaults...
Checking max_execution_time for PHP in /etc/php.ini...
Checking max_input_time for PHP in /etc/php.ini...
Checking max_input_vars for PHP in /etc/php.ini...
Checking memory_limit for PHP in /etc/php.ini...
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.

Nagios XI Upgrade Complete!
---------------------------

You can access the Nagios XI web interface by visiting:
http://10.255.208.16/nagiosxi/

[steph007]

The system look good after the update, but I wondering if I will not have issues later

[jmichaelson]

Could you show a few dozen lines prior to this in the log file? I'm trying to figure out what the previous step in the process is that's leading up to this.

[steph007]

Sure:

--- ccm_export.php -------------------
> Writing CCM configuration to Nagios files
Finished writing out configuraton
--------------------------------------

--------------------------------------
> Verifying configuration with Nagios Core
> Output:
Nagios Core 4.5.3
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 2024-06-11
License: GPL

Website: https://www.nagios.org
Reading configuration data...
Read main config file okay...
Read object config files okay...

Running pre-flight check on configuration data...

Checking objects...
Checked 25 services.
Checked 4 hosts.
Checked 1 host groups.
Checked 1 service groups.
Checked 9 contacts.
Checked 4 contact groups.
Checked 193 commands.
Checked 18 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 4 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 18 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check
> Return Code: 0
--------------------------------------

[DoubleDoubleA]

Hi @steph007,

From what I can tell from googling that error, you likely have a mismatch or misconfiguration somewhere on your system.

Knowing what I know about the nature of the update from 1.3.3 to 1.3.4, the chance that this error has to do with the update is very small.

Perhaps you have a cert mismatch or apache misconfiguration somewhere. Have you changed anything with your certs or ssl configurations lately?

Some threads:

viewtopic.php?t=62095

viewtopic.php?t=62563