In reference to https://support.zabbix.com/browse/ZBX-12251
The problem has been patched, but only for 4.0 alpha, and 3.2. My environment is on 3.4, which has just gone out of support, with no new version of zabbix to upgrade to. I'm a little upset that the patch did not get developed for 3.4, which was still in support when this bug was solved, and now I'm less likely to trust zabbix's support claims in the future.
I am frequently experiencing this bug, and many problems cannot be manually closed because the triggers were originally configured without "allow manual close". My only option is to clear the history data for the items, or delete and re-add the hosts, which I would like to save as a last resort. I have too many triggers to monitor individually for whether they are stuck or not (225836 enabled triggers across 7355 hosts). When triggers become stuck, it causes a problem for me because if the trigger fires again at a later time, then the action will not be performed and alerts do not get sent. To me, this is core functionality of the product.
My options are:
-downgrade my environment to 3.2
-Upgrade my environment to 4.0 alpha
Has anyone had any luck with any tunable settings, such as increasing history cache sizes, or something that I can do to mitigate this bug until the official release of Zabbix 4.0? I would rather not run my production environment on an alpha version, and I don't know if downgrading will work properly, since I am using features of 3.4 with LLD macros.
If it's possible to have a patch for 3.4 created, that would be ideal for me, but I will take whatever help I can get.
Thanks!
The problem has been patched, but only for 4.0 alpha, and 3.2. My environment is on 3.4, which has just gone out of support, with no new version of zabbix to upgrade to. I'm a little upset that the patch did not get developed for 3.4, which was still in support when this bug was solved, and now I'm less likely to trust zabbix's support claims in the future.
I am frequently experiencing this bug, and many problems cannot be manually closed because the triggers were originally configured without "allow manual close". My only option is to clear the history data for the items, or delete and re-add the hosts, which I would like to save as a last resort. I have too many triggers to monitor individually for whether they are stuck or not (225836 enabled triggers across 7355 hosts). When triggers become stuck, it causes a problem for me because if the trigger fires again at a later time, then the action will not be performed and alerts do not get sent. To me, this is core functionality of the product.
My options are:
-downgrade my environment to 3.2
-Upgrade my environment to 4.0 alpha
Has anyone had any luck with any tunable settings, such as increasing history cache sizes, or something that I can do to mitigate this bug until the official release of Zabbix 4.0? I would rather not run my production environment on an alpha version, and I don't know if downgrading will work properly, since I am using features of 3.4 with LLD macros.
If it's possible to have a patch for 3.4 created, that would be ideal for me, but I will take whatever help I can get.
Thanks!