Skip to content

Go-Opera Archive Node Upgrade Process from [release/txtracing/1.1.3-rc.5] to [v1.2.1-i] #406

@keennay

Description

@keennay

Hi,

Are there any recommended steps when upgrading a Fantom Go-Opera Mainnet archive node originally used with the release/txtracing/1.1.3-rc.5 branch to v1.2.1-i? We still need to support historical transactions for the Fantom Mainnet chain on our end. This archive node is also 19 TB and I want to prevent corrupting that database.

I see the chaindata directory for my Go-Opera node includes the following three directories:

  • leveldb-drc
  • leveldb-flg
  • leveldb-fsh
  • pebble-drc
  • pebble-flg
  • pebble-fsh

New syncs for Sonic v1.2.1-i don't show these directories, and only include gossip & lachesis. I also receive the below error when attempting to sync Sonic v1.2.1-i using the datadir of my Go-Opera node.

CRIT [05-08|20:37:27.682] Epoch state reading failed: genesis not applied

Please advise, thx

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions