Nagios Support Forum

Nagios XI 5.5.0

Here is the information that is requested:
CentOS Linux release 7.5.1804 (Core)
64BIT
Manual Install of XI

Ever since upgrading to 5.5.0 recurring maintenance's seem to not be working.

https://drive.google.com/open?id=1bZ75k ... XwQo--eZqJ

You can see the above screenshot that i have a recurring maintenance for 9:45 and to run for 2 hours on Tuesdays but yet on this Tuesday at 10:47 the service alert kicked off.

Is this fixed if 5.5.1 or what should i look at next?

Alerts should still happen during downtimes. Notifications should not be sent though. Did you also receive notifications?

Also did you see the downtime in the event log during that time?

Yes, but the alerts are still being sent. This is the alert being found in OpsGenie.

Any other thoughts?



Source
NagiosXIV2

Integration
Nagios XI (NagiosXIV2)

Teams
mn_co

Alias
BRVL-NetGuard-G5_Check_NetGuardian_432_Port_26_Warning_WARNING

Last Updated At
Jul 10, 2018 11:40 AM

Description
Notification Type: PROBLEM
Service: Check_NetGuardian_432_Port_26_Warning
Host: BRVL-NetGuard-G5
Address: 192.168.48.205
State: WARNING
Additional Info: Warning - MIN GEN RUN (Error).
Date/Time: Tue Jul 10 10:51:03 CDT 2018
Priority
host_address
192.168.48.205

host_alias
BRVL-NetGuard-G5

host_attempt
1

host_duration
25d 21h 58m 4s

host_group_name
Site - RSFD 00

host_latency
0.131

host_name
BRVL-NetGuard-G5

host_output
OK - 192.168.48.205: rta 29.293ms, lost 0%

host_perf_data
rta=29.293ms;3000.000;5000.000;0; pl=0%;80;100;; rtmax=32.729ms;;;; rtmin=26.180ms;;;;

host_state
UP

host_state_type
HARD

last_host_check
1531237823

last_host_state_change
1528998779

last_service_check
1531237854

last_service_state_change
1531237625

max_host_attempts
5

max_service_attempts
HARD

nagios_server
default

service_attempt
5

service_desc
Check_NetGuardian_432_Port_26_Warning

service_duration
0d 0h 3m 58s

service_group_name
$

service_latency
0.626

service_output
Warning - MIN GEN RUN (Error).

service_state
WARNING

service_state_type
HARD

No i posted the logs in that first post i made. It does not show Recurring Downtime being triggered in Event Logs.

So I am making the assumption that Recurring Downtime is not working at this time.

Is that a separate service? Is this something with 5.5.0? This started happening after the update last week.

I would definitely suggest upgrading to 5.5.1 for other fixes that are pretty important. We have not come across any issues that I know of with scheduling downtime or having downtime scheduled with the recurring downtime component.

There is also a recurringdowntime.log in the /usr/local/nagiosxi/var that if you can post it, can tell us if there were any errors while it's trying to schedule the downtime.

https://drive.google.com/open?id=1vpQ2O ... OHpotjPjm7

There is my latest recurring downtime.log

We are running the upgrade to 5.5.1 now.

https://pastebin.com/e5bmfrKX

Here is the output after the update. Looks like the update failed but UI shows 5.5.1 can you confirm?

Also recurring downtime is still now working we did not see the notification in the log.

And /var/log/httpd/error_log shows the following.


[Fri Jul 13 16:19:34.336679 2018] [:error] [pid 2924] [client 192.168.61.73:1800] PHP Notice: Undefined variable: search_str in /usr/local/nagiosxi/html/includes/components/xicore/recurringdowntime.inc.php on line 196, referer: http://nagios.acentek.net/nagiosxi/incl ... acb4a61b74
[Fri Jul 13 16:19:34.336943 2018] [:error] [pid 2924] [client 192.168.61.73:1800] PHP Notice: Undefined variable: search_str in /usr/local/nagiosxi/html/includes/components/xicore/recurringdowntime.inc.php on line 196, referer: http://nagios.acentek.net/nagiosxi/incl ... acb4a61b74
[Fri Jul 13 16:19:34.337198 2018] [:error] [pid 2924] [client 192.168.61.73:1800] PHP Notice: Undefined variable: search_str in /usr/local/nagiosxi/html/includes/components/xicore/recurringdowntime.inc.php on line 196, referer: http://nagios.acentek.net/nagiosxi/incl ... acb4a61b74

@acentek, Looking at the upgrade log I believe the update went successfully. Did you get that upgrade error message inside the GUI?
Have you tried scheduling downtime after the upgrade to see if you'll still receive notifications?