Unhealthy Agent in Stopped Container - shut down script failed #18840
Unanswered
jbnitorum
asked this question in
Workspace Provisioning & Templates
Replies: 1 comment
-
nevermind... figured it out. Sorry, new to coder. I needed to change the terraform code so it destroyed the agent on stop. Nothing to do with agent logs... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I can't quite seem to figure this one out. I have a workspace running inside a docker container on an EC2. The EC2 persists, does not terminate, just stops and starts. When I move to a stopped state everything works as expected, but in the UI I get an orange dot and it says that the agent is unhealthy, even though the workspace has stopped. I had assumed there is something where the agent inside the container isn't exiting gracefully maybe? I can't quite get it to look pretty on the UI.
When I go back into the instance after restarting from a stopped state the container logs from when the workspace starting stopping look like this:
followed by this a bunch times:
then I get this
Then thats followed by more 401 errors of the agent trying to connect. So i guess it tries to exit, fails, and then because it keeps pinging until the last moment the UI goes orange because it never gets a shutdown notification?
Beta Was this translation helpful? Give feedback.
All reactions