From 3f7a5d9e807550736c4ef5c55fce5e4e4c7f994b Mon Sep 17 00:00:00 2001 From: Tobias Munk Date: Sun, 5 Apr 2015 23:05:16 +0200 Subject: [PATCH 1/4] added troubleshooting section with tutum-agent restart --- README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.md b/README.md index 61f4aa3..b33c101 100644 --- a/README.md +++ b/README.md @@ -12,3 +12,11 @@ Get your `` by clicking on `Bring your own node` in Tutum's [Nodes dashbo vagrant init tutum/node TUTUM_TOKEN= vagrant up + +## Troubleshooting + +If you had to restart your Vagrant VM or underlying machine and your node remains *unreachable*, restart the `tutum-agent` with this command. + + service tutum-agent restart + +And your node should become available again. From 0021ebd38d3bebb7af115ea87fb0433518dc39d0 Mon Sep 17 00:00:00 2001 From: Tobias Munk Date: Sun, 5 Apr 2015 23:05:47 +0200 Subject: [PATCH 2/4] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b33c101..14d5909 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ Get your `` by clicking on `Bring your own node` in Tutum's [Nodes dashbo ## Troubleshooting -If you had to restart your Vagrant VM or underlying machine and your node remains *unreachable*, restart the `tutum-agent` with this command. +If you had to restart your Vagrant VM or underlying machine and your node remains *unreachable*, login to the VM and restart the `tutum-agent` with this command. service tutum-agent restart From a34ea48e7b5b23d7df5448785c6dfbdcabff6a54 Mon Sep 17 00:00:00 2001 From: Borja Burgos Date: Thu, 9 Apr 2015 15:50:24 -0400 Subject: [PATCH 3/4] Update README.md --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 61f4aa3..f075976 100644 --- a/README.md +++ b/README.md @@ -1,14 +1,16 @@ # tutum-node -Run your Tutum node inside a container! - Get your `` by clicking on `Bring your own node` in Tutum's [Nodes dashboard](https://dashboard.tutum.co/node/cluster/list/) ## Usage (using Docker) +Run your Tutum node inside a container! + docker run -d --net=host --privileged --restart=always -e TUTUM_TOKEN= tutum/node ## Usage (using Vagrant) +Run your Tutum node inside a Vagrant box! + vagrant init tutum/node TUTUM_TOKEN= vagrant up From 03352f7ae8f3421570df46e742f2c22b218b8d6c Mon Sep 17 00:00:00 2001 From: Tobias Munk Date: Fri, 17 Apr 2015 01:20:19 +0200 Subject: [PATCH 4/4] added instructions how to re-register a node --- README.md | 42 ++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 40 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 0134cd1..d8a053c 100644 --- a/README.md +++ b/README.md @@ -17,8 +17,46 @@ Run your Tutum node inside a Vagrant box! ## Troubleshooting -If you had to restart your Vagrant VM or underlying machine and your node remains *unreachable*, login to the VM and restart the `tutum-agent` with this command. +### Re-register a node after an unintended shutdown + +Use-case: Your Vagrant VM or underlying machine was experiencing a hard shutdown and your node remains *unreachable*, i.e. after +a server crash. + +In some cases a node might not be able to re-register itself correctly with tutum, to trigger a reconnection of a VM +with an existing node entry, follow these steps: + +Login to the node + + ssh mynode + +restart the `tutum-agent` with this command. service tutum-agent restart -And your node should become available again. +Check the logs if needed, the node may need about 1-2 minutes to come up again. + + tail -f /var/log/tutum/agent.log + +### Re-register with existing parameters + +If you're still experiencing issues, like [this one](https://github.com/tutumcloud/tutum-node/pull/1). + +Aquire your API token from your [account info page](https://dashboard.tutum.co/account/) + + export TUTUM_API_TOKEN=12345abcde12345abcde12345abcde12345abcde + +Go to the [cluster list](https://dashboard.tutum.co/node/cluster/list/) and get the `BYON_TOKEN` from the modal after clicking the `Bring your own node` button. + + export TUTUM_BYON_TOKEN=f1e2d3c4b5af1e2d3c4b5af1e2d3c4bc + +Get the UUID of the node by navigating to it's URL in the [cluster list](https://dashboard.tutum.co/node/cluster/list/). +Use the last part of the URL without the slash. + + export TUTUM_NODE_UUID=1a2b3c4d-5f6a-0e0d-1a2b-1234567890ab + +Set the API token value and run the command from the modal window in the Web UI. *Hint: You can also show the command with `tutum-cli`* + + sudo tutum-agent set TutumToken=$TUTUM_API_TOKEN + curl -Ls https://get.tutum.co/ | sudo -H sh -s $TUTUM_BYON_TOKEN $TUTUM_NODE_UUID '*.node.tutum.io' + +Check the logs, your node should register with the API under it's existing identifier. \ No newline at end of file