Open Sjors opened 1 month ago
This is symptomatic of a slow startup, potentially on a host that was dedicated to the background sync. Looking at the node now, it does look normal.
Background: we occasionally start the node in the background to have it sync up with the blockchain. This is done to allow the node not to have to first sync hundreds of blocks when the user starts it, presumably because they want to either send or receive. We have a separate pool of resources for these background syncs, and users may end up on those heavily loaded machines if they get unlucky. We should really preempt the node, and re-schedule it on the interactive pool. This may add a bit of startup time, but it'd result in a much better user experience.
Just tried again and got the same error. Waiting 30 seconds and trying again didn't help either.
Did you call stop
? If not the node will continue running for up to 15m, and any issues due to its location will only be resolved after it cycled once.
I had not tried that.
% glcli stop
[2024-08-09 15:49:45,037 - INFO] Configuring client with device credentials (legacy)
Node shut down
But still getting the same error calling getinfo
after that.
(tried another stop
and info
but no luck)
I tried to access a node that I created a year ago.
First I manually installed from master @ b9d1ecb9ea7325b041d08ddc171486fdad646a63 (see also #491).
From the directory with my earlier configuration I call:
Which after about 10 seconds returns:
Node id 036387fa666993defcf79719d5cdb3e1243d694e4a71922878c3dc83c4e65872ab.