[ZBX-11231] Error raised when returned value is integer for Store value - is Delta and Type of information - Numeric (float) Created: 2016 Sep 19  Updated: 2017 May 30  Resolved: 2016 Sep 20

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 3.2.0
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Yuriy Novoselov Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 14.04.5 LTS


 Description   

After upgrade from 3.0.3 to 3.2.0 in server log appeared messages like
10266:20160919:125617.813 error reason for "server:iptab.traf[ACCEPT,TCP_08080]" changed: Received value [1216122185] is not suitable for value type [Numeric (float)]

But Store value - is Delta (speed per second)
according to - 'Note: As this calculation may produce floating point numbers, it is recommended to set the 'Type of information' to Numeric (float), even if the incoming raw values are integers.' https://www.zabbix.com/documentation/3.2/manual/config/items/item
Type of information - is set to Numeric (float)



 Comments   
Comment by Glebs Ivanovskis (Inactive) [ 2016 Sep 19 ]

Is this item a script? Does it output CR or LF characters?

Comment by Yuriy Novoselov [ 2016 Sep 19 ]

UserParameter=iptab.traf[*],sudo /sbin/iptables -nvxwL | grep $1 | grep "zmon $2" | awk '

{print $$2}

'

Comment by Yuriy Novoselov [ 2016 Sep 20 ]

I'am very sorry, but looks like this command on some host return double line value. After fix error not rising again.
Meanwhile such log do nothing to associate with this issue.

Comment by Yuriy Novoselov [ 2016 Sep 20 ]

Missconfig

Comment by Glebs Ivanovskis (Inactive) [ 2016 Sep 20 ]

Indeed, error message is not the best. Probably, it is something we can improve. Your issue is somewhat related to ZBX-10784, I'll add a comment there since you've already closed this one.

Comment by Yuriy Novoselov [ 2016 Sep 20 ]

thnx

Generated at Sat Apr 05 01:18:10 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.