Exception TypeError: 'expected string or Unicode object, NoneType found'

[saeedghx68]

Hi I test this code

session = Session(hostname='x.x.x.x', community='PTSsnmpCacti', version=2, retries=3, timeout=40)
#for use change dslam port admin status:
session.set('1.3.6.1.2.1.2.2.1.7.101', '2')

I gave this error:
Exception TypeError: 'expected string or Unicode object, NoneType found' in <module 'threading' from '/usr/lib/python2.7/threading.pyc'> ignored

[mynever]

Hi, try to check this in python 3.x version.

[saeedghx68]

tnx @mynever dear ,My problem was solved with python3.x but i using python 2.7 .
Why is there a problem in Python2.7?

[mynever]

truly saying, i've checked this oid in my enviroment.
everything is fine.

Python 2.7.10 (default, Mar 16 2016, 16:34:50) 
[GCC 4.9.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from easysnmp import Session
>>> session = Session(hostname='x.x.x.x', community='x', version=2, retries=3, timeout=40)
>>> session.set('1.3.6.1.2.1.2.2.1.7.1', '2')
True
>>> session.set('1.3.6.1.2.1.2.2.1.7.1', '1')
True
>>> 

Try to check your versions of easysnmp and python 2.7.

[saeedghx68]

hi @mynever , tnx for reply
OS :Debian 8
Python : 2.7.9
easysnmp: 0.2.4
I was really confused

[mynever]

btw, u can also try this one fork

[kamakazikamikaze]

@saeedghx68 Did you encounter this error while attempting to multithread your code?

[saeedghx68]

Hi @kamakazikamikaze
No, I don't using multi-threading.

[AyoCross]

same error occurred to me(ubuntu16.04, python 2.7.9), when i use multiprocessing.Queue in a sub-tread.
It's OK in the main-thread. so weird.....if you have fixed this problem, please tell me...THX

[kamakazikamikaze]

This is similar to #34 where multi-threading does not work properly. Unfortunately I have not yet been able to look into these as they are currently low priority.

@AyoCross I would need to see some sample code to understand how you're using it. I assume that you're sharing sessions rather than results? When I was using using multiprocessing at my former workplace, we used multiprocessing.Manager.Queue instead to return SNMPVariables.

@saeedghx68 I would need to see a sample of the code you use as well. You say that this is not an issue in Python 3 but it is a problem in Python 2? I'm trying to understand how the threading module is being involved. Are you serializing/pickling anything?

[kamakazikamikaze]

@AyoCross Are you using v0.2.4 or the latest commit? I'm able to duplicate this while running tests on Raspbian Jessie and macOS, but Mint/Ubuntu is returning just fine

[AyoCross]

@kamakazikamikaze my error occurred when i put unserializable object into Queue, not because easysnmp....sorry

[kamakazikamikaze]

@AyoCross No worries! If you haven't seen it already, maybe dill could help serialize it

[AyoCross]

@kamakazikamikaze THX, that helps me a lot.

[kamakazikamikaze]

@mynever I think the reason why you may have had that issue is that your MIBs weren't loaded fully in the threads.

I came across this error myself when I tried using the dotted notation, ex. .1.3.6.1.2.1.31.1.1.1.18.10101. I had to manually specify the SNMP type unless I went with the full MIB name, ex. easysnmp.snmp_set('.1.3.6.1.2.1.31.1.1.1.18.10101', 'testing', 's', hostname='192.168.1.1') instead of easysnmp.snmp_set('IF-MIB::ifAlias.10101', 'testing', hostname='192.168.1.1').

If you were having success in the main thread using dot-notation without specifying type, but not in a sub-thread, perhaps it's an environment variable that isn't set when threads are created, therefore your snmp.conf file and MIBs are not being loaded?

There's too much going on to say for certain, but that would be my best guess.