Todays incident 20 Dec, Volumes Endpoints returning 5XX

1

I am currently getting my feet wet, testing a simple app on a single machine. It was affected (I think, even though correlation is not…) by today’s incident.

I get http status 502 and it is unresponsive, see log below. I am trying to figure out what to do here. Might it be that the incident is not fully resolved or do I need to redeploy or recreate the app/machine. What is best practice? My app is just a lab, nothing mission critical.

Monitoring tells me the following.

proxy[56833274ad2578] ams [error] failed to change machine state: machine still active, refusing to start
proxy[56833274ad2578] ams [info] Starting machine
proxy[56833274ad2578] ams [error] failed to change machine state: machine still active, refusing to start
proxy[56833274ad2578] ams [error] could not find a good candidate within 90 attempts at load balancing
2

Tonight it started on schedule and performed an action but I think it failed so save data to the attached volume at the last run, so it worked on old data.

It still had the same error when triggering it with a http request so I redeployed and now its responding correctly.

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.