Hi there! I received an email notification stating that my apps will be upgraded to the new apps v2 machines next week. To ensure a smooth transition, I decided to upgrade one of my apps this week and verify that everything is working properly.
Unfortunately, I am currently facing an issue with the “auto_stop_machines” feature, which is supposed to downscale my machines when traffic is lower. Upon reviewing the logs, I noticed that Fly attempts to downscale one of my apps, sends the signal, but immediately logs “Virtual machine exited abruptly.” As a result, my graceful shutdown scripts are not being executed. It seems like the machine restarts immediately after the abrupt exit, I’m assuming it considers it as crashed. This cycle repeats, keeping my machines at a count of 2 instead of downsizing them to 1 as intended, and preventing me from benefiting of autoscaling them.
I have the
kill_signal to “SIGINT” and the
kill_timeout to “5” set in my config file. I’ve also experimented by removing the
min_machines_running parameter or modifying the app’s regions, but Fly continues to fail in downgrading the machines.
flyctl machine stop <id> also abruptly exits the machine.
I’m unsure about the cause of this issue. Previously, everything was functioning correctly with Nomad, and my graceful shutdown scripts were executed without any issues. Local testing also works fine. Could there be an issue on Fly’s end? Or is it possible that there is a misconfiguration on my part?