Troubleshooting

1. Current version of go-opera

The current supported version is go-opera 1.1.1-rc.2 for both mainnet and testnet.

Go-opera older than 1.1.1-rc.2

You should download and use 1.1.1-rc.2

2. Pruning node state

If your node is about to run out of space, you may consider to extend the machine's storage OR to prune the current node's datadir. To prune the datadir, please use the following steps:

1) Manual pruning

  • Stop the node
  • Run at the terminal: ./opera snapshot prune-state
The state pruning process may take a couple of hours for every hundreds of GBs of data and the amount of time required will depend on the machine's speed.

2) Automatic pruning

Automatic pruning is introduced in https://github.com/Fantom-foundation/go-opera/releases/tag/v1.1.1-rc.2. You can run a node with --gcmode flag, either --gcmode full or --gcmode light. Note that
  • Both --gcmode full and --gcmode light will prune data that is processed after gcmode is enabled. Old data (before gcmode is enabled) is untouched.
  • Validator node can use --gcmode light but should not use --gcmode full.
  • --gcmode full option will prune much more EVM nodes than --gcmode light at expense of worse performance.

3. Offline node

If your validator node is down for more than 3 days, then it will become offline (i.e., pruned from the network). For offline node, you can undelegate and wait for 7 days to withdraw (bonding time). After that, you can transfer fund to a new wallet and make a new validator. Note that, if undelegating a locked stake or locked delegation before the locked period is expired, it will incur a penalty.

4. Trouble shooting: Syncing error

If your node is in dirty state (it may happen occasionally), please download:
and run the following command:
./opera fixdirty Alternatively, you may do a fresh resync as follows:
  • Stop the node
  • Remove the current (broken) datadir (the default datadir is located at ~/.opera)
  • Download and build the latest version go-opera 1.1.1-rc2
  • Run your node again in read mode

5. Old stuffs

Version go-lachesis 1.0.0-rc0 or older is longer supported.

If your node is in go-lachesis 1.0.0-rc0, and you still have events before migration (block 4564024), then you have two options:
  1. 1.
    Run the node in rc0 version and let the node complete the migration (it takes 1hr or more depending on the machine specs).
If the node was migrated successfully (check the log), then you can simply run in rc0 like before.
If the node failed the migration for whatever reason (check the log), then you will need to run the node in rc1. See the instruction above (option 2).