Sorry guys. I think that was my fault. It was caused by the server maintenance that I performed this weekend. There is currently an issue where if the web server is down when the device tries to authenticate, it will result in the device restarting activation. The following is the sequence of events that causes it:
- The web server goes down
- The device connects to the device server and sends its authentication token to log in
- The device server tries to reach the web server to verify the authentication token
- The request fails since the web server is down
- The device server returns an "authentication failed" response since it could not complete the process
- The device takes this to mean that its authentication token is invalid, and it restarts the activation process so that it can obtain a new auth token
It is step 5 above that is causing this to happen. I was planning to fix this by returning a "try again" response to the device so that it would not restart activation when this happens, but this is a bit tricky since it involves changing the messaging between the device and the server and we have to remain backwards compatible with all Model-T's out there. I think it can be done, its just tricky.
I just realized that I could get this behavior by simply having the device server drop the device connection if it ever fails to reach the web server. This will cause the device to reconnect and try again rather than restarting activation. Plus, it would not require any messaging or device code changes either. I will try and get this implemented soon so we can stop this from happening.