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.

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

Node Issue: the node won't sync after downloading official snapshot #12774

Open
AdamRylski opened this issue Jan 23, 2025 · 1 comment
Open
Assignees
Labels
community Issues created by community investigation required Node Node team

Comments

@AdamRylski
Copy link

Contact Details

No response

Node type

RPC

Which network are you running?

mainnet

What happened?

the node won't sync after downloading official snapshot

Version

neard (release trunk) (build unknown) (rustc 1.84.0) (protocol 74) (db 43)

Relevant log output

`2025-01-23T08:52:58.408326Z  INFO stats: #       0 Waiting for peers 0 peers ⬇ 0 B/s ⬆ 0 B/s 0.00 bps 0 gas/s CPU: 2%, Mem: 70.1 MB
2025-01-23T08:53:08.409600Z  INFO stats: #       0 Waiting for peers 0 peers ⬇ 0 B/s ⬆ 0 B/s 0.00 bps 0 gas/s CPU: 2%, Mem: 70.1 MB
2025-01-23T08:53:18.410983Z  INFO stats: #       0 Waiting for peers 0 peers ⬇ 0 B/s ⬆ 0 B/s 0.00 bps 0 gas/s CPU: 1%, Mem: 70.6 MB
2025-01-23T08:53:28.412053Z  INFO stats: #       0 Waiting for peers 0 peers ⬇ 0 B/s ⬆ 0 B/s 0.00 bps 0 gas/s CPU: 1%, Mem: 70.6 MB
2025-01-23T08:53:38.412968Z  INFO stats: #       0 Waiting for peers 0 peers ⬇ 0 B/s ⬆ 0 B/s 0.00 bps 0 gas/s CPU: 1%, Mem: 70.6 MB

Node head info

2025-01-23T08:51:16.879698Z  INFO neard: version="trunk" build="unknown" latest_protocol=74
2025-01-23T08:51:16.880236Z  INFO config: Validating Config, extracted from config.json...
2025-01-23T08:51:16.880522Z  WARN genesis: Skipped genesis validation
2025-01-23T08:51:16.880537Z  WARN genesis: Skipped genesis validation
2025-01-23T08:51:16.880542Z  INFO config: All validations have passed!
2025-01-23T08:51:16.880725Z  INFO db_opener: Opening NodeStorage path="/srv/near/data" cold_path="none"
2025-01-23T08:51:16.880763Z  INFO db: Opened a new RocksDB instance. num_instances=1
2025-01-23T08:51:16.885693Z  INFO db: Closed a RocksDB instance. num_instances=0
2025-01-23T08:51:16.885732Z  INFO db_opener: The database exists. path=/srv/near/data
2025-01-23T08:51:16.885773Z  INFO db: Opened a new RocksDB instance. num_instances=1
2025-01-23T08:51:16.920060Z  INFO db: Closed a RocksDB instance. num_instances=0
2025-01-23T08:51:16.920129Z  INFO db: Opened a new RocksDB instance. num_instances=1
2025-01-23T08:51:16.922706Z  INFO db: Closed a RocksDB instance. num_instances=0
2025-01-23T08:51:16.922746Z  INFO db: Opened a new RocksDB instance. num_instances=1
"FINAL_HEAD": Tip { height: 0, last_block_hash: 2SHhZjQ9GRUfs9SDKb9SxW4FMT9Fo5a3sbRWyPDr1xbc, prev_block_hash: 11111111111111111111111111111111, epoch_id: EpochId(11111111111111111111111111111111), next_epoch_id: EpochId(11111111111111111111111111111111) }
"GENESIS_CONGESTION_INFO_KEY": [1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
"GENESIS_JSON_HASH": 6ED81ZwqUuXDUt3V9vB6cJ27pi9KpShSRKuP79cFZFpt
"GENESIS_STATE_ROOTS": [F3xFjNwEjhAQWGwTpCNGvhscRYifQpFoEBai85GhWi7J]
"HEAD": Tip { height: 0, last_block_hash: 2SHhZjQ9GRUfs9SDKb9SxW4FMT9Fo5a3sbRWyPDr1xbc, prev_block_hash: 11111111111111111111111111111111, epoch_id: EpochId(11111111111111111111111111111111), next_epoch_id: EpochId(11111111111111111111111111111111) }
"HEADER_HEAD": Tip { height: 0, last_block_hash: 2SHhZjQ9GRUfs9SDKb9SxW4FMT9Fo5a3sbRWyPDr1xbc, prev_block_hash: 11111111111111111111111111111111, epoch_id: EpochId(11111111111111111111111111111111), next_epoch_id: EpochId(11111111111111111111111111111111) }
"LATEST_KNOWN": LatestKnown { height: 0, seen: 1736951400116752123 }
2025-01-23T08:51:16.954047Z  INFO db: Closed a RocksDB instance. num_instances=0

Node upgrade history

setup from scratch

DB reset history

DB from y-day snpashot
@AdamRylski
Copy link
Author

Today we have tried to run the node using docker https://near-nodes.io/validator/running-a-node#running-a-node-using-docker

docker run -v /data/near:/root/.near -d -p 3030:3030 --name nearup nearup/nearprotocol run mainnet

but

root@pve-near-02:/data/near# docker logs -f 71155dc3de04
run mainnet
2025-01-28 12:48:22.636 INFO nearup - run: Home directory is /root/.near/mainnet...
2025-01-28 12:48:22.637 INFO nodelib - setup_and_run: Using officially compiled binary
/root/.local/lib/python3.6/site-packages/boto3/compat.py:88: PythonDeprecationWarning: Boto3 will no longer support Python 3.6 starting May 30, 2022. To continue receiving service updates, bug fixes, and security updates please upgrade to Python 3.7 or later. More information can be found here: https://aws.amazon.com/blogs/developer/python-support-policy-updates-for-aws-sdks-and-tools/
  warnings.warn(warning, PythonDeprecationWarning)
2025-01-28 12:48:24.466 INFO util - download_binaries: Downloading latest deployed version for mainnet
2025-01-28 12:48:24.467 INFO util - download_binaries: Downloading neard to /root/.nearup/near/mainnet/neard from nearcore/Linux/2.4.0/dc7b83c03529c6e9b432c649414aa9c79580df30/neard...
2025-01-28 12:48:33.695 INFO util - download_binaries: Downloaded neard to /root/.nearup/near/mainnet/neard...
2025-01-28 12:48:33.696 INFO util - download_binaries: Making the neard executable...
2025-01-28 12:48:33.696 INFO nodelib - check_and_setup: Setting up network configuration.
2025-01-28 12:48:33.696 INFO nodelib - init_near: Initializing the node configuration using near binary...
/root/.nearup/near/mainnet/neard: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /root/.nearup/near/mainnet/neard)
/root/.nearup/near/mainnet/neard: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by /root/.nearup/near/mainnet/neard)
/root/.nearup/near/mainnet/neard: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.30' not found (required by /root/.nearup/near/mainnet/neard)
/root/.nearup/near/mainnet/neard: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /root/.nearup/near/mainnet/neard)
/root/.nearup/near/mainnet/neard: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by /root/.nearup/near/mainnet/neard)
Traceback (most recent call last):
  File "/root/.local/bin/nearup", line 178, in <module>
    cli()
  File "/root/.local/lib/python3.6/site-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/root/.local/lib/python3.6/site-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/root/.local/lib/python3.6/site-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/root/.local/lib/python3.6/site-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/root/.local/lib/python3.6/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/root/.local/bin/nearup", line 122, in run
    watcher=not no_watcher)
  File "/root/.local/lib/python3.6/site-packages/nearuplib/nodelib.py", line 315, in setup_and_run
    check_and_setup(binary_path, home_dir, chain_id, account_id, interactive)
  File "/root/.local/lib/python3.6/site-packages/nearuplib/nodelib.py", line 158, in check_and_setup
    init_near(home_dir, binary_path, chain_id, account_id, interactive)
  File "/root/.local/lib/python3.6/site-packages/nearuplib/nodelib.py", line 92, in init_near
    subprocess.check_call(cmd)
  File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/root/.nearup/near/mainnet/neard', '--home=/root/.near/mainnet', 'init', '--chain-id=mainnet']' returned non-zero exit status 1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Issues created by community investigation required Node Node team
Projects
None yet
Development

No branches or pull requests

2 participants