#2333 error on subcontainer 'swrun container' insert (-1)

[drook]

FreeBSD 8.2-STABLE
net-snmp 5.7.1 installed from ports

I get tonns of messages like "error on subcontainer 'swrun container' insert (-1)".

Being ran with -DALL I can see:

compare:index: compare .4756 to .4756
compare:index: result was 0
trace: netsnmp_binary_array_insert(): container_binary_array.c, 403:
container: not inserting duplicate key
error on subcontainer 'swrun container' insert (-1)
compare:index: compare .49357 to .4756
compare:index: result was 1
compare:index: compare .38311 to .4756
compare:index: result was 1
compare:index: compare .20808 to .4756
compare:index: result was 1
compare:index: compare .9300 to .4756
compare:index: result was 1
compare:index: compare .5278 to .4756
compare:index: result was 1
compare:index: compare .5248 to .4756
compare:index: result was 1
compare:index: compare .5246 to .4756
compare:index: result was 1
compare:index: compare .4756 to .4756
compare:index: result was 0
trace: netsnmp_binary_array_insert(): container_binary_array.c, 403:
container: not inserting duplicate key
error on subcontainer 'swrun container' insert (-1)
compare:index: compare .49357 to .4756
compare:index: result was 1
compare:index: compare .38311 to .4756
compare:index: result was 1
compare:index: compare .20808 to .4756
compare:index: result was 1
compare:index: compare .9300 to .4756
compare:index: result was 1
compare:index: compare .5278 to .4756
compare:index: result was 1
compare:index: compare .5248 to .4756
compare:index: result was 1
compare:index: compare .5246 to .4756
compare:index: result was 1
compare:index: compare .4756 to .4756
compare:index: result was 0
trace: netsnmp_binary_array_insert(): container_binary_array.c, 403:
container: not inserting duplicate key
error on subcontainer 'swrun container' insert (-1)
compare:index: compare .49357 to .4756

[Steve Polyack]

We're seeing the same behavior on FreeBSD 8.1-RELEASE.

[Dave Shield]

What logging options do you have set?
I've checked the code, and this message should only be generated if you have 'debug' level logging enabled.
For normal operation, this "error" situation should be silent
(at least for version 5.4.2 and 5.5 and above)

[drookie]

I can confirm this closed in 5.7.2.pre1. Please close this pr.

Thanks for a great work, guys.

[drookie]

For some reason it's back in 5.7.3.

[Brahma]

We are still facing the same issue on net-snmp-5.7.1. with FB10.1 kernel .could you please share the relavnt patch.

[Satish ish]

          This error is even produced with combo of net-snmp-5.7.3 and FreeBSD 10.1. Kindly share any relevant patch to eliminate this error.

Thanks in advance,
Satish

[drookie]

There's no solution and net-snmp is more and more like abandonware. Nobody of the developers cares about it. A bunch of reported bugs stays unresponded. This bug is the lesser evil of all, there's more harmful one when net-snmp reports absolutely weird counter values for hardware interfaces. I've switched to the bsnmpd on FreeBSD and I advise everyone to do the same.

[Bart Van Assche]

Please verify whether commit 024c6316eb1f ("SNMP-TARGET-MIB, FreeBSD: Hide kernel threads") fixes this. See also https://sourceforge.net/p/net-snmp/bugs/2890/.