[ZBX-24946] "Unsupported timeout value." while testing SNMP interface discovery Created: 2024 Jul 31 Updated: 2024 Sep 20 Resolved: 2024 Sep 20 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 7.0.2 |
| Fix Version/s: | None |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Pavel Fiyalka | Assignee: | Edgar Akhmetshin |
| Resolution: | Cannot Reproduce | Votes: | 10 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Oracle Linux Server 8.10 x86_64 zabbix-web-mysql-7.0.2-release1.el8.noarch |
||
| Attachments: |
2024-08-19_19-44.png
image-2024-08-02-10-00-52-773.png
image-2024-08-19-15-11-47-609.png
zabbix_7.0.2.png
|
| Description |
|
Steps to reproduce:
Result: |
| Comments |
| Comment by Pavel Fiyalka [ 2024 Jul 31 ] |
|
No one of discovery from discovery checks is working. I also checked that at zabbix 7.0.0 and it's work. |
| Comment by Aleksey [ 2024 Aug 01 ] |
|
Same problem with version 7.0.2 |
| Comment by Konstantīns Ošmjans [ 2024 Aug 01 ] |
|
The same problem with Zabbix v7.0.1. Checked with all versions of SNMP (v1, v2c, v3) – all testings are fail with the same error "Unsupported timeout value". Additional info: for troubleshooting purpose we tried to use the same OID value (from the LLD rule) in an usual (non-LLD) item. In this case the testing works without problems. |
| Comment by Aleksey [ 2024 Aug 01 ] |
|
The problem is not only with snmp. It's the same problem with Agents. |
| Comment by Danilov Aleksey [ 2024 Aug 01 ] |
|
Zabbix 7.0.2 Found the same bug today. Here they write that this bug also exists on "Zabbix -agent", but there it can be solved by overriding the Timeout value, but for the "SNMP agent" there is no way to override the timeout and this is the uniqueness of the bug with this type of data source. |
| Comment by Luke Burrows [ 2024 Aug 02 ] |
|
I am experiencing the same problem running on 7.0.2 when trying to test Discovery rules
|
| Comment by Shaun Dwyer [ 2024 Aug 19 ] |
|
I'm also impacted by this. If you edit the code and add a hidden field name="timeout" it succeeds.
Is there a global macro or configuration variable we can update that will make this work permanently? I'm also wondering why the priority on this ticket is 'trivial'. This makes debugging stuff much harder, especially for the development work im doing now on templates. |
| Comment by Thiago Alex [ 2024 Aug 19 ] |
|
I'm facing the same issue. I was using version 7.0.0 and started encountering this problem on one of the servers. I simply updated to 7.0.2 without reading any release notes, and the problem persists. |
| Comment by Thiago Alex [ 2024 Aug 20 ] |
|
I noticed version 7.0.3 was released, and although there were no specific mentions of the issue, it resolved itself after the update.
|
| Comment by Jan Nohejl [ 2024 Aug 20 ] |
|
Hi, 7.0.3 resolved this issue |
