1.4.1 Unsupported items serious problem

[testos]

Unsupported items [zabbix agent (active)] never make active when it is possible. Set parameter “Refresh unsupported items (in sec)” to several values #0 and not working. It is necessary to do it manually.
Regards.

[Alexei]

Currently it is implemented for passive checks only. Will be extended to all checks at some point.

[Palmertree]

Just curious when this might be implemented. I just had the same problem occur tonight where my Zabbix Agent items went unsupported but did not come back when the server was back online. Thanks in advance.

[Palmertree]

I made a temporary fix by creating the following bash script that is ran from a cron job every hour. It changes the status of "unsupported" to "Active". If the item is still unsupported it will eventually change back.

#!/bin/bash
mysql -uroot -p<password><<EOFMYSQL
use zabbix;
update items set status=0 where status=3 and type=0;
EOFMYSQL

[claytronic]

I've implemented Palmertree's workaround but I would really prefer the agent code be updated to work with the "Refresh Unsupported Items" for active-checks. Not having it degrades the reliability of active-checks.

[testos]

Active checks have got two serious limitations at present:
- Unsupported items never make active when it is possible
- Flexible intervals don't work for them

[Alexei]

Active checks have got two serious limitations at present:
- Unsupported items never make active when it is possible

This problem is fixed.

[testos]

That's great news.

Thanks for adding it. This goes well.

[claytronic]

Awesome.

--
Claytronic