Upgrade

[micatwix]

We noticed that the new update version of Nagios XI is available.
Please instruct us how to proceed with an upgrade.
What consideration should we take before an upgrade process.

Thanks !

[tonyyarusso]

Our upgrade instructions can be found on http://library.nagios.com/library/produ ... -nagios-xi

The easiest way to make a backup before proceeding is to use VMware's "snapshot" feature, assuming you're using a virtual machine.

[micatwix]

After the upgrade, we faced the symptom where on the NagiosXI dashboard screen we see that there is no critical issues, however on the Nagios status.cgi page we can see a several of those.
Please advise.

[micatwix]

Additionally we see that the apache error log is full of errors like these:

[error] [client 127.0.0.1] PHP Deprecated: Function eregi() is deprecated in /usr/local/nagios/share/pnp/include/function.inc.php on line 1553
...

[error] [client 127.0.0.1] PHP Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/nagios/share/pnp/include/function.inc.php on line 563

Waiting for your update.

[mguthrie]

After the upgrade, we faced the symptom where on the NagiosXI dashboard screen we see that there is no critical issues, however on the Nagios status.cgi page we can see a several of those.
Please advise.

Could you repost this as a separate thread and give us some more detail as to what you're seeing? Screenshots would help us better identify what you're seeing.

[mguthrie]

Additionally we see that the apache error log is full of errors like these:

[error] [client 127.0.0.1] PHP Deprecated: Function eregi() is deprecated in /usr/local/nagios/share/pnp/include/function.inc.php on line 1553
...

[error] [client 127.0.0.1] PHP Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/nagios/share/pnp/include/function.inc.php on line 563

Waiting for your update.

The error messages you're seeing have to do with your php.ini settings on your Apache webserver. These errors are non-critical warning messages and should not affect the functionality of XI. You can change your error message settings in your php.ini file to only display critical messages in the server log.
This is the internal doc pasted from the php.ini file that explains the settings.

Code: Select all

; Error handling and logging ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

; error_reporting is a bit-field.  Or each number up to get desired error
; reporting level
; E_ALL             - All errors and warnings (doesn't include E_STRICT)
; E_ERROR           - fatal run-time errors
; E_WARNING         - run-time warnings (non-fatal errors)
; E_PARSE           - compile-time parse errors
; E_NOTICE          - run-time notices (these are warnings which often result
;                     from a bug in your code, but it's possible that it was
;                     intentional (e.g., using an uninitialized variable and
;                     relying on the fact it's automatically initialized to an
;                     empty string)
; E_STRICT          - run-time notices, enable to have PHP suggest changes
;                     to your code which will ensure the best interoperability
;                     and forward compatibility of your code
; E_CORE_ERROR      - fatal errors that occur during PHP's initial startup
; E_CORE_WARNING    - warnings (non-fatal errors) that occur during PHP's
;                     initial startup
; E_COMPILE_ERROR   - fatal compile-time errors
; E_COMPILE_WARNING - compile-time warnings (non-fatal errors)
; E_USER_ERROR      - user-generated error message
; E_USER_WARNING    - user-generated warning message
; E_USER_NOTICE     - user-generated notice message

[micatwix]

Ok.
Here it comes another issue related to upgrade:

Any configuration change cannot be saved in the Nagios core configuration.
In the log we can see the following errors:

Code: Select all

Oct 11 09:51:10 nagiosxi nagios: ndomod: Could not open data sink!  I'll keep trying, but some output may get lost...
Oct 11 09:51:10 nagiosxi nagios: Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully.
Oct 11 10:06:22 nagiosxi nagios: ndomod: Still unable to connect to data sink.  27377 items lost, 5000 queued items to flush.
...
Oct 11 10:41:36 nagiosxi nagios: ndomod: Still unable to connect to data sink.  49336 items lost, 5000 queued items to flush.
Oct 11 10:56:48 nagiosxi nagios: ndomod: Still unable to connect to data sink.  71678 items lost, 5000 queued items to flush.
...

Please advise.

[micatwix]

Anyone ?

[micatwix]

Well, recompiling NDO-Utils with the different MySQL library solved this error,
however we still see that the Nagios configuration files are still not containing the changes made in UI.
This time we see no errors in the log beside of the warning like this one:

Code: Select all

Oct 12 08:29:32 nagiosxi nagios: Warning: Service <...> on host <...> has no check time period defined!

We got this warning for all Service, Host and Contacts objects.
Modifying the time periods in the templates, has no effect because of the issue above.

We are looking forward for your reply.

Thanks !

[mguthrie]

Are you able to "Apply Configuration" and have it go through successfully from Nagios XI?

The way the core config manager works is that when you make a change, the information gets updated in the MySQL database, but then it doesn't get written out into the config files until you click "Apply Configuration." If there's an error in the config, it will roll back to the last known good configuration and update the config files accordingly. You can view the configurations for the bad config by downloading the zip file from the "Configuration Snapshots" menu.

I'd like to pin down the specific problems you're currently still facing so we can help resolve the issues you're having.

First, are you able to Apply Configuration from the CCM? If not, can you send us the most recent Configuration Snapshot, both the zip file, and text file? (Bad snapshots will be highlighted in red).

Can you give us the system information for the box you're running XI on? Is it a manual install or VM? Which distro, and is it 32 or 64bit?