MyTonCtrl status error

[qqBelkaRezka]

MyTonCtrl> status [debug] 17.04.2024, 11:22:33.383 (UTC) start GetRootWorkchainEnabledTime function [debug] 17.04.2024, 11:22:33.383 (UTC) start GetValidatorEfficiency function [warning] 17.04.2024, 11:22:33.383 (UTC) GetValidatorEfficiency warning: efficiency not found. Error: Command '['/usr/bin/ton/lite-client/lite-client', '--global-config', '/usr/bin/ton/global.config.json', '--verbosity', '0', '--cmd', 'allshards']' timed out after 3 seconds

[pushiqiang]

Similar problem! I don't know any sync progress

[debug]   30.04.2024, 10:24:49.790 (UTC)  <Telemetry>   start GetFullElectorAddr function
[debug]   30.04.2024, 10:24:51.462 (UTC)  <custom_overlays>start GetConfig function (12)
[error]   30.04.2024, 10:24:52.795 (UTC)  <Telemetry>   GetElectionEntries error: Command '['/usr/bin/ton/lite-client/lite-client', '--global-config', '/usr/bin/ton/global.config.json', '--verbosity', '0', '--cmd', 'getconfig 1', '-i', '17']' timed out after 3 seconds
[debug]   30.04.2024, 10:24:52.795 (UTC)  <Telemetry>   start GetFullElectorAddr function
[debug]   30.04.2024, 10:24:54.058 (UTC)  <custom_overlays>start GetConfig function (15)
[error]   30.04.2024, 10:24:55.799 (UTC)  <Telemetry>   GetComplaints error: Command '['/usr/bin/ton/lite-client/lite-client', '--global-config', '/usr/bin/ton/global.config.json', '--verbosity', '0', '--cmd', 'getconfig 1', '-i', '1']' timed out after 3 seconds
[debug]   30.04.2024, 10:24:56.739 (UTC)  <custom_overlays>start GetConfig34 function
[error]   30.04.2024, 10:24:59.744 (UTC)  <custom_overlays>custom_overlays error: Command '['/usr/bin/ton/lite-client/lite-client', '--global-config', '/usr/bin/ton/global.config.json', '--verbosity', '0', '--cmd', 'getconfig 34', '-i', '1']' timed out after 3 seconds

[pushiqiang]

I want to know how to check the sync progress of data

[thedemons]

Do this to get a usable global.config.json:

wget https://api.tontech.io/ton/wallet-mainnet.autoconf.json -O /usr/bin/ton/global.config.json

It removes slow liteservers from the configuration file.

From Interaction with TON: Public Liteservers (endpoints)

Then restart the validator:

sudo systemctl restart validator

You can also increase the time out in ~/.local/share/mytonctrl/mytonctrl.db:

{
    "config": {
    },
    "liteclient_timeout": 15
}

[tiagocmachado]

Still seeing this on testnet with the latest global-config: https://github.com/ton-blockchain/ton-blockchain.github.io/blob/main/testnet-global.config.json

[Szymongib]

☝️ We are facing the same error on testnet.

[dnjef9duo]

☝️ same here

Error: LiteClient error: [ 0][t 1][2024-05-14 04:56:49.378979495][block.cpp:1647][!testnode]    Check `total_wt >= W[a]` failed
[pid 1322950] [time 1715662609] Signal: 6
------- Stack Backtrace -------
/usr/bin/ton/lite-client/lite-client[0x498949]
/usr/bin/ton/lite-client/lite-client[0x4971f6]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x7fc50c494420]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7fc50bf7b00b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7fc50bf5a859]

[awesome-doge]

My suggestion here is to delete the original database, because this database may already store part of the mainnet blockchain information.

# Stop services (first we shut down all services
sudo systemctl stop validator
sudo systemctl stop mytoncore

# Delete the original database (delete the data that may be stored in the mainnet) (don’t be too nervous, because it will be automatically regenerated here.
sudo rm -r /var/ton-work/db/adnl
sudo rm -r /var/ton-work/db/archive
sudo rm -r /var/ton-work/db/catchains
sudo rm -r /var/ton-work/db/celldb
sudo rm -r /var/ton-work/db/error
sudo rm -r /var/ton-work/db/files
sudo rm -r /var/ton-work/db/overlays
sudo rm -r /var/ton-work/db/state

# Download testnet configuration file and rename it
sudo wget -O /var/ton-work/global.config.json https://ton.org/testnet-global.config.json

#Restart services
sudo systemctl restart validator
sudo systemctl restart mytoncore

Then we go to sudo tail -f /var/ton-work/log* to observe all changes

Please also ensure a few things

1. Is your host a fixed IP?
2. Is the IP address written in your config.json file correct?
3. Does your host have enough memory?
4. Does your host have enough hard disk?
5. Does your firewall have the validator port opened?