[ZBX-12618] item became not supported: Item preprocessing step #1 failed: (null) Created: 2017 Aug 28 Updated: 2018 Oct 09 Resolved: 2017 Aug 29 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 3.4.1 |
Fix Version/s: | 3.4.2rc1, 4.0.0alpha1, 4.0 (plan) |
Type: | Problem report | Priority: | Major |
Reporter: | sles | Assignee: | Vjaceslavs Bogdanovs |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Centos 7 |
Attachments: | ZBX-12618.patch | ||||||||||||||||
Issue Links: |
|
||||||||||||||||
Team: | Team C | ||||||||||||||||
Sprint: | Sprint 15 | ||||||||||||||||
Story Points: | 1 |
Description |
Hello! Upgraded 3.4.0 to 3.4.1 today and now I see messages in logs like: This is snmp v1 item , which gets data from switch. snmpget -v1 -c public 192.168.22.178 interfaces.ifTable.ifEntry.ifOutOctets.26775 btw, there are no such errors in log with zabbix 3.4.0. Looks like new bug. |
Comments |
Comment by sles [ 2017 Aug 29 ] |
Hello! As I see current status is resolved. Thank you! |
Comment by Andris Zeila [ 2017 Aug 29 ] |
It's resolved, but not yet tested/finished. |
Comment by Andris Zeila [ 2017 Aug 29 ] |
Successfully tested. To clarify about the bug itself - when item with delta (simple change or speed per second) preprocessing option receives value less than the one before, item will become not supported. Next value (if it's greater than the last one) will be calculated normally (like before). So basically if we had input values 1,2,4,3,6 then for simple change the expected results were -,1,2,-,3 ('-' nothing happens), while the current results are -,1,2,(item becomes not supported),3 The error message is potentially dangerous - on some systems (depending on C library) printf("%s", NULL) might crash. |
Comment by sles [ 2017 Aug 29 ] |
Thank you for clarification, and... |
Comment by Andris Zeila [ 2017 Aug 29 ] |
Sure, you can get the patch from development branch svn://svn.zabbix.com/branches/dev/ZBX-12618 |
Comment by Vjaceslavs Bogdanovs [ 2017 Aug 29 ] |
Available in 3.4.2rc2 r71803 and 4.0.0alpha1 (trunk) r71809 |
Comment by sles [ 2017 Aug 29 ] |
Unfortunately, looks like it is not available anonymously: svn: E170000: URL 'svn://svn.zabbix.com/branches/dev/ZBX-12618' doesn't exist Thank you! |
Comment by Vjaceslavs Bogdanovs [ 2017 Aug 29 ] |
Sorry, it got merged into main branches. Feel free to use svn://svn.zabbix.com/branches/3.4 fix is already there. |
Comment by Vladislavs Sokurenko [ 2017 Aug 29 ] |
Thank you for your report, patch attached. |
Comment by sles [ 2017 Aug 29 ] |
Thank you! I just replaced src/zabbix_server/preprocessor/preproc_worker.c to file from svn, now I don't see preprocessor errors in log. Thank you! |
Comment by Vjaceslavs Bogdanovs [ 2017 Aug 29 ] |
Please be advised that /src/zabbix_server/preprocessor/preprocessing.c was changed as well. |
Comment by sles [ 2017 Aug 29 ] |
Oops! Thank you! |
Comment by Oleg Husnutdinov [ 2017 Sep 05 ] |
Hello, sorry that I'm write in resolved theme. Do I need to create new bug? If no, how can I apply this fix to my server which installed from packages? |
Comment by Andris Zeila [ 2017 Sep 06 ] |
As I explained earlier this is not SNMP problem, but bug in delta value preprocessing. In most of systems the only problem might be notification about unsupported items, otherwise the data gathering is not affected. It's fixed and will be released in Zabbix 3.4.2. There is no need to create a new bug, but there are no official packages yet - you either have to wait for 3.4.2 or compile server from sources. |
Comment by Jitendra Gondaliya [ 2017 Sep 19 ] |
Hi Team, We have updated zabbix from 2.4 to 3.4.1 and we see same errors. can we downgrade from 3.4.1 to 3.4.0, will same DB schema work for both version. Thanks, |
Comment by Jitendra Gondaliya [ 2017 Sep 19 ] |
Forgot to mention that we have installed zabbix from RPM. |
Comment by Ilmar Soobik [ 2017 Sep 20 ] |
" In most of systems the only problem might be notification about unsupported items, otherwise the data gathering is not affected. " Unless you have thousands of items which require preprocessing - then your unreachable pollers will simply die and the preprocessor manager will crash. |
Comment by Jitendra Gondaliya [ 2017 Sep 20 ] |
we have downgraded to 3.4.0-1 and now we dont see any such errors. Now we have different issue is there is lag in the data collected or plotted in the graph (around 1 hr lag and it increase over the time). We tried restating DB, zabbix but no luck and also we dont see much items in queue. our DB size is +200GB and table history_uint is +180GB. its seems DB issues to me. There are couple of blogs which which suggest to drop old data from this table and keeping only last few weeks data. will this help to improve DB performance. Thanks, |
Comment by Adrien Demma [ 2018 Feb 02 ] |
I seem to encounter this problem (but without the preprocessing part so probably not the same). Sometimes an item becomes unsupported and just after becomes supported again. It is flooding us with email alerts. |