Latest mainnet blocks show 0 for all columns if dcrd disconnects
monsa00 opened this issue · 4 comments
It appears that if the dcrd rpc host disconnects dcrdata does not fully recover unless it's restarted. The logs will show an error:
[WRN] JAPI: updateNodeConnections: failed to get connection count: the client has been shutdown
The dcrd logs show that dcrdata does reconnect, and dcrdata doesn't show any major error other than the above.
This is what shows until dcrdata is restarted:
It appears that if the dcrd rpc host disconnects dcrdata does not fully recover unless it's restarted. The logs will show an error:
[WRN] JAPI: updateNodeConnections: failed to get connection count: the client has been shutdown
The dcrd logs show that dcrdata does reconnect, and dcrdata doesn't show any major error other than the above.
@chappjc, From your comments here #1130 disabling auto-reconnect was intentional so the dcrdata will sync properly if it missed any block while the node client was down.
For the zero blocks display, I think we can/should display some information from the db, right? Related #356
For the zero blocks display, I think we can/should display some information from the db, right?
Maybe. It could be a lot of code and queries since we just use RPCs for many such things. Really does not seem worth it since the dcrdata needs to be restarted anyway.
Maybe. It could be a lot of code and queries since we just use RPCs for many such things. Really does not seem worth it since the dcrdata needs to be restarted anyway.
Well since dcrdata is handicapped without dcrd there is nothing to do about this for now. Maybe this can close?
If the node is down, this is not a dcrdata problem. Agree.