Problem launching op-node

[swigsstaking]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I can't launch my node because of this error

Protocol Description

[op-node/v1.3.2]
op-geth [v1.101304.2]

Node Logs

No response

Additional Information

No response

Feedback

No response

[opfocus]

Please provide your op-geth logs. This typically happens when op-geth is not ready yet, and op-node is started too early

[swigsstaking]

I have errors at the end of my logs but maybe that's because it's been running since yesterday

[opfocus]

I think the issue is with op-geth. For now, we can temporarily ignore the issues with op-node. I noticed multiple occurrences of 'unclean shutdown,' which is a very serious problem. Please try deleting the data folder, recreating the data folder, and decompressing the snapshot. I believe this will allow op-geth to run normally. Additionally, we need to investigate the cause of the unclean shutdown issue.

[swigsstaking]

Ok I understood I had a problem with my jwt. I have another question, if op-node stops it is no longer possible to restart it on my side, is this normal?

[opfocus]

I don't understand the reason for the unclean shutdown and hope others can join the discussion.
The error 'WARN [12-20|09:45:58.063] failed to dial address, but may connect later addr=ws://localhost:8551' is very familiar to me and is encountered frequently. It's worth noting that this error is not related to JWT; JWT issues typically result in another 401 error. As for the issue of op-geth not restarting after stopping, honestly, I haven't encountered that before. In my experience, they have always been able to restart, although there is a possibility of the database crashing.

[swigsstaking]

while maintaining my node was working but I had to restart the server and my two clients can no longer communicate although both are working. I have this error message in my op-node log: WARN [12-24|06:19:58.362] failed to notify engine driver of new L2 payload err="context deadline exceeded" id=c90f49..e01047: 113899995

[sbvegan]

Hey @swigsstaking, do you mind copy and pasting those logs? I'd like to add this to our troubleshooting page.

[swigsstaking]

./bin/op-node --l1=$L1_RPC_URL --l1.rpckind=$L1_RPC_KIND --l2=ws://localhost:8551 --l2.jwt-secret=./jwt.txt --network=op-mainnet --rpc.addr=0.0.0.0 --rpc.port=8547
INFO [12-20|09:45:56.824] Not opted in to ProtocolVersions signal loading, disabling ProtocolVersions contract now.
INFO [12-20|09:45:56.881] Rollup Config l2_chain_id=10 l2_network=OP-Mainnet l1_chain_id=1 l1_network=mainnet l2_start_time=1,686,068,903 l2_block_hash=0xdbf6a80fef073de06add9b0d14026d6e5a86c85f6d102c36d3d8e9cf89c2afd3 l2_block_number=105,235,063 l1_block_hash=0x438335a20d98863a4c0c97999eb2481921ccd28553eac6f913af7c12aec04108 l1_block_number=17,422,590 regolith_time="@ genesis" canyon_time="@ 1704992401 ~ Thu Jan 11 17:00:01 UTC 2024" span_batch_time="(not configured)"
INFO [12-20|09:45:56.881] Initializing rollup node version=v0.0.0-6a9f126e-1702334001
WARN [12-20|09:45:56.887] failed to dial address, but may connect later addr=ws://localhost:8551
WARN [12-20|09:45:58.063] failed to dial address, but may connect later addr=ws://localhost:8551
WARN [12-20|09:46:00.080] failed to dial address, but may connect later addr=ws://localhost:8551
WARN [12-20|09:46:04.114] failed to dial address, but may connect later addr=ws://localhost:8551
WARN [12-20|09:46:12.363] failed to dial address, but may connect later addr=ws://localhost:8551
WARN [12-20|09:46:22.435] failed to dial address, but may connect later addr=ws://localhost:8551
WARN [12-20|09:46:32.454] failed to dial address, but may connect later addr=ws://localhost:8551
WARN [12-20|09:46:42.643] failed to dial address, but may connect later addr=ws://localhost:8551
WARN [12-20|09:46:52.673] failed to dial address, but may connect later addr=ws://localhost:8551
WARN [12-20|09:47:02.714] failed to dial address, but may connect later addr=ws://localhost:8551
ERROR[12-20|09:47:02.714] Error initializing the rollup node err="failed to init L2: failed to setup L2 execution-engine RPC client: operation failed permanently after 10 attempts: address unavailable (ws://localhost:8551)"
CRIT [12-20|09:47:02.714] Application failed message="failed to setup: unable to create the rollup node: failed to init L2: failed to setup L2 execution-engine RPC client: operation failed permanently after 10 attempts: address unavailable (ws://localhost:8551)"

[github-actions[bot]]

Hey @swigsstaking, We hope your recent question was resolved to your satisfaction. Your feedback is invaluable and helps us improve our support services. Could you spare a moment to fill out a short feedback survey. Thank you for helping us improve our developer community.