Base node unsynced and couldn't pick up

[inemyrovsk]

Base node unsynced and couldn't pick up, I dont see any error logs, also I have tried to update to op-node/v1.11.2 with Corresponding op-geth release: v1.101500.1 but it fails the same way Latest synced block behind by: 29008862 minutes

I have been running base node for 2 weeks and almost everyday I had to restart it because it stuck sometimes but now it completely stuck. SPECS: model name : 13th Gen Intel(R) Core(TM) i5-13500

free -h total used free shared buff/cache available Mem: 62Gi 9.1Gi 534Mi 1.5Mi 53Gi 53Gi Swap: 31Gi 0B 31Gi

/dev/nvme2n1p5 6.6T 3.0T 3.6T 46% /data samsung nvme ssd

the only thing I have changed in vars: HOST_DATA_DIR=/data/snapshots/mainnet/download/geth +OP_NODE_L1_ETH_RPC=https://****/7f52f3121096ec9e14b804977567e6caf4914691

[required] replace with your preferred L1 CL beacon endpoint:

-OP_NODE_L1_BEACON=https://your.mainnet.beacon.node/endpoint-here +OP_NODE_L1_BEACON=https://ethereum-beacon-api.publicnode.com

LOGS: execution-1 | WARN [02-26|01:01:02.603] Served optimism_syncStatus conn=188.245.147.19:49148 reqid=0 duration="5.566µs" err="the method optimism_syncStatus does not exist/is not available" execution-1 | WARN [02-26|01:07:35.460] Served admin_peers reqid=1 duration="35.105µs" err="the method admin_peers does not exist/is not available"

[nikolayovn]

I have the same issue, and I don't think your node is stuck. It's just syncing very slowly, just like mine.

Instead of looking at the minutes, try checking the sync progress in seconds with this command:

command -v jq  &> /dev/null || { echo "jq is not installed" 1>&2 ; }
echo Latest synced block behind by: \
$((($( date +%s )-\
$( curl -s -d '{"id":0,"jsonrpc":"2.0","method":"optimism_syncStatus"}' -H "Content-Type: application/json" http://localhost:7545 |
   jq -r .result.unsafe_l2.timestamp)))) seconds

Also, you should update your data directory path:

HOST_DATA_DIR=/data/snapshots/mainnet/download/geth

to:

HOST_DATA_DIR=/data/snapshots/mainnet/download

The reason for this change is that if you run:

 ls /data/snapshots/mainnet/download/geth

You'll see that there's another geth directory inside:

 /data/snapshots/mainnet/download/geth/geth

This happens because the node expects a geth directory inside HOST_DATA_DIR, so setting it to /data/snapshots/mainnet/download should fix the issue.

"29008862 minutes" fron your output shows that you are not syncing from snapshot beacause of that HOST_DATA_DIR

By the way, I'm also looking for ways to speed up the sync process.