I have a few devices set up in my account that all run on the same application. I recently set up 3rd-party logging to Papertrail, and through that I can see the resin_supervisor logs.
The supervisor on one of my devices has been throwing a 401 error every 10 seconds for some time now. It didn’t seem to affect functionality at first, but eventually the device failed (or ignored?) a Supervisor update. Since then it has started exhibiting other weird behavior, including not showing one of my application containers in the dashboard “Services” list, even though that container is actively logging in the dashboard log window. The device is also stuck on an older release of my application code.
The error in the logs is the only indication of a possible problem. My application containers are all running and logging fine with no issues (aside from them being an older version than expected). My other two devices are not exhibiting this issue.
The error in the logs is:
f7402c2 [error] Error from the API: 401 f7402c2 [error] Non-200 response from the API! Status code: 401 - message: Error f7402c2 [error] at /usr/src/app/dist/app.js:22:554770 f7402c2 [error] at runMicrotasks (<anonymous>) f7402c2 [error] at processTicksAndRejections (internal/process/task_queues.js:97:5) f7402c2 [error] at async /usr/src/app/dist/app.js:22:554078 f7402c2 [error] at async /usr/src/app/dist/app.js:22:555600
I have tried restarting containers, rebooting, and manually pulling the power plug and letting it sit offline for a bit. This is a development/test machine and is not important in the short term, however as I get closer to deployment, I’m worried about this happening in production and what options I would have to solve it in that situation.