Introduce synchronous=auto as new default value for the driver setting
#1315
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ainloop(): trace connection faults and reconnections better
…y-chain device" debug log
…vice.0" when in daisy-chain context (skip anyway even for singular devices where we should also walk .1 anyway)
…if not a daisy-chain, for balance
…mber) devices, walk a ".1" device only (should end up querying non-templated OIDs anyway) - avoid walking .0 partially and .1 again for same data
…" when logging that write failed
…ng; log the faults (and successes) at level 1
… 1 now, and without a dot-number (to avoid confusion)
… and if it helped
…e maybe) and so driver is disconnecting
… (now by default) so reconnections would be sync
…WARNING more visible
…t less verbose (level 6)
…k from send_to_one()
jimklimov
added
SNMP
raspberry
service/daemon start/stop
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #1309
Also
Closes: #1314 (to not snmpwalk an "unitary" device twice)
Some commits picked from #320
While the issue was discovered with snmp-ups driver, the problem after analysis seems to generally impact drivers with many data points, depending on performance and competing workload of the machines running the drivers and data server. I suspect this may be why reports with particularly Raspberry Pi, especially of older revisions, were prominent in the recent years of issue tracking.