Troubleshooting

1. Current version of go-opera

The current supported version is go-opera 1.0.2-rc5 for both mainnet and testnet.

Go-opera older than 1.0.2-rc5

You should download and use 1.0.2-rc.5

Trouble shooting: Syncing error

If you're downloading a version older than 1.0.2-rc5, and thus you can't sync or you may get any errors, then please make sure you:
  • Stop the node
  • Remove the current (broken) datadir (the default datadir is located at ~/.opera)
  • Download and build the latest version go-opera 1.0.2-rc5
  • Run your node again in read mode

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). You can check your log to see the progress. After migration, the node will run normal.
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).

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:
  • 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.
Last modified 7d ago