Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update data about archive node sync timings #720

Merged
merged 1 commit into from
Aug 28, 2024
Merged

Update data about archive node sync timings #720

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions docs/participate/run-nodes/archive-node.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ To install **testnet** dump use:
wget --user <usr> --password <pwd> -c https://archival-dump.ton.org/dumps/latest_testnet.zfs.lz | pv | plzip -d -n <cores> | 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`)
Expand Down Expand Up @@ -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
Expand Down
5 changes: 5 additions & 0 deletions docs/participate/run-nodes/nodes-troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

```
Expand Down
Loading