Manage core services

How to check and update services

Manage core services

This section provides a low-level explanation of how the services work, which is essential for debugging, even if the infrastructure is built using Kubernetes (K8s). Kubernetes also utilizes these methods under the hood.

<aside> 📌

For deployment and management using Kubernetes (K8s), refer to this link

</aside>

To ensure proper operation, the nodes must be started in the order specified in this document and shut down in the reverse order:

• op-geth
• op-node
• op-proposer
• op-batcher

op-geth

• Start up the node

  • Archive Mode: It is crucial to run the op-geth node in archive mode using the -gcmode flag. Archive mode enables recording all historical data at any block number, which is particularly useful for recovery in case of issues.
  • WebSocket Support: Use the —ws flag to enable WebSocket. This allows DApps to listen for events on the L2 network.

  geth \
  	--datadir=/db \
  	--verbosity=3 \
  	--http \
  	--http.corsdomain=* \
  	--http.vhosts=* \
  	--http.addr=0.0.0.0 \
  	--http.port=8545 \
  	--http.api=web3,debug,eth,txpool,net,engine \
  	--ws \
  	--ws.addr=0.0.0.0 \
  	--ws.port=8546 \
  	--ws.origins=* \
  	--ws.api=debug,eth,txpool,net,engine \
  	--syncmode=full \
  	--nodiscover \
  	--maxpeers=0 \
  	--networkid=901 \
  	--rpc.allow-unprotected-txs \
  	--authrpc.addr=0.0.0.0 \
  	--authrpc.port=8551 \
  	--authrpc.vhosts=* \
  	--authrpc.jwtsecret=jwt-secret.txt \
  	--gcmode=archive \
  	--state.scheme=hash \
  	--metrics \
  	--metrics.addr=0.0.0.0 \
  	--metrics.port=6060
  
  

  

• Shut down the node

  • Using archive mode can help reduce data loss in case shutting down unexpectedly. However, the op-geth needs to be stopped gracefully by sending a SIGINT signal to the op-geth process.
  • The archive mode cannot address all scenarios, so it is beneficial to have another replica of op-geth and op-node running in sync with each other. This redundancy ensures that if one node goes down unexpectedly, the other can continue providing data and minimize downtime.
  • Some command examples for shutting down the op-geth node (all commands must to send SIGINT signals).

  # Kill process with a SIGINT directly
  kill -2 <Process ID>
  
  # 
  docker stop -t 300 <Container ID>
  

op-node

• Start up the node

  • op-node processes L1’s data, communicates with op-geth and instructs op-geth on how to build L2.
  • Example command and result:

  op-node \
  	--l1=<L1_RPC> \
  	--l1.fork-public-network=False \
  	--l2=http://0.0.0.0:8551 \
  	--l2.jwt-secret=jwt-secret.txt \
  	--sequencer.enabled \
  	--sequencer.l1-confs=0 \
  	--verifier.l1-confs=0 \
  	--p2p.sequencer.key=<p2p sequencer key> \
  	--rollup.config=rollup.json \
  	--rpc.addr=0.0.0.0 \
  	--rpc.port=8545 \
  	--p2p.listen.ip=0.0.0.0 \
  	--p2p.listen.tcp=9003 \
  	--p2p.listen.udp=9003 \
  	--p2p.scoring.peers=light \
  	--p2p.ban.peers=true \
  	--snapshotlog.file=snapshot.log \
  	--p2p.priv.path=p2p-node-key.txt \
  	--metrics.enabled \
  	--metrics.addr=0.0.0.0 \
  	--metrics.port=7300 \
  	--rpc.enable-admin \
  	--l1.beacon= \
  	--l1.trustrpc