Nagios Support Forum

That did it, thanks.

I was attempting to upgrade from 5.6.2 to 5.6.4, but it is failing. It appears to be complaining of duplicate configs, but I've had that in previous upgrades and it still succeeded. [root@NagiosXI nagiosxi]# ./upgrade Nagios XI Upgrade Log ========================== DATE: Thu Jul 11 09:15:30 EDT 201...

That did it, thank you.

1. I am upgrading from 5.5.9 2. [root@NagiosXI ~]# yum repolist -v Loading "fastestmirror" plugin Config time: 0.007 Yum Version: 3.2.29 Loading mirror speeds from cached hostfile epel/metalink | 18 kB 00:00 * base: centos.mirror.lstn.net * epel: mirror.math.princeton.edu * extras: mirror....

I attempted to upgrade to the latest version of NagiosXI via the Web UI, but it failed. I then attempted to do so manually, but received the below error. It appears to be trying to install a 7 version of the packages. Is there a way to bypass this? Nagios XI Upgrade Log ========================== DA...

We upgraded from 5.4.13.

Prior to upgrade, we would only receive the recovery notification if the service recovered from a critical state using the escalation feature. This was a preferable case because we use the escalation for our on-call. So receiving pages in the middle of the night for recoveries of objects that weren'...

I have upgraded to 5.5.1 but am still having the same issue occur. I have provided an example. All of the notifications here are coming from service escalations. The Warning notifications are intentional, but the ones labeled 'Custom: notify-service-by-pager' are only set for alerting from critical ...

define serviceescalation { # config_name NOG On Call hostgroup_name Production Database Server,Production Web Servers,Production Windows Servers service_description * contact_groups nog-on_call first_notification 1 last_notification 0 notification_interval 60 escalation_period xi_timeperiod_24x7 es...

I have confirmed that the service never went into a Hard state. It was in a Warning state and then recovered. The pages that we receive for this particular instance are done via Service Escalations. The escalation is set to only send pages on Critical and Ok.