-
-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pysnmp seems stuck intermittently #432
Comments
UDP isn't a reliable protocol, so when you sent out SNMP GET requests (like the log showed) you should expect a certain amount of requests to fail with timeout (request/response lost on the wire, or agent slowly responded). Actions are only required if you observe a significant amount of timeout cases. Most likely the cause is on agent side (busy agent or busy machine), so only digging into manager side log as above won't give you the whole picture. |
Hi Lex @lextm thanks for responding. |
@adarsh-chauhan I wonder what you meant by "the control should be given back to the caller". A library like PySNMP has to respect the timeout you give or preset value, and actually wait that long for a response from the remote agent. As the caller of PySNMP API, it will be your code to decide whether it will call and wait for PySNMP on the same thread, or call PySNMP asynchronously. Note that asynchronously calling a socket API (not only SNMP or PySNMP) is widely adopted. So, I don't think there is anything needed to change on PySNMP side. I guess your concern is more related to specific applications, such as AWS Lambda, the throughput and the possibly cost increase. But that's another story about code optimization, not PySNMP's defect. |
Hi Team,
We are using pysnmp version
4.4.9
library in AWS Lambda and it seems pysnmp to be stuck at times.In our config we are doing 1 second of timeout with 1 retry, total 2 seconds for unresponsive devices.
We use
bulkcmd
andgetCmd
.getCmd
snippetbulkCmd
snippetLast 3 lines, it seems that pysnmp was stuck.
can someone tell me what are we doing wrong or if this is actually an anamoly ?
The text was updated successfully, but these errors were encountered: