# Machine stuck in starting for ~15h after resume from suspend

**URL:** <https://community.fly.io/t/machine-stuck-in-starting-for-15h-after-resume-from-suspend/28766>\
**Category:** Questions / Help\
**Created:** [October 7, 2026, 12:16pm UTC](https://community.fly.io/t/machine-stuck-in-starting-for-15h-after-resume-from-suspend/28766 "2026-10-07T12:16:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rayko](https://avatars.discourse-cdn.com/v4/letter/r/a88e4f/32.png) [@rayko](https://community.fly.io/u/rayko)\
**Post date:** [October 7, 2026, 12:16pm UTC](https://community.fly.io/t/machine-stuck-in-starting-for-15h-after-resume-from-suspend/28766/1 "2026-10-07T12:16:36Z")

</div>

App `hla-law-app`, region `fra`, machine `784e1eefe2ee48` (single machine, `shared-cpu-1x`, 512 MB, volume `vol_r1jw5p5n7m1kme9r`). Config: `auto_stop_machines = "suspend"`, `min_machines_running = 0`.

Timeline (UTC, 2026-10-06):

- 20:47:40 proxy `cordon`, then `suspension` started
- 20:48:18 flyd: `suspended`
- 20:52:57 proxy `start` → machine entered `starting` and never left it

The machine stayed in `starting` until ~12:05 UTC on 2026-10-07. During that time, proxy logs showed repeated `machine failed to start, currently starting` and `rate limit exceeded`, then `could not find a good candidate within 40 attempts at load balancing`. All requests timed out.

Recovery attempts failed:

- `fly machine stop`: `unable to stop machine, current state invalid, starting` (Request ID `01M4B3X1M8V4N0JM2DCVHMGTHY-ams`)
- `fly machine start`: `machine failed to start, currently starting` (`01M4B3XZV5S13N3QZFA68D2JEM-ams`)
- `fly machine restart --force`: `internal: internal server error` (`01M4B3Y4G884M8G3X7DM0ZJPEA-ams`)

I had to destroy the machine and redeploy. There was no deploy or config change around the failure; the image had been running since 2026-09-24.

Questions: why did the resume hang, and why didn’t it fall back to a cold boot? Is suspend currently safe for a single-machine app with a volume?

---

<div class="post-metadata">

**Author:** ![flyio-support](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/flyio-support/32/46245_2.png) [@flyio-support](https://community.fly.io/u/flyio-support)\
**Post date:** [October 7, 2026, 1:24pm UTC](https://community.fly.io/t/machine-stuck-in-starting-for-15h-after-resume-from-suspend/28766/2 "2026-10-07T13:24:59Z")

</div>

Hi, falling back to a cold boot would only happen if the machine determines it cannot begin to resume. If it can, it will try but if the resume process gets stuck, then the machine will get stuck as you noticed. There’s nothing supervising the machine comes up: it’s a “try to resume” fire and forget kind of thing.

I checked and the actual reason appears to be that the host ran out of capacity for the machine, so a migration was queued and the machine moved to a new host. This should have resulted in a cold boot, but since the volume was being migrated too, there was a race between some of the operations which is what got the machine stuck. I’ll look into getting it fixed so this doesn’t happen again!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/fly1/original/3X/6/e/6e8955d00cb218e186ebbe3a6ab06fefdce15290.svg) [@system](https://community.fly.io/u/system)\
**Post date:** [October 17, 2026, 1:25pm UTC](https://community.fly.io/t/machine-stuck-in-starting-for-15h-after-resume-from-suspend/28766/3 "2026-10-17T13:25:53Z")

</div>

Closed on October 17, 2026, 1:25pm UTC

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