Initial node sync failing?

[Mandelhoff]

I got a fresh clone about 10 minutes ago. I did the start:sync() and it sync'd for a while. It seems to stall out.

I can run api:height(). and it tells me 2254 which is the height that your Explorer web page shows, but I keep getting timeouts and getblock errors like the screenshot.

The pool also gives an error saying the node isn't sync'd.

[zack-bitcoin]

what does block:height(). return?
api:height only tells you how many headers you have downloaded. Headers are a lot quicker than blocks.

It seems like your node is trying to contact one of the other nodes, and it is failing.

Is this your public node?
Are you mining?

When mining, the nodes contact each other regularly, and it would make sense if the message would occasionally fail, since my node has a lot of traffic and the software isn't perfect.

[Mandelhoff]

Public node - yes.
Mining - no. (My pool wouldn't start.)

I gave it a make prod-clean and then build. It's syncing well now.

If you have any tips about preventing the sync timeouts, please let me know.

[zack-bitcoin]

When you go offline, my node deletes yours from the list of peers.
And when you go offline, you delete your own list of peers.

[zack-bitcoin]

fixed sync:stop().
If you want to turn a node off while it is syncing, it is probably safest to stop the syncing first before you do api:off().