Lisk-Core Update flow
- Stop running lisk-core
- Make a backup of your custom configuration and the
pm2.conf.json
file. - Download latest lisk-core from binary or npm
- Binary:
curl -o lisk-core.tar.gz https://downloads.lisk.io/lisk/testnet/3.0.0-rc.4/lisk-core-v3.0.0-rc.4-linux-x64.tar.gz
tar -xf ./lisk-core.tar.gz
- NPM:
npm install --global lisk-core@3.0.0-rc.4
- Binary:
- Remove old snapshots, if existent:
rm blockchain.db.tar.gz && rm blockchain.db.tar.gz.SHA256
- Download the testnet snapshot from height 14183092 (rollbacked snapshot):
lisk-core blockchain:download -n testnet
- Verify the checksum of the snapshot:
sha256sum blockchain.db.tar.gz
- The sha256 checksum should be
125f83dc2773e79272c2ddcfd9016aeeac0690a085f2029b148bc1a5f1a084e7
- Import the testnet snapshot from height 14183092
lisk-core blockchain:import --force ./blockchain.db.tar.gz
- Remove PoM data if any. By default, it would be below path
rm -f ~/.lisk/lisk-core/plugins/data/lisk-framework-report-misbehavior-plugin.db
- Update network version on lisk-core
updatenetworkVersion
to"3.0"
on file~/lisk-core/config/testnet/custom-config.json
- Start running lisk-core
lisk-core start -n testnet --api-ws
- Check valid forger info:
lisk-core forging:status
- Use the forger info to enable forging
Lisk-Service Update flow (Docker)
In case you’ve been using Installation with Docker - Lisk Service Docs
- Stop running Lisk Service (make down)
- Update lisk-core with the instructions above
- Start Lisk Service (make up)
Lisk-Service Update flow (source code)
In case you’ve been using Installation from source code - Lisk Service Docs
- Stop running Lisk Service
-
Ctrl+C
when usingnpm start
-
pm2 stop lisk-service-core
for PM2 deployments
-
- Flush the MySQL database:
- Access the MYSQL CLI:
mysql -u root -p
- and then
mysql> DROP DATABASE lisk; CREATE DATABASE lisk
- Access the MYSQL CLI:
- Flush Redis
- Access the Redis CLI:
redis-cli
- and then type
FLUSHALL
(note this will drop your all Redis DBs)
- Access the Redis CLI:
- Update lisk-core with the above instructions
- Start Lisk Service (
npm start
orpm2 restart lisk-service-core
)
The Lisk Service search index needs to be rebuilt. It can take 1-2 hrs depending on the machine you’re using.