I’m following the guides to setup a node on the mainnet, but the catchup operation does not complete. It times out after 45 minutes approximately 2/3’s of the way through. I’m running the run the following commands: ./update.sh -i -c stable -p ./node -d ./node/data -n ./goal node start -d data .…

Thanks @fabrice , Yes, I tried that, but I’m not gettting download errors. I’m getting the following error: :“warning”,“line”:344,“msg”:“dbatomic: tx surpassed expected deadline by 6.730578955s”,“name”:"",“readonly”:false,“time”:“2020-11-08T15:18:14. 046234-08:00”} Also, I didn’t mention it in t…

@worrymite , The dbatomic warning message is most likely benign; it would not prevent your from completing the catchup, however it might indicate that you have a slower than desired storage device. If you could confirm what type of storage device you have, it would be great. ( HDD, SSD, nvme, other …

Thanks @tsachi , The data is being written to an SSD, no other processes were running. The memory usage is steady and it doesn’t swap out of RAM. Do I need to open up any port in my firewall to better talk to the servers or peers (I’m not clear on that part of the protocol)? Is there any mid-poin…

@worrymite , Thanks for the storage device update. No, there is no need to open any ports; if the algod was able to start the download progress, then all the communication needs have already been met. For security reasons, there is no mid-point catchpoint data. It downloads and calculate the hash i…

I’ve been wrestling with this problem myself, I tried with 3 different machines and none could complete fast catchup before restarting after 45 minutes. I don’t know if there are any config params that can be tuned, I tried messing with them but didn’t notice much of a difference. It seemed like s…

Some supplemental information, I built algod with maxCatchpointFileDownloadDuration set to a much higher number and I do get further, it runs longer than 45 minutes, but it still fails with “unable to download ledger : http: unexpected EOF reading trailer” and restarts.

Hi @jiffe , Sounds like some good experiments. I infer from @tsachi message that the 45 minute timeout is also enforced by the other peers/relays in the network. Here is what I’m doing and it is working so far. I’m doing the catchup with to an older point. This is ~8.5 million blocks and the cur…

Thanks @worrymite , Using this catchpoint I was able to complete fast catchup and its now syncing the rest of the way.

@jiffe and @worrymite , thanks for your the details you’ve provided. It’s really helpful to get constructive feedback like yours. The idea of running algod with an in-memory storage was really creative one ;-). Could you please confirm that you both were running 2.2.0 ( or equivalent ) codebase ? …

Can't complete catchup operation on mainnet -- timeout after 45 minutes (~4m accounts)

General

fabrice November 9, 2020, 2:20am 2

Welcome @worrymite!

Have you tried Fast Catchup not working for our node on MainNet?

Topic		Replies	Views
Mainnet Fast Catchup Stalling General fast-catchup	6	479	February 7, 2022
Fast Catchup not working for our node on MainNet	53	5356	October 7, 2020
Fast catchup for mainnet General mainnet	11	1194	August 27, 2021
Fast catchup does not work on Raspberry Pi 4B General mainnet	24	1404	May 24, 2021
Fast catchup not synchronizing General	2	477	June 15, 2021

Can't complete catchup operation on mainnet -- timeout after 45 minutes (~4m accounts)

Related topics