Got this machine causing issues on deployment. we have run the clone command to recreate but cant seen to remove this machine and every deployment fails.
Also tried the machine destory command but that failed aswell
Hi… As a quick tip, --exclude-machines from the command line is an effective workaround for the deployment aspect of this kind of problem, in many cases.
Also, there’s fly m destroy --force, if you haven’t tried that variant already.
-f, --force force kill machine regardless of current state
Hope this helps a little!
I have the same issue.
When I’m trying to run fly m destroy –force or fly scale count 0I get an error:
Error: could not destroy machine ——————: failed to destroy VM ——————: failed_precondition: unable to update machine to destroying
I scales it to 2 and the app is running, however, I can’t remove the machine in “replaced” state.
Can you please help me?
Hm, those are the two main tricks that I know of for this situation… Perhaps you could post the full output of fly m list?
(You can use the </> button in the toolbar to get an area suitable for pasting code, output, etc.)
In particular, do you see the daggers (†) from this other active forum thread?
https://community.fly.io/t/sjc-deployment-issues/26641/6
[If I remember correctly, that or an asterisk (*) indicates a failure of the underlying physical host machine(s), but I’m hunting for a reference…]
1 Like
Hey! Thanks for a quick response! Unfortunately only recreating the app from scratch helped.
Fortunately it was not hard.
For a future, I think what might be the issue is that I’ve had a polling mechanism on the server, which hit Telegram. I think this might caused the issue when I scaled the instances to 2 (just a guess)
1 Like
Hry all thought I would close the loop. spoke to support it is a bug they know about and have something in review to fix so they were able to manually remove for me .
just in case you have the error again
1 Like