Closed netniV closed 1 year ago
This is confirmed as a spine bug
Running Spine v1.2.23 produces the following output:
2022/11/23 05:30:01 - SPINE: Poller[1] PID[24670] PT[140235009996544] Device[55] Updating Full System Information Table
2022/11/23 05:30:01 - SPINE: Poller[1] PID[24670] PT[140235009996544] ERROR: Failed to get oid '.1.3.6.1.6.3.10.2.1.3.0' for Device[55] with Response[2]
2022/11/23 05:30:01 - SPINE: Poller[1] PID[24670] PT[140235009996544] DEBUG: Device[55] HT[1] RECACHE: Processing 5 items in the auto reindex cache for '<IP>'
2022/11/23 05:30:01 - SPINE: Poller[1] PID[24670] PT[140235009996544] Device[55] HT[1] DQ[1] Legacy Uptime Result: 703767000, Is Numeric: 1
2022/11/23 05:30:01 - SPINE: Poller[1] PID[24670] PT[140235009996544] ERROR: Failed to get oid '.1.3.6.1.6.3.10.2.1.3.0' for Device[55] with Response[2]
2022/11/23 05:30:01 - SPINE: Poller[1] PID[24670] PT[140235009996544] Device[55] HT[1] DQ[1] Extended Uptime Result: , Is Numeric: 0
2022/11/23 05:30:01 - SPINE: Poller[1] PID[24670] PT[140235009996544] Device[55] HT[1] DQ[1] RECACHE OID: .1.3.6.1.2.1.1.3.0, (assert: 703761000 < output: )
2022/11/23 05:30:01 - SPINE: Poller[1] PID[24670] PT[140235009996544] Device[55] HT[1] DQ[1] RECACHE ASSERT FAILED: '703761000<'
2022/11/23 05:30:01 - SPINE: Poller[1] PID[24670] PT[140235009996544] Device[55] HT[1] NOTICE: Spike Kill in Effect for '<IP>'
2022/11/23 05:30:01 - SPINE: Poller[1] PID[24670] PT[140235009996544] Device[55] HT[1] DQ[10] RECACHE OID: .1.3.6.1.2.1.1.3.0, (assert: 703761000 < output: 703767000)
2022/11/23 05:30:01 - SPINE: Poller[1] PID[24670] PT[140235009996544] Device[55] HT[1] DQ[11] RECACHE OID: .1.3.6.1.2.1.1.3.0, (assert: 703761000 < output: 703767000)
2022/11/23 05:30:01 - SPINE: Poller[1] PID[24670] PT[140235009996544] Device[55] HT[1] DQ[12] RECACHE OID: .1.3.6.1.2.1.1.3.0, (assert: 703761000 < output: 703767000)
2022/11/23 05:30:01 - SPINE: Poller[1] PID[24670] PT[140235009996544] Device[55] HT[1] DQ[13] RECACHE OID: .1.3.6.1.2.1.1.3.0, (assert: 703761000 < output: 703767000)
Note the Extended Uptime Result is blank, and so is the final RECACHE OID result.
Describe the bug
Under 1.2.23, if you run Spine v1.2.23 this appears to cause constant recaching events for various devices. For example, a Mikrotik running RouterOS will suddenly cause lots of reindexing if your method is set to uptime. The logs show a blank for one of the two uptime comparison values suggesting it doesn't know what it was, ergo it initiates a reindex.
Running an snmpget against the device shows that only the older uptime OID is supported:
Rolling Spine back to v1.2.20 (the previous version installed) stopped these messages from appearing. This may be a spine issue or a core issue so it's being logged here until it's known. If it becomes a spine-specific issue, this issue can be moved to that repository.
Sample logs
Expected behaviour
Since both should be known, the
RECACHE ASSERT FAILED: '701004300<'
log notice should show two uptime values (current vs previous).