From: Jean Flach Date: Fri, 24 Aug 2018 09:03:29 +0000 (+0200) Subject: Add note about workaround for broken custom vars X-Git-Tag: v2.9.2~6 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=7713291805e46229ab0039432d94c1a12e7eb6fd;p=icinga2 Add note about workaround for broken custom vars refs #6572 --- diff --git a/doc/16-upgrading-icinga-2.md b/doc/16-upgrading-icinga-2.md index 870b09d69..af6d6b9ec 100644 --- a/doc/16-upgrading-icinga-2.md +++ b/doc/16-upgrading-icinga-2.md @@ -97,6 +97,22 @@ With the removal of RHEL 5 as supported platform, we can finally use real unique This is reflected in generating names for e.g. API stage names. Previously it was a handcrafted mix of local FQDN, timestamps and random numbers. +### Custom Vars not updating + +A rare issue preventing the custom vars of objects created prior to 2.9.0 being updated when changed may occur. To +remedy this the config checksums of the affected type need to be reset to trigger a full update. The following is an +example of how to do this for Hosts in mysql: + +``` +$ mysql -uroot -picinga icinga +MariaDB [icinga]> UPDATE icinga_hosts SET config_hash = NULL; +MariaDB [icinga]> exit +Bye +$ sudo systemctl restart icinga2 +``` + +Custom vars should now be up to date. + ## Upgrading to v2.8.2