Thanks, all! I’m glad it’s not just me. On September 2, 2016 at 8:03:58 AM, Peter Eckel (li...@eckel-edv.de) wrote:
Hi, I can confirm it's there in 2.5.4. Cheers, Peter. > On 02 Sep 2016, at 08:53, Bancal Samuel <samuel.ban...@epfl.ch> wrote: > > Hi, > > This is a bug that was reported https://dev.icinga.org/issues/11182 and marked as resolved 3 months ago (target version 2.5.0). > When 2.5.0 was released ... aparently the bug was still there : https://dev.icinga.org/issues/12548 . > > You can "Watch" these bugs to know when it'll be fixed. > > Regards, > Samuel > > > On 02. 09. 16 00:33, Rob DeSanno wrote: >> I'm at a loss and hoping that maybe someone here has a solution. The problem that I have been noticing is that anytime I do a restart or reload, I am losing some type of downtime information in icinga2. I just upgraded to the latest release but unfortunately the problem still exists for me. >> >> For starters, I am running icinga 2.5 with mariadb, plus icinga2-classic for use with nagstamon and older mobile app compatibility. >> >> # rpm -qa | egrep -i 'mariadb|icinga' >> icingacli-2.3.4-1.el7.centos.noarch >> icingaweb2-vendor-dompdf-0.6.2-1.el7.centos.noarch >> MariaDB-client-10.1.17-1.el7.centos.x86_64 >> icinga2-2.5.4-1.el7.centos.x86_64 >> opsgenie-icinga2-2.0.0-1.all.noarch >> icinga2-common-2.5.4-1.el7.centos.x86_64 >> icinga2-classicui-config-2.5.4-1.el7.centos.x86_64 >> icinga-rpm-release-7-1.el7.centos.noarch >> icingaweb2-vendor-lessphp-0.4.0-1.el7.centos.noarch >> icinga2-libs-2.5.4-1.el7.centos.x86_64 >> MariaDB-server-10.1.17-1.el7.centos.x86_64 >> icingaweb2-common-2.3.4-1.el7.centos.noarch >> icingaweb2-vendor-JShrink-1.0.1-1.el7.centos.noarch >> icingaweb2-vendor-Parsedown-1.0.0-1.el7.centos.noarch >> MariaDB-common-10.1.17-1.el7.centos.x86_64 >> icinga2-bin-2.5.4-1.el7.centos.x86_64 >> icingaweb2-2.3.4-1.el7.centos.noarch >> icinga-gui-1.13.3-0.el7.centos.x86_64 >> MariaDB-shared-10.1.17-1.el7.centos.x86_64 >> icinga2-ido-mysql-2.5.4-1.el7.centos.x86_64 >> icinga-doc-1.13.3-0.el7.centos.x86_64 >> php-Icinga-2.3.4-1.el7.centos.noarch >> icingaweb2-vendor-HTMLPurifier-4.7.0-1.el7.centos.noarch >> >> The problem is that when I have a host that is down, and it is acked, the services still show up in icinga classic as critical. If I set a downtime on the host and services at the same time, everything is fine until I do a restart or a reload. This causes icinga to ignore that there is a downtime set against the host even though my previous comments still persist. >> >> To troubleshoot, I tried all different kinds of approaches like removing the downtimes from >> /var/lib/icinga2/api/packages/_api/{SERVERNAME}-1459445242-1/conf.d/downtimes/ >> >> or manually removing them from the following database tables directly (ie icinga_downtimehistory, icinga_acknowledgements, icinga_comments, or icinga_scheduleddowntime). >> >> The reason for being so extreme is because I was not able to remove whatever downtime was associated with this host by using the gui directly. I guess the next step would be to remove the host and add it back in to see what happens but to be honest, i'm seeing this same problem with a handful of hosts however, it could be just limited to these servers and not all. >> >> Anyone have any similar experiences? >> >> >> >> >> _______________________________________________ >> icinga-users mailing list >> >> icinga-users@lists.icinga.org >> https://lists.icinga.org/mailman/listinfo/icinga-users > > -- > Samuel Bancal > ENAC-IT > EPFL > > _______________________________________________ > 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
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
