From e579091ffc080b033021b9c3d0521b8cf68e240d Mon Sep 17 00:00:00 2001 From: Gleb Karavatski Date: Thu, 31 Oct 2024 12:06:19 +0300 Subject: [PATCH 1/4] node slow sync potential reasons --- docs/v3/guidelines/nodes/nodes-troubleshooting.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/v3/guidelines/nodes/nodes-troubleshooting.md b/docs/v3/guidelines/nodes/nodes-troubleshooting.md index b65521fac9..3a8514a1ef 100644 --- a/docs/v3/guidelines/nodes/nodes-troubleshooting.md +++ b/docs/v3/guidelines/nodes/nodes-troubleshooting.md @@ -34,6 +34,11 @@ Try to perform following checks: Go through the checklist [from this section](/v3/guidelines/nodes/nodes-troubleshooting#about-no-progress-in-node-synchronization-within-3-hours). +## Slow sync potential reasons + +1. The disk is relatively weak. It's advisable to check the IOPS of the disk (though sometimes hosting providers exaggerate these numbers). +2. Updates coincided with network congestion. However, the slow synchronization is due to the load, not the updates. The full node cannot catch up with the network because there were about 100 million transactions. +3. Since the default value of keep history for a Full Node state has been reduced to one day, there are fewer Full Nodes in the network that can provide older states, may cause making it harder to sync with such a delay. ## Cannot apply external message to current state : External message was not accepted From c9eebf1f307fb6997b8c7eaf36735e306027a8f1 Mon Sep 17 00:00:00 2001 From: Aliaksandr Bahdanau Date: Thu, 31 Oct 2024 16:32:40 +0300 Subject: [PATCH 2/4] fix: fix build --- docusaurus.config.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docusaurus.config.js b/docusaurus.config.js index f6b224bb3b..319ee631bc 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -8,7 +8,7 @@ const getEnvLangConfig = () => { const langArray = process.env.TARGET_LANGS ? process.env.TARGET_LANGS.split(",") - : []; // ["mandarin"]; TODO: uncomment when done + : ["mandarin"]; // : ["mandarin", "ru", "ko", "pl", "uk", "ja"]; const locales = Array.from(new Set([defaultLocale, ...langArray])); From 5ba877e16964d1dd284d66ea8dee82c948ee8637 Mon Sep 17 00:00:00 2001 From: Gleb Karavatski Date: Mon, 4 Nov 2024 14:52:00 +0300 Subject: [PATCH 3/4] add MyTonCtrl errors article --- .../infra/nodes/mytonctrl/mytonctrl-errors.md | 44 +++++++++++++++++++ .../guidelines/nodes/nodes-troubleshooting.md | 1 + sidebars/documentation.js | 35 ++++++++------- 3 files changed, 63 insertions(+), 17 deletions(-) create mode 100644 docs/v3/documentation/infra/nodes/mytonctrl/mytonctrl-errors.md diff --git a/docs/v3/documentation/infra/nodes/mytonctrl/mytonctrl-errors.md b/docs/v3/documentation/infra/nodes/mytonctrl/mytonctrl-errors.md new file mode 100644 index 0000000000..ddbe9b3d5b --- /dev/null +++ b/docs/v3/documentation/infra/nodes/mytonctrl/mytonctrl-errors.md @@ -0,0 +1,44 @@ +# MyTonCtrl errors + +## Overview + +This article describes MyTonCtrl errors that a user may encounter. + +## Common errors + +| Error | Possible solution | +|:---------------------------------------------------------------------------|:----------------------------------------------------------------------| +| Unknown module name: `name`. Available modes: `modes` | Check available modes list | +| No mode named `name` found in current modes: `current_modes` | Check current modes list | +| GetWalletFromFile error: Private key not found | Check wallet name path | +| Cannot get own IP address | Check access to the https://ifconfig.me/ip and https://ipinfo.io/ip resources | + + +## Liteserver errors + +| Error | Possible solution | +|:---------------------------------------------------------------------------|:----------------------------------------------------------------------| +| Cannot enable liteserver mode while validator mode is enabled | Use `disable_mode validator` | +| LiteClient error: `error_msg` | Check MyTonCtrl parameters for running Liteserver | + +## Validator errors + +| Error | Possible solution | +|:---------------------------------------------------------------------------|:---------------------------------------------------------------------------------------------------------| +| ValidatorConsole error: Validator console is not settings | Check [validator article](/v3/guidelines/nodes/nodes-troubleshooting#validator-console-is-not-settings) | +| Cannot enable validator mode while liteserver mode is enabled | Use `disable_mode liteserver` | +| Validator wallet not found | Check [validator article](/v3/guidelines/nodes/running-nodes/validator-node#view-the-list-of-wallets) | +| Validator is not synchronized | Wait more for sync or check [sync troubleshouting](/v3/guidelines/nodes/nodes-troubleshooting#about-no-progress-in-node-synchronization-within-3-hours) | +| Stake less than the minimum stake. Minimum stake: `minStake` | Use [`set stake {amount}`](/v3/guidelines/nodes/running-nodes/validator-node#your-validator-is-now-ready) and [check stake parameters](/v3/documentation/network/configs/blockchain-configs#param-17) | +| Don't have enough coins. stake: `stake`, account balance: `balance` | Top up your `balance` up to `stake` | + +## Nominator Pool errors + +| Error | Possible solution | +|:---------------------------------------------------------------------------|:----------------------------------------------------------------------| +| CreatePool error: Pool with the same parameters already exists | Check `pools_list` for existing pools | +| create_single_pool error: Pool with the same parameters already exists | Check `pools_list` for existing pools | + +## See Also + +* [Nodes Troubleshooting](/v3/guidelines/nodes/nodes-troubleshooting) \ No newline at end of file diff --git a/docs/v3/guidelines/nodes/nodes-troubleshooting.md b/docs/v3/guidelines/nodes/nodes-troubleshooting.md index 3a8514a1ef..8ad1d69671 100644 --- a/docs/v3/guidelines/nodes/nodes-troubleshooting.md +++ b/docs/v3/guidelines/nodes/nodes-troubleshooting.md @@ -220,3 +220,4 @@ There are two known cases when this error appears: ## See Also * [MyTonCtrl FAQ](/v3/guidelines/nodes/faq) +* [MyTonCtrl errors](/v3/documentation/infra/nodes/mytonctrl/mytonctrl-errors) diff --git a/sidebars/documentation.js b/sidebars/documentation.js index d344342e7f..f5575373e5 100644 --- a/sidebars/documentation.js +++ b/sidebars/documentation.js @@ -171,23 +171,6 @@ module.exports = [ 'type': 'html', 'value': ' Infrastructure Documentation ', }, - 'v3/documentation/infra/minter-flow', - { - type: 'category', - label: 'Cross-chain Bridges', - items: [ - { - type: 'doc', - label: 'Overview', - id: 'v3/documentation/infra/crosschain/overview', - }, - { - type: 'doc', - label: 'Bridges Addresses', - id: 'v3/documentation/infra/crosschain/bridge-addresses', - }, - ], - }, { type: 'category', label: 'Blockchain Nodes', @@ -200,6 +183,7 @@ module.exports = [ 'v3/documentation/infra/nodes/mytonctrl/mytonctrl-overview', 'v3/documentation/infra/nodes/mytonctrl/mytonctrl-alerting', 'v3/documentation/infra/nodes/mytonctrl/mytonctrl-status', + 'v3/documentation/infra/nodes/mytonctrl/mytonctrl-errors', ], }, 'v3/documentation/infra/nodes/node-commands', @@ -217,6 +201,23 @@ module.exports = [ }, ], }, + 'v3/documentation/infra/minter-flow', + { + type: 'category', + label: 'Cross-chain Bridges', + items: [ + { + type: 'doc', + label: 'Overview', + id: 'v3/documentation/infra/crosschain/overview', + }, + { + type: 'doc', + label: 'Bridges Addresses', + id: 'v3/documentation/infra/crosschain/bridge-addresses', + }, + ], + }, { 'type': 'html', 'value': '
', From f7d4c0e5ee4fcdb7813de3c3dc972dcb2ff30c2b Mon Sep 17 00:00:00 2001 From: Gleb Karavatski Date: Thu, 21 Nov 2024 12:12:53 +0300 Subject: [PATCH 4/4] update slow sync potential reasons --- docs/v3/guidelines/nodes/nodes-troubleshooting.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/v3/guidelines/nodes/nodes-troubleshooting.md b/docs/v3/guidelines/nodes/nodes-troubleshooting.md index 8ad1d69671..672a738433 100644 --- a/docs/v3/guidelines/nodes/nodes-troubleshooting.md +++ b/docs/v3/guidelines/nodes/nodes-troubleshooting.md @@ -36,9 +36,7 @@ Go through the checklist [from this section](/v3/guidelines/nodes/nodes-troubles ## Slow sync potential reasons -1. The disk is relatively weak. It's advisable to check the IOPS of the disk (though sometimes hosting providers exaggerate these numbers). -2. Updates coincided with network congestion. However, the slow synchronization is due to the load, not the updates. The full node cannot catch up with the network because there were about 100 million transactions. -3. Since the default value of keep history for a Full Node state has been reduced to one day, there are fewer Full Nodes in the network that can provide older states, may cause making it harder to sync with such a delay. +The disk is relatively weak. It's advisable to check the IOPS of the disk (though sometimes hosting providers exaggerate these numbers). ## Cannot apply external message to current state : External message was not accepted