[AGENT++] SNMP++ walk error. Transport operation failed. error 10055

[Jochen Katz]

Hi,

error 10055 is a windows error code and it looks like your application
does not close all open sockets (I found: "Error 10055 means that
Windows has run out of TCP/IP socket buffers because too many
connections are open at once"). Do you delete all created Snmp objects?

I would recommend that you create one Snmp object at startup (or one for
each thread you have) and reuse this object for all quests.

About the IPv6 issue: The send function maps the IP to IPv6 if IPv4
fails and as IPv6 is disabled you get the error message. This is clearly
a bug, that will be fixed (The error message should only be displayed if
the user passes a IPv6 address to snmp++).

Regards,
  Jochen


Anders_Koepping at gmx.de schrieb:
> I have a problem concerning SNMP++:
> 
> I created an application that polls a switch every second for statistical values. The switch has 16 ports, so i did that with "snmpwalk" activating the "subtree" function.
> After some time of processing (about 5-10 minutes) I get an error saying: "snmp Walk Error. Transport operation failed". After those 5 minutes this message appears after every poll. So no further snmpwalk requests happen. Increasing the timeout (from 200 to 5000 ms and in-between) does not help.
> 
> after those 5 minutes SNMP log says:
> Call to bind throws error 10055
> User error: Enable IPv6 and recompile snmp
> Why is SNMP++ sending to a IPv6 address after those 5 minutes?
> 
> before the error SNMP log says:
> ++ SNMP++: sending to 192.168.2.138/161:
> afterwards it says:
> ++ SNMP++: sending to [0000:0000:0000:0000:0000:ffff:c0a8:028a]/161
> 
> 
> what does this error code 10055 mean? Is it that WinSocket Buffer is at its maximum? Or is the switch agent overloaded?
>  
> 
> Any help would be appreciated.
> 
> Andy