[ZBX-13481] Incorrect parsing BITS data type from SNMP response Created: 2018 Feb 16  Updated: 2024 Apr 10  Resolved: 2018 Apr 20

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 3.0.14
Fix Version/s: 3.0.17rc1, 3.4.9rc1, 4.0.0alpha6, 4.0 (plan)

Type: Patch request Priority: Critical
Reporter: Alexey Pustovalov Assignee: Vladislavs Sokurenko
Resolution: Fixed Votes: 0
Labels: boolean, snmp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File ZBX-13481.diff    
Issue Links:
Duplicate
Team: Team A
Sprint: Sprint 28, Sprint 29, Sprint 30, Sprint 31, Sprint 32
Story Points: 0.25

 Description   

If SNMP OID has BITS value type, Zabbix does not parse it at all.
1. Value type text: Empty string
2. Value type numeric with/without data type boolean:

Received value [] is not suitable for value type [Numeric (unsigned)] and data type [Boolean]


 Comments   
Comment by Oleksii Zagorskyi [ 2018 Feb 16 ]

similar to ZBX-13402

Comment by Vladislavs Sokurenko [ 2018 Feb 21 ]

Reproduced on trunk.

Note that preprocessing will not help here because question mark is saved to database instead of real value:

 26757:20180221:183857.389 zbx_snmp_get_octet_string() full value:'BITS: 80 00 notification(0) ' hint:'(null)'
 26757:20180221:183857.389 End of zbx_snmp_get_octet_string():'�

Even if text type is used, frontend still displays ? instead of actual value.

Comment by Vladislavs Sokurenko [ 2018 Apr 19 ]

Fixed in:

  • pre-3.0.17rc1 r79905
  • pre-3.4.9rc1 79906
  • pre-4.0.0alpha6 (trunk) r79907
Generated at Thu Apr 03 04:02:37 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.