My app keeps getting suspended

[rakinar2]

I’ve deployed a Discord bot on fly.io a long time ago. Today I had decided to migrate the app from v1 to v2. But as soon as I migrated the app, I ran into some trouble and deleted the whole app, and then recreated it. But now in each 10-15 mins it keeps getting “Supended” (The status changes to suspended, and all VMs stop). Then in about 5 minutes it restarts. But this downtime is not acceptable cause the bot may be failing to respond to commands during this time.

What is causing this issue and how can I fix this? Or possibly, how can I go back to v1?

[rakinar2]

Update: Running the troubleshoot command gave me this error

Also accessing the application page Sign In · Fly returns HTTP 500 Internal Server Error.

Also, I’ve noticed this in the logs:

Why is my app automatically downscaled?

[elephantshadow]

My app is also in suspended state, including the build machine. It sucks.

Suddenly suspended machine with SIGTERM signal shutting down

Hey there, My app is down for no obvious reason and can not bring it back up. It’s in “suspended” state. The logs indicate that a SIGTERM kill signal is sent during the start. Not sure what’s causing this, I haven’t deployed any change in past 2.5 weeks. Machine Id: 21781955a10e89 I’m not sure how to address this and it’s blocking me from demo’ing my app to customers tomorrow. Logs: 2023-07-09T09:17:42.673 app[21781955a10e89] dfw [info] [1686859.631179] reboot: Restarting system 2023-07-…

[pavel]

@rakinar2

Why is my app automatically downscaled?

Your app has auto_stop_machines and auto_start_machines set to true, which is the default for new V2 apps. With these settings, machines are downscaled when there are no incoming requests and started back when there are incoming requests.

If you also need to do some background processing in your app outside of incoming requests context, you may want to set them to false.

Automatically stop and start Machines