I had this same exact problem too and the only way I found to resolve it was to blow the install / db away and reinstall from scratch. The only downside, aside from the time it takes to reinstall, was the loss of our history but that was acceptable compared to not having consistent downtimes.
https://github.com/Icinga/icinga2/issues/4747 On Feb 23, 2017, 3:48 PM -0500, Michael Martinez <mwt...@gmail.com>, wrote: > HEre are the contents of my /var/lib/icinga2/api directory: > > [root@ec2 icinga101 api]$ pwd > /media/ephemeral0/icinga2/var/lib/icinga2/api > [root@ec2 icinga101 api]$ !find > find . -path '*downtimes*' -prune -o -path '*comments*' -prune -o -type f > ./packages/_api/conf.d/downtimes > ./packages/_api/conf.d/comments > > On Thu, Feb 23, 2017 at 12:30 PM, Michael Martinez <mwt...@gmail.com> wrote: > > Is there any way to make the scheduled Downtimes persistent between > > doing a reload? They disappear every time a reload occurs. > > > > -- > > --- > > Michael Martinez > > http://www.michael--martinez.com > > > > -- > --- > Michael Martinez > http://www.michael--martinez.com > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
