I can set a one time period and the hosts will go into maintenance but when I use (daily, weekly, monthly) the hosts don't go into maintenance. Is there something I'm not aware of or is this a bug?
-
-
Any ideas? -
Works for us....
On the maintenance period definition (first screen), make sure your active since is before now and your active till is after. Check your periods, make them at least an hour long to test.Comment
-
I have the maintenance active from the beginning of the month until the same month next year. It shows active on the first page. I've chosen a host group with multiple hosts and set the period to daily at 12:00 for 2 hours. The wrench icon will not show and I still receive notifications. I've made sure the actions are configured correct as well. If I change it to a one time then it works. I've upgraded to 6.2 from 6.0 and it is still happening.Comment
-
We are seeing similar problem. We did upgrade from 5.x to 6.x and after that maintenance periods are not working. Hosts are not going to maintenance (wrench not shown). If we define maintenance for one time only, that is working correcly. And for defining period e.g. that should be active daily on night time, that does not trigger.Comment
-
Hi guys, I had the same problem. In my case was about timezones conflict. I had configured correctly Zabbix GUI timezone but server's timezone was incorrect. That was doing that one time maintenance worked but the scheduled not. I guess that when you schedule a maintenance it uses Zabbix Server timezone to execute the maintenance. If server's timezone is incorrect, it will put the target on manteinance at non wished hours. So basically it works but not when you wantComment
-
Because of host server and zabbix application php timezone difference, maintenance with "one time" will work properly but reoccurring will not work.
Once both server and application time matches, it will start to work normalComment
Comment