Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Emergency Procedures #58

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update Emergency Procedures #58

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions thornodes/emergency-procedures.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,6 +74,9 @@ All wallets and frontends should monitor for any of the halts and automatically

## Node Migration

###
🚩 Warning: Running more than one active `thornode` with the same keys will result in significant bond slashing. It is highly recommended that you only use this procedure in emergency situations and while your node is in `Standby`. In addition, be certain your old node is disabled before your new node becomes `Active`.

### Create node backup

* [ ] Copy mnemonic with the following command
Expand Down Expand Up @@ -111,6 +114,7 @@ kubectl cp thornode/\$pod:/root/.thornode/bifrost.tar ~/bifrost.tar

### Restore Node backup

* [ ] When setting up your new node, it is important to set the same password for your `thornode` during `make install`
* [ ] Copy node backup files made in [Node backup section](emergency-procedures.md#create-node-backup) to the new node's control station
* [ ] Create `yaml` config files for temporary pods thornode-recovery.yaml

Expand Down Expand Up @@ -182,7 +186,7 @@ kubectl cp keyring-file/thorchain.info bifrost-recovery:/data/thornode/keyring-f

```
kubectl cp bifrost.tar bifrost-recovery:/data/thornode/bifrost.tar
kubectl exec deploy/thornode -c bifrost-recovery -- sh -c "cd /root/.thornode && tar xf bifrost.tar"
kubectl exec bifrost-recovery -- sh -c "mkdir /root/.thornode && cd /root/.thornode && tar xf /data/thornode/bifrost.tar"
```

* [ ] Stop temporary pods
Expand All @@ -192,7 +196,7 @@ kubectl delete -f thornode-recovery.yaml
kubectl delete -f bifrost-recovery.yaml
```

> **If you're maling live migration, then after stopping temporary pods on the NEW node stop thornode and bifrost daemons on the OLD node**
> **🚩After stopping temporary pods on the NEW node, ensure that you have stopped `thornode` and `bifrost` daemons on the OLD node BEFORE you re-enable `thornode` and `bifrost`. Failure to do so will result in significant bond slashing.**

* [ ] Re-scale thornode and bifrost deployments

Expand Down