The machine seems to have been auto-spun up by the machine rules in the app and now won’t come up or down and is wreaking havoc on the network.
Error: could not kill machine 7843694be3ded8: failed to kill VM 7843694be3ded8: unavailable: dial tcp: connect: connection refused
Error: could not destroy machine 7843694be3ded8: failed to destroy VM 7843694be3ded8: request returned non-2xx status: 408
Getting errors when trying to kill this machine both from the flyctl and from the GUI.
I’m seeeing the same issue, I have two apps in lhr that each have one unreachable machine host. I cannot kill/destroy either.
we’re looking at this now, you should see a host issue in your personal status page
Feel free to kill the misbehaving instances. I just need things back online.
it should be back now, can you try deleting the machine again now?
I was able to run fly scale count ${procName}=0 followed by fly scale count ${procName}=${originalCount}, as recommended by the email sent out – not sure if that was before or after any changes on fly.io’s end.
It is back up and running and I can manage the machines as normal. Thanks.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
