[#ZBX-16342] Unsupported items are not rechecked at [Refresh unsupported items (in sec)] interval

[ZBX-16342] Unsupported items are not rechecked at [Refresh unsupported items (in sec)] interval Created: 2019 Jul 05 Updated: 2024 Apr 10 Resolved: 2019 Jul 23
Status:	Closed
Project:	ZABBIX BUGS AND ISSUES
Component/s:	Proxy (P), Server (S)
Affects Version/s:	3.0.27, 4.0.9
Fix Version/s:	4.4 (plan)

Type:

Problem report

Priority:

Trivial

Reporter:

Syusei YIn

Assignee:

Aleksejs Sestakovs (Inactive)

Resolution:

Fixed

Votes:

Labels:

None

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Attachments:

Screen Shot 2019-07-04 at 19.06.28.png

Screen Shot 2019-07-05 at 10.46.50.png

Screen Shot 2019-07-05 at 11.21.23.png

Issue Links:

Sub-task

Team:

Team C

Sprint:

Sprint 54 (Jul 2019)

Story Points:

Description

As mentioned in Zabbix Documentation 3.0,

Unsupported items
An item can become unsupported if its value cannot be retrieved for some reason. Such items are still rechecked at a fixed interval, configurable in Administration section.

unsupported items are considered to be rechecked by [Refresh unsupported items (in sec)], but Zabbix do not activate unsupported item every N seconds set here.

Steps to reproduce:

Configure an external check item like attached (Update interval (300s), Refresh unsupported items (600s))
Item key test2.sh like below.
```
#! /bin/bash

#sleep 60
echo 1
```
Make sure you can get value, then delete the "#" in front of [sleep 60] in the test2.sh script, make it timeout and become [not supported] status.Please refer to below log.
```
7794:20190704:185923.437 item "test_external:test2.sh" became not supported: Timeout while executing a shell script.
```
Add "#" in front of [sleep 60], make it works normally, then you can checkout this item activate after 300s, not 600s.Please refer to attached Screen Shot 2019-07-04 at 19.06.28.png and log below.
```
7793:20190704:190420.665 item "test_external:test2.sh" became supported
```

It can reproduce most of the time, but sometimes it makes sense activate the unsupported item by [Refresh unsupported items] (600s).You can try several times above steps to checkout different behaviors from Zabbix Documentations.

Best regards.
Syusei

Comments

Comment by Aleksejs Sestakovs (Inactive) [ 2019 Jul 10 ]

Hello Syusei,

The first item check after update interval change might occur earlier than configured. This includes update interval change to [Refresh unsupported items] value if item became unsupported. That is intended behavior caused by the seed value applied to the delay to spread item checks. We will update the documentation to reflect it.

yIn Thank you. Now, I've got it.

Comment by Alexander Vladishev [ 2019 Jul 23 ]

Updated documentation:

Comment by alix [ 2019 Oct 12 ]

I'm having the same problem on 4.0.13, unsupported items are not being retried with "Refresh unsupported items interval" (item update interval is bigger than refresh interval obviously).

I don't understand the answer given for the original bug reporter, it seems like there was a miscommunication. It is obvious that zabbix doesn't work the way it is supposed to work.

Or are you saying that the issue is known and is planned to be fixed only in 4.4?

Generated at Wed Aug 06 09:02:13 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.

[ZBX-16342] Unsupported items are not rechecked at [Refresh unsupported items (in sec)] interval Created: 2019 Jul 05 Updated: 2024 Apr 10 Resolved: 2019 Jul 23