testnet node err after sync new snapshot ( AMD CPU only )

[msobh13]

neard (release 2.2.1-rc.1) (build 2.2.1-rc.1) (rustc 1.79.0) (protocol 71) (db 40) features: [default, json_rpc, rosetta_rpc]

lscpu | grep -P '(?=.*avx )(?=.*sse4.2 )(?=.*cx16 )(?=.*popcnt )(?=.*sha_ni )' > /dev/null \ && echo "Supported" \ || echo "Not supported"
Supported

CPU is AMD Ryzen 9 5950X

tried snapshots
PRE 2024-09-14T23:00:31Z/ PRE 2024-09-15T23:00:32Z/ PRE 2024-09-16T23:00:50Z/ PRE 2024-09-17T23:00:31Z/ PRE 2024-09-18T23:00:32Z/ PRE 2024-09-19T23:00:31Z/ PRE 2024-09-20T23:00:49Z/ PRE 2024-09-21T23:00:33Z/ PRE 2024-09-22T23:00:31Z/

always after fully sync header got warn likes

2024-09-23T15:29:26.369135Z WARN garbage collection: Error in gc: GC Error: block on canonical chain shouldn't have refcount 0 2024-09-23T15:29:27.370411Z WARN garbage collection: Error in gc: GC Error: block on canonical chain shouldn't have refcount 0 2024-09-23T15:29:28.371955Z WARN garbage collection: Error in gc: GC Error: block on canonical chain shouldn't have refcount 0

waited hours and no sync . after restart service got this err

2024-09-23T15:32:36.510998Z INFO config: Validating Config, extracted from config.json... 2024-09-23T15:32:36.511026Z INFO neard: No validator key /nvme2/neartestnet/validator_key.json. 2024-09-23T15:32:36.511475Z INFO near_o11y::reload: Updated the logging layer according to log_config.json2024-09-23T15:32:36.513077Z INFO db_opener: Opening NodeStorage path="/nvme2/neartestnet/data" cold_path="none" 2024-09-23T15:32:36.514016Z INFO db: Opened a new RocksDB instance. num_instances=1 2024-09-23T15:32:38.816325Z INFO db: Closed a RocksDB instance. num_instances=0 2024-09-23T15:32:38.816361Z INFO db_opener: The database exists. path=/nvme2/neartestnet/data 2024-09-23T15:32:38.816653Z INFO db: Opened a new RocksDB instance. num_instances=1 2024-09-23T15:32:49.699466Z INFO db: Closed a RocksDB instance. num_instances=0 2024-09-23T15:32:49.699501Z INFO db: Opened a new RocksDB instance. num_instances=1 2024-09-23T15:32:49.726552Z INFO db: Closed a RocksDB instance. num_instances=0 2024-09-23T15:32:49.726576Z INFO db: Opened a new RocksDB instance. num_instances=1 thread 'main' panicked at chain/client/src/client_actor.rs:168:6: calledResult::unwrap()on anErrvalue: Chain(DBNotFoundErr("epoch block: FTDUrmskPugXsfQZ9g75nkK5FTWCE232ehwKTcvrUUUN")) stack backtrace: 0: rust_begin_unwind 1: core::panicking::panic_fmt 2: core::result::unwrap_failed 3: nearcore::start_with_config_and_synchronization 4: neard::cli::RunCmd::run::{{closure}} 5: tokio::task::local::LocalSet::run_until::{{closure}} 6: neard::cli::NeardCmd::parse_and_run 7: neard::main note: Some details are omitted, run withRUST_BACKTRACE=fullfor a verbose backtrace.

and somtimes this err

22T14:21:25.131328Z ERROR client: Received an invalid block during state sync err=DBNotFoundErr("epoch block: BrGEHWcpewP3KsFs8XPwHMP6kXjzp4oH4xGnkeczs5oc") block_hash=8UjqHTSgNnxd2Nz4qPsPukLnDcVwxbGswmcjV6X6sNan2024-09-22T14:21:25.131358Z ERROR client: Received an invalid block during state sync err=DBNotFoundErr("epoch block: BrGEHWcpewP3KsFs8XPwHMP6kXjzp4oH4xGnkeczs5oc") block_hash=8UjqHTSgNnxd2Nz4qPsPukLnDcVwxbGswmcjV6X6sNan 2024-09-22T14:21:25.133679Z ERROR client: Received an invalid block during state sync err=DBNotFoundErr("epoch block: BrGEHWcpewP3KsFs8XPwHMP6kXjzp4oH4xGnkeczs5oc") block_hash=8UjqHTSgNnxd2Nz4qPsPukLnDcVwxbGswmcjV6X6sNan2024-09-22T14:21:25.134613Z

tried also to

`Clear the compiled contract cache: rm -rf ~/.near/data/contracts
Undo the last block: ./neard undo-block

`

Tried different hosting provider and different HW . all AMD CPU . No luck

My Intel 13 core i5 works fine and sync fine

[msobh13]

config.json
attached config file but just to mention , this happen with my old config and also i downloaded and used new config same issue

[msobh13]

this had been fixed using snapshot 2024-09-25T23:00:32Z