Centos 7

Hello!

As I see current status is resolved.
Could you, please, point me to patch or revision with resolution, so I'll be able to fix this locally before 3.4.2rc1 is out?

Thank you!

It's resolved, but not yet tested/finished.

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.

Thank you for clarification, and...
If it is tested - may I use it?
Thank you!

Sure, you can get the patch from development branch svn://svn.zabbix.com/branches/dev/ZBX-12618

Available in 3.4.2rc2 r71803 and 4.0.0alpha1 (trunk) r71809

Unfortunately, looks like it is not available anonymously:

svn: E170000: URL 'svn://svn.zabbix.com/branches/dev/ZBX-12618' doesn't exist

Thank you!

Sorry, it got merged into main branches. Feel free to use svn://svn.zabbix.com/branches/3.4 fix is already there.

Thank you for your report, patch attached.

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!

Please be advised that /src/zabbix_server/preprocessor/preprocessing.c was changed as well.

Oops! Thank you!
rebuilding...

Hello, sorry that I'm write in resolved theme.
I have similar problem, but with disk perfomance stats.
"6525:20170905:181505.541 item "hostname:vfs.dev.read[vda1,ops]" became not supported: Item preprocessing step #1 failed: (null)
6527:20170905:181507.513 item "hostname:vfs.dev.read[vda15,ops]" became not supported: Item preprocessing step #1 failed: (null)"

Do I need to create new bug? If no, how can I apply this fix to my server which installed from packages?

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.

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,
Jitendra

Forgot to mention that we have installed zabbix from RPM.

" 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.

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,
Jitendra

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.
I'm on 3.4.6 though.