Ilya Etingof
> because the OID is perfectly in the scope of the requested OID. You mean we should not report that EOM oid-value at the end? Trouble is that if you...
Thank you for reporting this issue! Did I get it right, that the Python file being generated (i.e. MIB) is failing to be parsed because of unescaped unicode code (i.e....
It's something about your building environment... Let's see which `pysnmp` you are importing: ``` >>> import pysnmp >>> pysnmp.__path__ ['/home/user/pysnmp/pysnmp'] ``` If it's a wrong one, try `$PYTHONPATH`: ``` PYTHONPATH=/home/user/pysnmp...
May be you need to: export PYTHONPATH=/etingof/pysnmp/pysnmp to make sure this variable gets into python environment as well?
This is curious... Let's add this at the beginning of the script and give it another run: from pysnmp import debug debug.setLogger(debug.Debug('msgproc', 'secmod'))
Ah, indeed, that's the missing `ContextData` parameter! Somehow your only OID got consumed as `ContextData` (which is ignored if SNMPv1/v2c is in use). Therefore no OIDs remain in the `getCmd`...
> Okay well, that's a bit weird. Are you sure it's a normal behavior ? I mean, it's really hard to understand what's going on... Absolutely, I will push a...
That is a bug in pysnmp which I'm trying to fix. So this just to acknowledge that your report is not forgotten. ;-)
Make sure you are using the latest pysnmp version. If the error does not go away with the most recent pysnmp, I'd probably need some debugging info to see what...
@sydneyli Would you please take a look...? ;-)