-
Type:
Incident report
-
Resolution: Fixed
-
Priority:
Major
-
None
-
Affects Version/s: None
-
Component/s: Agent (G), Documentation (D), Frontend (F), Installation (I), Server (S)
-
None
-
Environment:freebsd,debian,gentoo
There is a problem with snmp elements (after migration 1.6.1->trunk(6425))
Type: SNMPv2 agent
Type of information: Numeric (float or integer)
Data type: decimal
other settings default.
With other types information all OK.
An example:
real value: 166
Displayed value: 13834357133799325696
log file:
Code:
1921:20081209:002538 AV loop OID [.1.3.6.1.4.1.9.10.19.1.1.5.0] Type [2] ' INTEGER: 166'
1921:20081209:002538 End get_value () 1921:20081209:002538 Query [begin;]
1921:20081209:002538 In process_new_value (vpn. NumVPNTunnels)
1921:20081209:002538 In add_history (key:vpn. NumVPNTunnels, value_type:0, type:2)
1921:20081209:002538 In add_history (itemid:48367, DOUBLE:13834357133799325696.000000) 1
921:20081209:002538 In add_history ()
Problem in 6378 rev - - [DEV-266] added support of octal and hexadecimal data
problem in check_snmps.c
in funtion get_snmp
Code:
zbx_snprintf(buf, sizeof(buf), ZBX_FS_UI64, (unsigned long)*vars->val.integer);
if (*vars->val.integer < 0)
zbx_snprintf(buf, sizeof(buf), ZBX_FS_DBL, (double)*vars->val.integer);
else
zbx_snprintf(buf, sizeof(buf), ZBX_FS_UI64, (unsigned long)*vars->val.integer);