Version Upgrade
Upgrade is not required at this point! Only use this guide to upgrade a validator that was installed and working using the previous guide!
This process can be completed on a validator that is running but may fall delinquent if resources are too limited. Complete using xand user without sudo privledge.
Update repo, checkout new tag, and build.
Change directory into validator repo
cd ~/solanaUpdate repo
git remote update origin --pruneCheckout new version number
git checkout v1.16.10Build new release
./cargo build --releaseNOTE: Try adding -j 2 to limit the build to 2 cpu cores if needed.
When build completes, create new folders for the new version.
mkdir ~/.local/share/solana/install/releases/1.16.10/bin -pChange directory into new build release folder
cd ~/solana/target/releaseMove all files to new bin folder
mv * .* ~/.local/share/solana/install/releases/1.16.10/binIgnore these errors...as these folders can't move:
mv: cannot move '.' to '/home/xand/.local/share/solana/install/releases/1.16.10/bin/.': Device or resource busy mv: cannot move '..' to '/home/xand/.local/share/solana/install/releases/1.16.10/bin/..': Device or resource busy
Check your current version and note so you can compare with later
solana -VUpdate the symlink to point to new binaries
ln -sf <path/to/binaries/> <path/to/symlink/>
ln -sf /home/xand/.local/share/solana/install/releases/1.16.10/bin/ /home/xand/.local/share/solana/install/releases/active_release/Check your new version is being used and compare with former
solana -VIf the new version shows up, then time to restart your validator! It will restart using the new binaries.
solana-validator --ledger ~/ledger exit --max-delinquent-stake 10 --min-idle-time 0 --monitorNOTE: Follow along with the restart using the ./mon.sh and ./catchup.sh tools in another shell created in Monitoring your validator