[OP Stack Deployment] <getting issue in running op-batcher in linux > #716
Replies: 14 comments 19 replies
-
|
1:are you running batch for you own op stack chain?if so,how you deploy it?(op-deployer? or from tutorials/chain branch?) |
Beta Was this translation helpful? Give feedback.
-
|
so i was following the tutorials/chain and i tried to run op batcher , the docs are removed i think https://docs.optimism.io/builders/chain-operators/tutorials/create-l2-rollup i can't able to access that command again. but yesterday i got that issue when i tried to run op batcher i was following tutorials/chain in the op docs which are now removed |
Beta Was this translation helpful? Give feedback.
-
|
what i was doing is , basically test a l2 chain on testnet built using op-stack. |
Beta Was this translation helpful? Give feedback.
-
the URL changed a little bit https://docs.optimism.io/operators/chain-operators/tutorials/create-l2-rollup
then how you can run the batcher and get the error log now?you can also try find how you start batcher in .bash_history also,please do the point 3, the curl command so that we can see the node is working or not |
Beta Was this translation helpful? Give feedback.
-
|
curl -X POST -H "Content-Type: application/json" --data \ ✔ |
Beta Was this translation helpful? Give feedback.
-
This is my OP-GETH response./build/bin/geth \ ✔ This is of OP-NODE response./bin/op-node \ ✔ ▼ This is op-batcher response./bin/op-batcher \ ✔ ▼ This is OP-PROPOSER response ~/optimism/op-proposer develop *1 !3 ?4 ./bin/op-proposer \ ✔ ▼ i just wanted to know what is wrong happening here and how to fix this . |
Beta Was this translation helpful? Give feedback.
-
|
can you add |
Beta Was this translation helpful? Give feedback.
-
|
./bin/op-node \ INT ✘ ▼ not working same issue as above |
Beta Was this translation helpful? Give feedback.
-
|
node log?i saw your ✔ mark disappeared |
Beta Was this translation helpful? Give feedback.
-
|
where ?? |
Beta Was this translation helpful? Give feedback.
-
|
./bin/op-node \ INT ✘ ▼ |
Beta Was this translation helpful? Give feedback.
-
|
First， follow this to restart your chain https://docs.optimism.io/operators/chain-operators/management/operations#stopping-your-rollup The inability of op-proposer and op-batcher to connect to op-node may be temporary. Please keep running for a while and observe |
Beta Was this translation helpful? Give feedback.
-
|
failed to fetch receipts of L1 block You need to check your L1 RPC if it is getting rate limited |
Beta Was this translation helpful? Give feedback.
-
|
./bin/op-node \ INT ✘ ▼ |
Beta Was this translation helpful? Give feedback.
-
|
You're likely getting rate limited. Infura RPC free plan isn't designed for running OP Stack chain. You can try Alchemy free plan: https://www.alchemy.com/ And make sure to set |
Beta Was this translation helpful? Give feedback.
-
|
INFO [02-11|12:07:13.904] Channel closed id=e3bd96..1d5f2b blocks_pending=0 num_frames=1 input_bytes=81 output_bytes=120 full_reason="channel full: close to sequencer window timeout" compr_ratio=1.481 [02-11|11:46:54.621] Connected to L2OutputOracle address=0x2BB24C12566804F72f13Dc7f012386F819342189 version=1.7.0 |
Beta Was this translation helpful? Give feedback.
-
|
FO [02-11|12:02:45.405] Advancing bq origin origin=52b7ef..70d5b3:7645573 originBehind=false |
Beta Was this translation helpful? Give feedback.
-
|
i corrected rpc still getting issue |
Beta Was this translation helpful? Give feedback.
-
|
You have to wait for a while as op-node is syncing... Wait for Advancing bq origin to hit the sepolia chain head Now op-node is on block 7645590 which is 5 days ago |
Beta Was this translation helpful? Give feedback.
-
|
./bin/op-node \ ✔ ▼ this issue |
Beta Was this translation helpful? Give feedback.
-
Seems you hadn't setup the |
Beta Was this translation helpful? Give feedback.
-
|
If i want want deploy my own rollup using op-stack on mainnet how to any guide ?? |
Beta Was this translation helpful? Give feedback.
-
|
OsirisOx — Yesterday at 9:55 PM @OsirisOx Shak — Yesterday at 10:07 PM |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
yes exactly |
Beta Was this translation helpful? Give feedback.
-
|
i havn't tried that above i'll and let you know |
Beta Was this translation helpful? Give feedback.
-
|
hey @jsvisa getting this issue in the running local development node Adding service with name 'cl-1-lighthouse-geth' and image 'ethpandaops/lighthouse:stable' == FINISHED SERVICE 'cl-1-lighthouse-geth' LOGS =================================== Error encountered running Starlark code. |
Beta Was this translation helpful? Give feedback.
-
|
@jsvisa help me i tried too much still getting same issue |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for the delay, it appers this issue is a known bug documented in ethpandaops/ethereum-package#899, as a walkaround, could you please append the below configs into network-config.yaml: ethereum_package:
participants:
- el_type: geth
cl_type: tekuAfter appended, the network-config.yaml now looks like below: optimism_package:
chains:
- participants:
- el_type: op-geth # this node will be the sequencer since it's first in the list
network_params:
name: rollup-1 # can be anything as long as it is unique
network_id: 12345 # can be anything as long as it is unique
ethereum_package:
participants:
- el_type: geth
cl_type: tekuAnd then take a retry. |
Beta Was this translation helpful? Give feedback.
-
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
NFO [02-07|10:55:22.977] Initializing Batch Submitter
INFO [02-07|10:55:23.743] metrics disabled
INFO [02-07|10:55:23.743] Admin RPC enabled
INFO [02-07|10:55:23.743] Starting JSON-RPC server
INFO [02-07|10:55:23.754] Starting batcher notSubmittingOnStart=false
INFO [02-07|10:55:23.754] Starting Batch Submitter
INFO [02-07|10:55:23.754] Batch Submitter started
INFO [02-07|10:55:27.631] Starting batch-submitter work at safe-head safe=5f6cbc..8d802d:0
WARN [02-07|10:55:27.631] Error calculating L2 block range err="L2 safe head ahead of L2 unsafe head"
WARN [02-07|10:55:38.115] Error calculating L2 block range err="failed to get sync status: Post "http://localhost:9545/": context deadline exceeded"
WARN [02-07|10:55:41.522] Error calculating L2 block range err="L2 safe head ahead of L2 unsafe head"
WARN [02-07|10:55:47.634] Error calculating L2 block range err="L2 safe head ahead of L2 unsafe head"
WARN [02-07|10:55:50.606] Error calculating L2 block range err="L2 safe head ahead of L2 unsafe head"
WARN [02-07|10:55:52.620] Error calculating L2 block range err="L2 safe head ahead of L2 unsafe head"
WARN [02-07|10:55:55.008] Error calculating L2 block range err="L2 safe head ahead of L2 unsafe head"
i am getting this error in op batcher what could be the reason ??
Logs
No response
Additional Information
No response
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions