tyler.durden
/
icinga2
mirror of https://github.com/Icinga/icinga2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update workaround for custom vars 

This updates #6572 which did not work
This commit is contained in:
Jean Flach 2018-09-04 13:33:48 +02:00 committed by GitHub
parent 81b9c9cef0
commit e1a963f0ac
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/16-upgrading-icinga-2.md
View File

@ -147,18 +147,20 @@ mix of local FQDN, timestamps and random numbers.
### Custom Vars not updating <a id="upgrading-to-2-9-custom-vars-not-updating"></a> ### Custom Vars not updating <a id="upgrading-to-2-9-custom-vars-not-updating"></a>
A rare issue preventing the custom vars of objects created prior to 2.9.0 being updated when changed may occur. To 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 remedy this, truncate the customvar tables and restart Icinga 2. The following is an example of how to do this with mysql:
example of how to do this for Hosts in mysql:
``` ```
$ mysql -uroot -picinga icinga $ 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 MariaDB [icinga]> exit
Bye Bye
$ sudo systemctl restart icinga2 $ 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 <a id="upgrading-to-2-8-2"></a> ## Upgrading to v2.8.2 <a id="upgrading-to-2-8-2"></a>