Uptime reports delayed while node is online and connected #2328
Comments
|
Here's another case that's slightly different but I think still fits the pattern. Node id is 6774. This happens during a farmerbot wake up. Uptime is logged when the node boots up: We'd expect to see an uptime report made 40 minutes later, but there's no connection to tfchain corresponding precisely with the expected timestamp: When the node does finally send an uptime report before shutting down, it cycles through the tfchain nodes without errors except on the usual suspect 03 (this behavior I also didn't see before): |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've had a couple different reports from different farmers that their nodes are showing brief period of downtime without a clear cause.
Example 1
Here's one example (times are CEST in this case):
And here are a selection of relevant log entries for node 5158:
Example 2
Here's another example (EDT this time):
Logs:
I've included the logs from provisiond here to show that the node has nearly simultaneous successful communication with tfchain at the time it also tried to submit its uptime report and failed.
Example 3
Here's one more example (PDT here):
This seems to be widespread. The last example is happening to my own node as I write this. I haven't noticed any network outages on my uplink, and nor has anything changed with this node.
The text was updated successfully, but these errors were encountered: