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

Bug: #12687

Open
maximdogonov opened this issue Jan 6, 2025 · 0 comments
Open

Bug: #12687

maximdogonov opened this issue Jan 6, 2025 · 0 comments
Assignees
Labels
community Issues created by community investigation required

Comments

@maximdogonov
Copy link

Contact Details

[email protected]

Which network are you using?

mainnet

What happened?

I try run near archive node and I take last snapshot use follow command:

s5cmd --no-sign-request=true sync --delete s3://near-protocol-public/backups/mainnet/archive/2024-12-28T00:17:26Z/cold-data/* .

s5cmd --no-sign-request=true sync --delete s3://near-protocol-public/backups/mainnet/archive/2024-12-28T00:17:26Z/hot-data/* .

sync done successful, but when I try run node got error MANIFEST-111337287 No such file or directory

now I have MANIFEST on hot-data but with different number as MANIFEST-113063816:

-rw-r--r-- 1 root root  78354550 Jan  6 06:57 LOG
-rw-r--r-- 1 root root  12896048 Jan  6 06:57 MANIFEST-113063816
-rw-r--r-- 1 root root    284928 Jan  6 06:57 OPTIONS-113063814
-rw-r--r-- 1 root root    284928 Jan  6 06:57 OPTIONS-113063818
drwxr-xr-x 1 root root        88 Jan  6 07:01 state_snapshot
drwxr-xr-x 1 root root       190 Jan  6 07:02 test

How I can fixed that?

Thank you!

Relevant log output

near-mainnet-node  | 2025-01-06T07:33:57.648157Z  INFO config: Validating Config, extracted from config.json...
near-mainnet-node  | 2025-01-06T07:33:57.648171Z  INFO neard: No validator key /root/.near/validator_key.json.
near-mainnet-node  | 2025-01-06T07:33:57.648194Z  INFO near_o11y::reload: Updated the logging layer according to `log_config.json`
near-mainnet-node  | 2025-01-06T07:33:57.648211Z  INFO db_opener: Opening NodeStorage path="/hot-data" cold_path="/cold-data"
near-mainnet-node  | 2025-01-06T07:33:57.648232Z  INFO db: Opened a new RocksDB instance. num_instances=1
near-mainnet-node  | 2025-01-06T07:33:57.664909Z  INFO db: Closed a RocksDB instance. num_instances=0
near-mainnet-node  | thread 'main' panicked at neard/src/cli.rs:571:14:
near-mainnet-node  | start_with_config: unable to open database at /hot-data
near-mainnet-node  | 
near-mainnet-node  | Caused by:
near-mainnet-node  |     IO error: No such file or directory: While opening a file for sequentially reading: /hot-data/MANIFEST-111337287: No such file or directory
near-mainnet-node  | stack backtrace:
near-mainnet-node  |    0: rust_begin_unwind
near-mainnet-node  |    1: core::panicking::panic_fmt
near-mainnet-node  |    2: core::result::unwrap_failed
near-mainnet-node  |    3: neard::cli::RunCmd::run::{{closure}}
near-mainnet-node  |    4: tokio::task::local::LocalSet::run_until::{{closure}}
near-mainnet-node  |    5: neard::cli::NeardCmd::parse_and_run
near-mainnet-node  |    6: neard::main
near-mainnet-node  | note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
near-mainnet-node  | 2025-01-06T07:33:58.861704Z  INFO neard: version="2.4.0" build="2.4.0" latest_protocol=73
near-mainnet-node  | 2025-01-06T07:33:58.861917Z  INFO config: Validating Config, extracted from config.json...
near-mainnet-node  | 2025-01-06T07:33:58.863567Z  WARN genesis: Skipped genesis validation
near-mainnet-node  | 2025-01-06T07:33:58.863583Z  INFO config: Validating Genesis config and records. This could take a few minutes...
near-mainnet-node  | 2025-01-06T07:33:58.863742Z  INFO config: All validations have passed!
near-mainnet-node  | 2025-01-06T07:33:58.864616Z  INFO neard: Changing the config "/root/.near/log_config.json". config=LogConfig { rust_log: None, verbose_module: None, opentelemetry: None }
near-mainnet-node  | 2025-01-06T07:33:58.864751Z  INFO config: Validating Config, extracted from config.json...
near-mainnet-node  | 2025-01-06T07:33:58.864764Z  INFO neard: No validator key /root/.near/validator_key.json.
near-mainnet-node  | 2025-01-06T07:33:58.864790Z  INFO near_o11y::reload: Updated the logging layer according to `log_config.json`
near-mainnet-node  | 2025-01-06T07:33:58.864805Z  INFO db_opener: Opening NodeStorage path="/hot-data" cold_path="/cold-data"
near-mainnet-node  | 2025-01-06T07:33:58.864823Z  INFO db: Opened a new RocksDB instance. num_instances=1
near-mainnet-node  | 2025-01-06T07:33:58.881920Z  INFO db: Closed a RocksDB instance. num_instances=0
near-mainnet-node  | thread 'main' panicked at neard/src/cli.rs:571:14:
near-mainnet-node  | start_with_config: unable to open database at /hot-data
near-mainnet-node  | 
near-mainnet-node  | Caused by:
near-mainnet-node  |     IO error: No such file or directory: While opening a file for sequentially reading: /hot-data/MANIFEST-111337287: No such file or directory
near-mainnet-node  | stack backtrace:
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
Projects
None yet
Development

No branches or pull requests

2 participants