[OP Stack Deployment] <Not able to deploy RPC archive node nor with docker or source>

[gautamjha2002]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I started Optimism rpc node with docker Firstly It stared syncing and now it is stucked Op-node is running fine but op-geth is not syncing right now.

Logs

The OP-Geth logs in docker container is like this

INFO [02-09|02:33:04.823] Regenerated local transaction journal    transactions=0 accounts=0
INFO [02-09|02:33:07.716] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|02:33:07.716] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|02:43:07.711] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|02:43:07.711] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|02:53:07.640] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|02:53:07.640] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|03:03:07.997] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|03:03:07.997] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|03:13:07.714] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|03:13:07.714] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|03:23:07.727] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|03:23:07.727] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|03:33:04.822] Regenerated local transaction journal    transactions=0 accounts=0
INFO [02-09|03:33:07.895] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|03:33:07.895] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|03:43:07.709] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|03:43:07.709] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|03:53:07.670] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|03:53:07.670] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|04:03:07.720] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|04:03:07.720] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|04:13:07.981] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|04:13:07.981] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|04:23:07.712] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|04:23:07.712] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|04:33:04.823] Regenerated local transaction journal    transactions=0 accounts=0
INFO [02-09|04:33:07.713] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|04:33:07.713] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|04:43:07.904] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|04:43:07.904] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|04:53:07.734] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0
INFO [02-09|04:53:07.734] Ahead with major required protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0

Additional Information

this is my .env file

###############################################################################
#                                ↓ REQUIRED ↓                                 #
###############################################################################

# Network to run the node on ("op-mainnet" or "op-sepolia")
NETWORK_NAME=op-mainnet

# Type of node to run ("full" or "archive"), note that "archive" is 10x bigger
NODE_TYPE=archive

###############################################################################
#                            ↓ REQUIRED (LEGACY) ↓                            #
###############################################################################

# L1 node to get chain data from (L2 sync no longer supported)
DATA_TRANSPORT_LAYER__RPC_ENDPOINT= < my own Eth RPC URL >

###############################################################################
#                            ↓ REQUIRED (BEDROCK) ↓                           #
###############################################################################

# Where to get the Bedrock database ("download" or "migration"), see README
BEDROCK_SOURCE=download

# L1 node that the op-node (Bedrock) will get chain data from
OP_NODE__RPC_ENDPOINT=< my own Eth RPC URL >

# Type of RPC that op-node is connected to, see README
OP_NODE__RPC_TYPE=basic

# Reference L2 node to run healthcheck against
HEALTHCHECK__REFERENCE_RPC_PROVIDER=https://mainnet.optimism.io

###############################################################################
#                            ↓ OPTIONAL (BEDROCK) ↓                           #
###############################################################################

# Optional provider to serve legacy RPC requests, see README
OP_GETH__HISTORICAL_RPC=https://mainnet.optimism.io

###############################################################################
#                                ↓ OPTIONAL ↓                                 #
###############################################################################

# Feel free to customize your image tag if you want, uses "latest" by default
# See here for all available images: https://hub.docker.com/u/ethereumoptimism

Feedback

No response

[sbvegan]

Hey @gautamjha2002,

Logs

These logs don't indicate a problem. It just means you're on the latest version of the protocol and the minimum required is v3.1.0:

INFO [02-09|03:43:07.709] Ahead with major recommended protocol version change local=v6.0.0-2 required=v3.1.0 recommended=v3.1.0

Check out the specs for details on the versions.

Request for Logs

It would be helpful to get the logs when op-geth first started up and any error/warning logs.

Misconfiguration

Historical RPC

If you're trying to run an archive node, you have the following line misconfigured:

OP_GETH__HISTORICAL_RPC=https://mainnet.optimism.io/

That url is the public endpoint for OP Mainnet. That configuration is meant to point to Legacy Geth (l2geth). More details on that in the docs here. OP Mainnet is a migrated network, so how the nodes worked pre-bedrock upgrade are different than post-bedrock upgrade. To get historical execution requests pre-bedrock op-geth will route them to l2geth.

DTL

I believe this line is deprecated, but I'm not positive:

DATA_TRANSPORT_LAYER__RPC_ENDPOINT= < my own Eth RPC URL >

Comments

This looks like an issue with the simple-optimism-node repository, can you open an issue there? cc @Chomtana fyi I think we need to look into the example environment file and fix a couple things.

[Chomtana]

Just notice a snapshot for Optimism mainnet archive node. It's possible that we need that to sync.

Also if we have a recent snapshot for Goerli or Sepolia, it would be great for testing a beacon node.

DTL should be deprecated

[Chomtana]

A patch for OP mainnet archive node snapshot is under testing: smartcontracts/simple-optimism-node#128