Mirobit
commented
3 years ago I hope that I finally fixed this (f940e45). Please let me know if the errors from the second screenshot are still happening.
Closed mcjoshea closed 3 years ago
Mirobit
commented
3 years ago I hope that I finally fixed this (f940e45). Please let me know if the errors from the second screenshot are still happening.
mcjoshea
commented
3 years ago Not yet :-(
Sometimes it looks fixed but then when I do a refresh it comes back.
Remember that I have to stop and start the node for all this to happen. Never usually see it. The error only occurs up to the point when the geolocation request picks up the first node's location.
Where the there are more error lines than usual, that's when I manually refreshed the page, possibly a few times.
Let me know if you would like me to follow a set of predefined steps to help with the fault finding. Not sure how useful it is with me just randomly pressing refresh!
Mirobit
commented
3 years ago Okay this is weird. This doesn't seem to be related to the geo tracing. The errors happen in a part of the code that only interacts with Bitcoin Core. It seems that Bitcoin Core didn't have some information for certain peers at the time of the request. If you refresh after a few seconds Core apparently is able to provide this information. But I can't explain why these errors stop as soon as the first geo call is made.
For now I am out of ideas, since I am not able to reproduce it. You could try to update to 0.20.1 but I don't think that is the issue.
mcjoshea
commented
3 years ago Thanks for trying. Not a big deal really as it goes away after a minute or two, and only occurs after if I restart the node.
Not sure if it makes any difference but my node is running as a Snap image (https://snapcraft.io/bitcoin-core) on a Raspberry Pi 3 Model B+ running Linux bitcoin-pi 5.4.72-v7+ #1356 SMP.
mcjoshea
commented
3 years ago Just a quick update. I restarted my node again and got no error at all.
All I did was add a whitelist IP address to the node's config file and removed this: peerbloomfilters=1
As usual there was no geo info for a while after restarting the node but this time there were no errors.
I restarted my node today and noticed these errors:
A short while later I did a refresh and got this:
As soon as the geo tracing picked up the first IP address the errors went away.
I had just updated BNM to the very latest version so not sure if that had anything to do with this. I seem to remember seeing this before but did not mention it as it went away within minutes.