Troubleshooting

1. Current version of go-opera
The current supported version is go-opera 1.1.0-rc.4 for both mainnet and testnet.
Go-opera older than 1.1.0-rc.4
You should download and use 1.1.0-rc.4
Trouble shooting: Syncing error
If you're downloading a version older than 1.1.0-rc4, and thus you can't sync or you may get any errors. Then you can try to fix a dirty state node.
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.0-rc4
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.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.
2.Run the node in go-lachesis 1.0.0-rc1. Simply run : https://github.com/Fantom-foundation/lachesis_launch/blob/release/opera-v1.0.0-rc1/docs/setup-readonly-node.sh​
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.
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. Dirty state node
If your node is in dirty state (it may happen occasionally), please download:
​https://github.com/Fantom-foundation/go-opera/tree/feature/fixdirty​
and run the following command:
opera fixdirty

Node - Previous

Testnet Faucet

Next - API

Public API endpoints

Last modified 22d ago

Copy link

Contents

1. Current version of go-opera

2. Pruning node state

3. Offline node

4. Dirty state node