From 30919d352bb08178825a9b393078a67f9fcab1d6 Mon Sep 17 00:00:00 2001 From: PixelPlex Dev team <10460630+pixelplex@users.noreply.github.com> Date: Wed, 28 Aug 2024 11:59:35 +0300 Subject: [PATCH] Update data about archive node sync timings (#720) Co-authored-by: Full-Hat --- docs/participate/run-nodes/archive-node.md | 14 ++++++++++++-- .../participate/run-nodes/nodes-troubleshooting.md | 5 +++++ 2 files changed, 17 insertions(+), 2 deletions(-) diff --git a/docs/participate/run-nodes/archive-node.md b/docs/participate/run-nodes/archive-node.md index 07257665a4..0de7ffea30 100644 --- a/docs/participate/run-nodes/archive-node.md +++ b/docs/participate/run-nodes/archive-node.md @@ -83,7 +83,7 @@ To install **testnet** dump use: wget --user --password -c https://archival-dump.ton.org/dumps/latest_testnet.zfs.lz | pv | plzip -d -n | zfs recv data/ton-work ``` -Size of the dump is __~1.5TB__, so it will take some time to download and restore it. +The size of the dump is approximately __4TB__, so it may take several days (up to 4 days) to download and restore. The dump size can increase as the network grows. Prepare and run the command: 1. Install the tools if necessary (`pv`, `plzip`) @@ -131,7 +131,17 @@ nano /etc/systemd/system/validator.service ``` :::info -Please be patient once you start the node and observe the logs. Dumps come without DHT caches, so it will take your node some time to find other nodes and then sync with them. Depending on the age of the snapshot, your node might take from a few hours to several days to catch up with the network. This is normal. +Please be patient once you start the node and observe the logs. +Dumps come without DHT caches, so it will take some time for your node to find other nodes and sync with them. +Depending on the age of the snapshot and your internet connection speed, +it might take your node anywhere **from a few hours to several days** to catch up with the network. +**On a minimum setup, this process can take up to 5 days.** +This is normal. +::: + +:::caution +If the node sync process has already taken 5 days, but the node is still out of sync, you should check the +[troubleshooting section](/participate/run-nodes/nodes-troubleshooting#archive-node-is-out-of-sync-even-after-5-days-of-the-syncing-process). ::: #### Start the node diff --git a/docs/participate/run-nodes/nodes-troubleshooting.md b/docs/participate/run-nodes/nodes-troubleshooting.md index cb9cd2908b..3e1203a5c6 100644 --- a/docs/participate/run-nodes/nodes-troubleshooting.md +++ b/docs/participate/run-nodes/nodes-troubleshooting.md @@ -30,6 +30,11 @@ Try to perform following checks: 3. Is there NAT between the machine and the internet? If so, ensure that the IP address defined in the `addrs[0].ip` field of the `/var/ton-work/db/config.json` file corresponds to the real public IP of the machine. Note that the value of this field is specified as a signed INT. The `ip2dec` and `dec2ip` scripts located in [ton-tools/node](https://github.com/sonofmom/ton-tools/tree/master/node) can be used to perform conversions. +## Archive node is out of sync even after 5 days of the syncing process + +Go through the checklist [from this section](/participate/run-nodes/nodes-troubleshooting#about-no-progress-in-node-synchronization-within-3-hours). + + ## Cannot apply external message to current state : External message was not accepted ```