Installdocs 1 #1820
Installdocs 1 #1820
Conversation
| @@ -0,0 +1,66 @@ | |||
| # Troubleshooting - Adding or Upgrading Indy Nodes | |||
| Many things can go wrong while adding or upgrading nodes on an existing Indy network and this guide will cover symptoms and issues encountered and some steps you might take to recover from those. The steps listed are likely just possible remedies to the listed issues. Feel free to add more remedies or issues if you don't see your's included here. As bugs are fixed, the issues noted below might not occur any more, or might have a different remedy. | |||
There was a problem hiding this comment.
Scary. Perhaps just “Things an go wrong…"
| This section covers troubleshooting the addition of a node to a network. This can occur either as part of an upgrade (e.g. the 20.04 upgrade) or as part of a new node being added to an existing network. | ||
|
|
||
| ### Symptom 1 - Node is unresponsive | ||
| - Cause #1 - Node is performing catchup. (Large Network) |
There was a problem hiding this comment.
Given the discussion on the Indy Contributor’s call this week (2023.09.26), should the instructions not always say to have a “recent” copy of the Indy Node data folder for the network, so the “long catchup” is not an issue?
When upgrading, the advice can be to use the node’s own data folder.
When adding a new node, include a step where the node operator’s technical team provides a data folder from another node.
There was a problem hiding this comment.
Wade has not experienced the issue, it seems, so I wondered whether "every time" is appropriate for all networks. Until we figure out why this is only happening for me, maybe it's okay to leave this as is?
"Own" data folder is a great idea for the upgrade scenario.
There was a problem hiding this comment.
I think any time I can reduce the “wait” for something that might turn out badly is a good thing.
Not required — I just thing it is a good “best practice” vs. having nodes start from scratch. It doesn’t have to be a “to the minute” — it can be a “recent” backup to get (what appears to me to be) a significant benefit.
| 6. On your 2FA phone app, add an account, and then scan the barcode or enter the 16 character secret key from step 4’s output. | ||
| 7. Log out and then log back in to check and make sure it worked! | ||
| 5. All of your secondary admin users should be setup now. | ||
| 30. You can now begin the Indy Node installation using the Validator Preparation Guide. |
There was a problem hiding this comment.
Is there a link available to the guide?
There was a problem hiding this comment.
not yet, a future PR will have the guide in it
|
Awesome stuff. I added a couple of notes — one of which would seem to be important — the use of a data folder for the network when adding or upgrading a network. |
|
To clairfy my approval. I didn’t go through the steps in detail — just assume that a “best effort” was done in creating the steps, and from this basis we can evolve the steps further. |
|
Modified troubleshooting slightly based on Stephens comments above. I am not understanding why "statusCheck" is not passing, so some help here would be good. thx! |
…they have trouble while adding a node to a network. Some workarounds for bugs I encountered are included as well. Signed-off-by: Lynn Bendixsen <[email protected]>
Signed-off-by: Lynn Bendixsen <[email protected]>
…e in this commit. These install files are the ones that Indicio and Sovrin are using for the initial installation of servers in different scenarios. Signed-off-by: Lynn Bendixsen <[email protected]>
Signed-off-by: Lynn Bendixsen <[email protected]>
lynnbendixsen
force-pushed
the
installdocs-1
branch
from
a7aa3c3
to
c02538c
Compare
|
Fixed a DCO issue (last set of commits) |
Node installation documents to install the server.