Skip to main content

Troubleshooting

This section contains answers to the most frequently asked questions about running nodes.

Failed to get account state​

Failed to get account state

This error means that there are issues during search for this account in shard state. Most probably it means that liteserver node is syncing too slow, in particular the Masterchain synchronisation overtook shardchains (Basechain) synchronisation. In this case node knows the recent Masterchain block but can not check account state in recent shardchain block and returns Failed to get account state.

Failed to unpack account state​

Failed to unpack account state

This error means that requested account doesn't exist in current state. That means that this account is simultaneously is not deployed AND has zero balance

About no progress in node synchronization within 3 hours​

Try to perform following checks:

  1. Is process running without crashes? (Check systemd process status)
  2. Is there a firewall between node and internet, if so, will it pass incoming UDP traffic to port specified in field addrs[0].port of /var/ton-work/db/config.json file?
  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 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.

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​

Cannot apply external message to current state : External message was not accepted

This error means that contract didn't accepted external message. You need to find exitcode in trace. -13 means that account doesn't have enough TON to accept message (or it requires more than gas_credit). In case of wallet contracts exitcode=33 means wrong seqno (probably seqno data you use is outdatd), exitcode=34 means wrong subwallet_id (for old wallets v1/v2 it means wrong signature), exitcode=35 means that either message is expired or signature is wrong.

What does Error 651 mean?​

[Error : 651 : no nodes] indicates that your node cannot locate another node within the TON Blockchain.

Sometimes, this process can take up to 24 hours. However, if you've been receiving this error for several days, that means that your node cannot synchronize via a current network connection.

Solution

You need to check the firewall settings, including any NAT settings if they exist.

It should allow incoming connections on one specific port and outgoing connections from any port.

Validator console is not settings​

If you encounter the Validator console is not settings error, it indicates that you are running MyTonCtrl from a user other than the one you used for the installation.

Solution

Run MyTonCtrl from the user you've installed it (non-root sudo user).

mytonctrl

###Running MyTonCtrl as Different User

Running MyTonCtrl as a different user may trigger the following error:

Error: expected str, bytes or os.PathLike object, not NoneType

To resolve this, you should run MyTonCtrl as the user who installed it.

What does "block is not applied" mean?​

Q: Sometimes we get block is not applied or block is not ready for various requests - is this normal?

A: This is normal, typically this means you tried to retrieve block, which does not reach the node you asked.

Q: If comparative frequency appears, does it mean there is a problem somewhere?

A: No. You need to check "Local validator out of sync" value in mytonctrl. If it's less than 20 seconds, then everything is fine.

But you need to keep in mind that the node is constantly synchronizing. Sometimes, you may try to receive a block that has not reached the node you requested.

You need to repeat the request with a slight delay.

Out of Sync Issue with -d Flag​

If you encounter an issue where the out of sync equals the timestamp after downloading MyTonCtrl with the -d flag, it's possible that the dump wasn't installed correctly (or it's already outdated).

Solution

The recommended solution is to reinstall MyTonCtrl again with the new dump.

If syncing takes an unusually long time, there may have been issues with the dump. Please contact us for assistance.

Please, run mytonctrl from the user you've installed it.

Error command... timed out after 3 seconds​

This error means that the local node is not yet synchronized(out of sync lesser then 20 sec) and public nodes are being used. Public nodes do not always respond and end up with a timeout error.

Solution

The solution to the problem is to wait for the local node to synchronize or execute the same command several times before execution.

Status command displays without local node section​

If there is no local node section in the node status, typically this means, something went wrong during installation and the step of creating/assigning a validator wallet was skipped. Also check that the validator wallet is specified.

Check directly the following:

mytonctrl> get validatorWalletName

If validatorWalletName is null then execute the following:

mytonctrl> set validatorWalletName validator_wallet_001

Transfer a Validator on the new Server​

info

Transfer all keys and configs from the old to the working node and start it. In case something goes wrong on the new one, there is still the source where everything is set up.

The best way (while the penalty for temporary non-validation is small, it can be done without interruption):

  1. Perform a clean installation on the new server using mytonctrl, and wait until everything is synchronized.

  2. Stop the mytoncore and validator services on both machines, make backups on the source and on the new one:

  • 2.1 /usr/local/bin/mytoncore/...
  • 2.2 /home/${user}/.local/share/mytoncore/...
  • 2.3 /var/ton-work/db/config.json
  • 2.4 /var/ton-work/db/config.json.backup
  • 2.5 /var/ton-work/db/keyring
  • 2.6 /var/ton-work/keys
  1. Transfer from the source to the new one (replace the contents):
  • 3.1 /usr/local/bin/mytoncore/...
  • 3.2 /home/${user}/.local/share/mytoncore/...
  • 3.3 /var/ton-work/db/config.json
  • 3.4 /var/ton-work/db/keyring
  • 3.5 /var/ton-work/keys

  1. In /var/ton-work/db/config.json edit addrs[0].ip to the current one, which was after installation (can be seen in the backup /ton-work/db/config.json.backup)

  2. Check the permissions on all replaced files

  3. On the new one, start the mytoncore and validator services, check that the node synchronizes and then validates

  4. On the new one, make a backup:

cp var/ton-work/db/config.json var/ton-work/db/config.json.backup

Mytonctrl was installed by another user. Probably you need to launch mtc with ... user​

Run MyTonCtrl with user that used to install it.

For example, the most common case is when one tries to run MyTonCtrl as root user, even though it was installed under a different user. In this case, you need to log in to the user who installed MyTonCtrl and run MyTonCtrl from that user.

Mytonctrl was installed by another user. Probably you need to launch mtc with validator user​

Run command sudo chown <user_name>:<user_name> /var/ton-work/keys/* where <user_name> is user which installed mytonctrl.

Mytonctrl was installed by another user. Probably you need to launch mtc with ubuntu user​

Additionally mytonctrl may not work properly with this error. For example, the status command may return empty result.

Check mytonctrl owner:

ls -lh /var/ton-work/keys/

If the owner is the root user, uninstall mytonctrl and install it again using non-root user.

Else, log out from the current user (if ssh connection is used, break it) and log in as the correct user.

The message must disappear.

MyTonCtrl's console launch breaks after message "Found new version of mytonctrl! Migrating!"​

There are two known cases when this error appears:

Error After Updating MytonCtrl​

  • If MyTonCtrl was installed by root user: delete file /usr/local/bin/mytonctrl/VERSION.
  • If MyTonCtrl was installed by non root user: delete file ~/.local/share/mytonctrl/VERSION.

Error During MytonCtrl Installation​

MytonCtrl may open, but the node will not work properly. Please remove MytonCtrl from your computer and reinstall it, ensuring to address any errors that were previously encountered.

See Also​