This support forum board is for support questions relating to
Nagios XI, our flagship commercial network monitoring solution.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
-
Contact:
Post
by scottwilkerson »
This was a bug that we resolved in the recently released 5.5.2
from the changelog
Code: Select all
Fixed issue in Nagios Core where scheduled flexible downtimes would not trigger downtime start -JO
an upgrade to 5.5.2 should resolve the issue
-
jaroork
- Posts: 12
- Joined: Wed Dec 28, 2016 10:48 am
Post
by jaroork »
If this is what you're asking for i get 302 POST when I schedule the downtime
type=host
hosts[]=au-kvm-a.dev.multiservice.com
com_author=Jeff+A+Roork
com_data=test+downtime
trigger=0
fixed=0
hours=0
minutes=20
start_time=2018-07-31+10:15:44
end_time=2018-07-31+12:15:44
childoptions=1
serviceoptions=1
Is that not expected?
-
jaroork
- Posts: 12
- Joined: Wed Dec 28, 2016 10:48 am
Post
by jaroork »
sorry, i didn't see page 2 with your reply.
-
jaroork
- Posts: 12
- Joined: Wed Dec 28, 2016 10:48 am
Post
by jaroork »
You can close this thread, 5.5.2 seems to have fixed flexible downtime. Thanks,
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
-
Contact:
Post
by scottwilkerson »
jaroork wrote:You can close this thread, 5.5.2 seems to have fixed flexible downtime. Thanks,
Excellent
Locking