Add MyTonCtrl errors article (#830)

* node slow sync potential reasons * fix: fix build * add MyTonCtrl errors article * update slow sync potential reasons --------- Co-authored-by: Gleb Karavatski <[email protected]> Co-authored-by: Aliaksandr Bahdanau <[email protected]>
ton-community · Nov 26, 2024 · 0b1c5c9 · 0b1c5c9
1 parent a705861
commit 0b1c5c9
Show file tree

Hide file tree

Showing 3 changed files with 64 additions and 20 deletions.
diff --git a/docs/v3/documentation/infra/nodes/mytonctrl/mytonctrl-errors.md 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)
diff --git 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
 
@@ -220,3 +218,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
@@ -189,23 +189,6 @@ module.exports = [
     'type': 'html',
     'value': '<span class=\'menu__link\'><b><small> Infrastructure Documentation </small></b></span>',
   },
-  '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',
@@ -218,6 +201,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',
@@ -235,6 +219,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': '<hr/>',