Update reconnect node with kickstart info (#12891)
* Update reconnect node with kickstart info * Split stop from start Second change done because restart may very easily result in the agent failing to connect because of problematic handling of reconnections.
Chris Akritidis committed
May 13, 2022 at 07:34 UTC
eb67c421985382c0b33e835421a1a45fd66c994a
1 file changed
+6
-9
claim/README.md
+6
-9
@@ -492,16 +492,13 @@ sudo rm -rf cloud.d/
492
This node no longer has access to the credentials it was used when connecting to Netdata Cloud via the ACLK.
493
You will still be able to see this node in your War Rooms in an **unreachable** state.
494
495
-If you want to reconnect this node, you need to create a new identity by adding `-id=$(uuidgen)` to
496
-the claiming script parameters (not yet supported on the kickstart script). Make sure that you have the `uuidgen-runtime` package installed, as it is used to run the command `uuidgen`. For example:
495
+If you want to reconnect this node, you need to:
496
+1. Ensure that the `/var/lib/netdata/cloud.d` directory doesn't exist.
497
+2. Stop the agent.
498
+3. Ensure that the `uuidgen-runtime` package is installed. Run ```echo "$(uuidgen)"``` and validate you get back a UUID.
499
+4. Copy the kickstart.sh command to add a node from your space and add to the end of it `--claim-id "$(uuidgen)"`. Run the command and look for the message `Node was successfully claimed.`
500
+5. Start the agent
501
498
-**Claiming script**
499
-
500
-```bash
501
-sudo netdata-claim.sh -token=TOKEN -rooms=ROOM1,ROOM2 -url=https://app.netdata.cloud -id=$(uuidgen)
502
-```
503
-
504
-The agent _must be restarted_ after this change.
502
503
## Connecting reference
504
In the sections below, you can find reference material for the kickstart script, claiming script, connecting via the Agent's command line