[Bug] MultiIndex measurement not reloaded on some cases - use of closed network connection #524
Comments
sbengo
pushed a commit
that referenced
this issue
Nov 15, 2022
On the measurement gatherloop the measurement is marked as non-connected if it becomes unresponsive or the metrica cannot be retrieved for some connectivity reason. When it happens, the gatherloop tries to reconnect again querying complete sysinfo and resets the snmpclient This PR tries to fix the logic of the snmpclient inherit from the measurement, as it is using a pointer of a copy instead of the original snmpclient. In this case, any change on the measurement snmpclient doesn't populates to the multiindex measurement snmpclient, and an already closed connection was being used and the load index is not being done and all the indexes were remain as the last time that they got gethered (wrong if the processed failed at some point) fix #524
sbengo
added a commit
that referenced
this issue
Nov 15, 2022
On the measurement gatherloop the measurement is marked as non-connected if it becomes unresponsive or the metrica cannot be retrieved for some connectivity reason. When it happens, the gatherloop tries to reconnect again querying complete sysinfo and resets the snmpclient This PR tries to fix the logic of the snmpclient inherit from the measurement, as it is using a pointer of a copy instead of the original snmpclient. In this case, any change on the measurement snmpclient doesn't populates to the multiindex measurement snmpclient, and an already closed connection was being used and the load index is not being done and all the indexes were remain as the last time that they got gethered (wrong if the processed failed at some point) fix #524
sbengo
added a commit
that referenced
this issue
Nov 15, 2022
On the measurement gatherloop the measurement is marked as non-connected if it becomes unresponsive or the metrica cannot be retrieved for some connectivity reason. When it happens, the gatherloop tries to reconnect again querying complete sysinfo and resets the snmpclient This PR tries to fix the logic of the snmpclient inherit from the measurement, as it is using a pointer of a copy instead of the original snmpclient. In this case, any change on the measurement snmpclient doesn't populates to the multiindex measurement snmpclient, and an already closed connection was being used and the load index is not being done and all the indexes were remain as the last time that they got gethered (wrong if the processed failed at some point) fix #524
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After the gather refactor logic - the gather loop is done and managed by measurements instead of devices - the load index process (every device FilterFreq or measurement override) tries go refresh the current indexes
The following log entry appeared on some devices:
All the following entries refers to the same origin. After a deep analysis to find the root cause, it seems related with:
The text was updated successfully, but these errors were encountered: