Why rename folder .fuelup_beta4 to .fuelup_beta5 ?
→ Because .fuelup_beta5 is not created automatically after using these commands :
~ fuelup toolchain install beta-5
~ fuelup default beta-5
And if you run the command ; rm rf ~/.fuel/db ?
→ No, same issue is returned when I re-run the node command launch
Other question : Why .fuelup toolchain install --help doesn’t return beta-5 as value ?
Thank you for you answer.
The issue is different but still present :
2024-03-05T10:49:25.089719Z INFO fuel_core::cli::run: 266: Block production disabled
2024-03-05T10:49:25.089770Z WARN fuel_core::cli::run: 294: The coinbase recipient `ContractId` is not set!
2024-03-05T10:49:25.089781Z INFO fuel_core::cli::run: 358: Fuel Core version v0.22.1
2024-03-05T10:49:25.089787Z INFO fuel_core::service: 95: Opening database "/root/.fuel_beta5" with cache size "1073741824"
2024-03-05T10:49:25.101975Z ERROR fuel_core::state::rocks_db: 169: Couldn't open the database with an error: Invalid argument: Column families not opened: column-24, column-23, column-22, column-21, column-20, column-19, column-18, column-17, column-16, column-15, column-14, column-13, column-0, column-1, column-2, column-3, column-4, column-5, column-6, column-7, column-8, column-9, column-10, column-11, column-12.
Trying to repair the database
Error: Failed to open rocksdb, you may need to wipe a pre-existing incompatible db `rm -rf ~/.fuel/db
Sorry you are still encountering errors. One thing that might work is rm-rf ~/.fuel_beta5. If this doesn’t work could you please show me the output/screenshot of: fuelup show fuelup check which fuel-core
Also I’m not sure why beta-5 is not listed as a toolchain in fuelup, but the lastest toolchain is pinned to the same versions as the beta-5 toolchain. Why do you expect .fuelup_beta5 to be created? Do we mention that somewhere in our docs? fuelup manages various toolchains from the ~/.fuelup folder.
So all of the output of your commands looks correct. Did you try my suggestion of removing the ~/.fuel_beta5 folder before running the command again?
When running this on my computer I did not have to create this folder. I believe if the command fails it probably does not create the folder which is what is happening in your case.
Where are you running the command fuel-core run ... from?
Somes projects add the posibility to link the node/validator to a wallet address through the creation run command.
That give the possibilities to interact with project network , like : create smart contract or make staking actions directly through the wallet linked to a validator.
I don’t find this on Fuel project, maybe I missed something