added troubleshooting section

[schmunk42]

No description provided.

[fermayo]

doesn't the agent autostart when the VM starts? I cannot reproduce that issue

[schmunk42]

No, not reliably.
Maybe if you shut down the system in a clean way. But not if the underlying system had a problem.
The tutum-Agent says it is running but the node remains unreachable.

Von meinem iPhone gesendet

Am 06.04.2015 um 13:43 schrieb Fernando Mayo notifications@github.com:

doesn't the agent autostart when the VM starts? I cannot reproduce that issue

—
Reply to this email directly or view it on GitHub.

[schmunk42]

You could try to reproduce this by starting a Vagrant VM node.
And then simply turn it off (hard shutdown), does it become available after a restart for you?

[fermayo]

Yes, it works for me... Could you reproduce it on your end and paste the agent logs at /var/log/tutum/agent.log?

And also, which vagrant box version are you using? Could you try to run the following?

$ vagrant box update
==> default: Checking for updates to 'tutum/node'
    default: Latest installed version: 0.13.2
    default: Version constraints:
    default: Provider: virtualbox
==> default: Box 'tutum/node' (v0.13.2) is running the latest version.

Thanks!

[schmunk42]

2015/04/07 07:34:59 Set logger to /var/log/tutum/agent.log
2015/04/07 07:34:59 Preparing directories and files...
2015/04/07 07:34:59 Checking if config file exists...
2015/04/07 07:34:59 Config file exist, skipping
2015/04/07 07:34:59 Loading Configuration file...
2015/04/07 07:34:59 Removing all existing cert and key files https://dashboard.tutum.co/api/agent/node/
2015/04/07 07:34:59 Registering in Tutum via POST: https://dashboard.tutum.co/api/agent/node/ ...
2015/04/07 07:35:05 Checking if TLS certificate exists...
2015/04/07 07:35:05 No tls certificate founds, creating a new one using CN: [CORRECT_ID].node.tutum.io
2015/04/07 07:35:05 Written certificate to /etc/tutum/agent/cert.pem
2015/04/07 07:35:05 Written /etc/tutum/agent/key.pem
2015/04/07 07:35:05 New tls certificate is generated
2015/04/07 07:35:05 Registering in Tutum via PATCH: https://dashboard.tutum.co/api/agent/node/ ...
2015/04/07 07:35:05 Registration failed, Status: 405. Retry in 1 seconds
2015/04/07 07:35:12 Registration failed, Status: 405. Retry in 2 seconds
2015/04/07 07:35:20 Registration failed, Status: 405. Retry in 4 seconds
2015/04/07 07:35:30 Registration failed, Status: 405. Retry in 8 seconds
2015/04/07 07:35:44 Registration failed, Status: 405. Retry in 16 seconds
2015/04/07 07:36:01 Registration failed, Status: 405. Retry in 32 seconds
2015/04/07 07:36:33 Registration failed, Status: 405. Retry in 64 seconds
2015/04/07 07:37:38 Registration failed, Status: 405. Retry in 128 seconds

[schmunk42]

Works for me now...

[Zertz]

@schmunk42 Late to the party, but I've had this happen in the past as well. Seems to be fixed now though.