Failed to start remote builder heartbeat: failed to create volume: App not found

,
1

Sometimes deployment fails and I have to force GitHub actions to re-run jobs to deploy. Plz can you fix this? Unstable deployment is what keeps me from using Fly.io for anything serious. Github Actions Logs:

Run flyctl deploy --remote-only
[6]==> Verifying app config
[7]Validating /home/runner/work/thinkfast/thinkfast/fly.toml
[8] ✓ Configuration is valid
[9]--> Verified app config
[10]==> Building image
[11] WARN Failed to start remote builder heartbeat: failed to create volume: App not found
[12]
[13] ==> Building image
[14]👀 checking remote builder compatibility with wireguardless deploys ...
[15] WARN Failed to start remote builder heartbeat: Get "http://fly-builder-bold-glade-6234.fly.dev/flyio/v1/settings": EOF
[16]
[17]
Error: failed to fetch an image or build from source: Get "http://fly-builder-bold-glade-6234.fly.dev/flyio/v1/settings": EOF
[18] Error: Process completed with exit code 1.
1 Like
2

So after a retry, it deployed, but then subsequent deploy failed with this:

 > Waiting for e286765db13686 [app] to become healthy: 0/2

[184]✖ Machine e286765db13686 [app] update failed: timeout reached waiting for health checks to pass for machine e286765db13686: failed to get VM e286765db13686: Get "https://api.machines.dev/v1/apps/thinkfast/machines/e286765db13686": net/http: request canceled

[185] Error: timeout reached waiting for health checks to pass for machine e286765db13686: failed to get VM e286765db13686: Get "https://api.machines.dev/v1/apps/thinkfast/machines/e286765db13686": net/http: request canceled
1 Like
3

I’ve been having massive deploy failures today as well.

@rubys any clue what’s going on?

4

Seeing the same thing here. :melting_face:

==> Verifying app config
Validating {{ directory }}/fly.toml
✓ Configuration is valid
--> Verified app config
==> Building image
WARN Remote builder did not start in time. Check remote builder logs with `flyctl logs -a fly-builder-wispy-night-4756`

WARN Failed to start remote builder heartbeat: remote builder app unavailable

==> Building image
WARN Failed to start remote builder heartbeat: failed to restart VM 3d8de92b154d58: failed_precondition: unable to restart machine, not currently started or stopped

Error: failed to fetch an image or build from source: failed to restart VM 3d8de92b154d58: failed_precondition: unable to restart machine, not currently started or stopped (Request ID: 01J3DZG6779CE46CRZEHSF0XVZ-ord) (Trace ID: eff7f1213555dd6274f64ab249015266)
5

I’m not personally seeing this, but enough people are that there are a team of people who have been working on this for several days; the first set of changes are queued up to be included in the flyctl release tomorrow.

6

Can you all share where you’re running your deployments from? These are all errors talking to the APIs, which could mean some kind of connectivity issue.

7

@robcarleski your errors were due to a host failure that affected your builder app. It should be resolved now, will you give it another try?

8

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