Witness Node Issues resolved and Back Producing

Hi Everyone, yesterday my Witness node crashed for some reason. The data was corrupted. I tried to bring it back with --replay-blockchain command, but it did not work. So, in morning I done something different.

@saboin helped me with a backup instead of presync image which is heavier than the backup.

Here are the steps I followed. (If any witness face corruption, can follow these steps)

1. Remove the existing container (if existing node, no need in case of new)

docker rm -f blurtd

2. Change to data directory and remove existing blockchain folder to prevent data corruption while copying and replacing.

cd /var/lib/docker/volumes/blurtd/_data/
rm -rf blockchain

3. Download the backup folder. It will take some time, so don't worry if there is no output as the file is around 6 GB and may take time to unpack after download is complete.

wget -qO- https://blurt-chain.s3.nl-ams.scw.cloud/witness-0.8.2-amd64-latest.tar.lz4 | lz4 -d | tar x

4. Turn up the docker container to bring your node up

docker run -d --init --net=host -v blurtd:/blurtd --name blurtd registry.gitlab.com/blurt/blurt/witness:dev /usr/bin/blurtd --data-dir /blurtd

Now you just need to wait until you start seeing block production.

The benefit of this way is now less space being used for node. Isnt it good ?

Thats all for now. Keep voting my witness to support me back.

Thanks everyone.

---

https://blurtwallet.com/~witnesses?highlight=tekraze

https://blurtwallet.com/~witnesses?highlight=blurt.one

---

---

_{Posted from https://blurt.one}