Good morning,
We have made an update from nagios 5.8.9 to 5.10.0. It is observed that the following error is observed in the ssl_error_log file:
[Fri May 26 12:14:26.429061 2023] [:error] [pid 13463] [client 10.8.198.61:57125] PHP Notice: DB is not connected in /usr/local/nagiosxi/html/includes/db.inc.php on line 397, referer: https://guardian01.central.sepg.minhac. ... en/noc.php
[Fri May 26 12:14:26.349491 2023] [:error] [pid 1863] [client 10.8.198.61:57121] PHP Notice: DB is not connected in /usr/local/nagiosxi/html/includes/db.inc.php on line 397, referer: https://guardian01.central.sepg.minhac. ... /index.php
We have the old version of PHP (5.4.16), we don't know where the error could come from. Could you tell us how to proceed?
Error update nagios 5.10.0
Re: Error update nagios 5.10.0
You could try updating 1 at a time to see if that resolves your upgrading issue. So you'd upgrade from 5.8.9 to 5.8.10 then keep going from there. 5.8.10 to 5.9.0, 5.9.0 to 5.9.1. Keep going till you upgrade to the latest.
Re: Error update nagios 5.10.0
The error message you provided indicates that the Nagios system is encountering an issue with the database connection after upgrading to version 5.10.0. The PHP notice suggests that the database is not connected at line 397 of the file "/usr/local/nagiosxi/html/includes/db.inc.php."igae1 wrote: ↑Fri May 26, 2023 5:16 am Good morning,
We have made an update from nagios 5.8.9 to 5.10.0. It is observed that the following error is observed in the ssl_error_log file:
[Fri May 26 12:14:26.429061 2023] [:error] [pid 13463] [client 10.8.198.61:57125] PHP Notice: DB is not connected in /usr/local/nagiosxi/html/includes/db.inc.php on line 397, referer: https://guardian01.central.sepg.minhac. ... en/noc.php incredibox
[Fri May 26 12:14:26.349491 2023] [:error] [pid 1863] [client 10.8.198.61:57121] PHP Notice: DB is not connected in /usr/local/nagiosxi/html/includes/db.inc.php on line 397, referer: https://guardian01.central.sepg.minhac. ... /index.php
We have the old version of PHP (5.4.16), we don't know where the error could come from. Could you tell us how to proceed?