From e1a963f0accd8febf21d1bf68682e9fffa3fb837 Mon Sep 17 00:00:00 2001 From: Jean Flach Date: Tue, 4 Sep 2018 13:33:48 +0200 Subject: [PATCH] Update workaround for custom vars This updates #6572 which did not work --- doc/16-upgrading-icinga-2.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/doc/16-upgrading-icinga-2.md b/doc/16-upgrading-icinga-2.md index f483ff0e3..266e073f5 100644 --- a/doc/16-upgrading-icinga-2.md +++ b/doc/16-upgrading-icinga-2.md @@ -147,18 +147,20 @@ 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: +remedy this, truncate the customvar tables and restart Icinga 2. The following is an example of how to do this with mysql: ``` $ mysql -uroot -picinga icinga -MariaDB [icinga]> UPDATE icinga_hosts SET config_hash = NULL; +MariaDB [icinga]> truncate icinga_customvariables; +Query OK, 0 rows affected (0.05 sec) +MariaDB [icinga]> truncate icinga_customvariablestatus; +Query OK, 0 rows affected (0.03 sec) MariaDB [icinga]> exit Bye $ sudo systemctl restart icinga2 ``` -Custom vars should now be up to date. +Custom vars should now stay up to date. ## Upgrading to v2.8.2