Can't deploy "Failed to update machines"

Questions / Help
1

I’m trying to redeploy an app I just created and whenever I do it just hangs periodically emitting messages like the ones below. I assume I borked something up but I have no idea how to figure out what it is. My app is just a simple Dockerfile based deployment that starts a node/express web server.

Watch your deployment at https://fly.io/apps/bhs-cs/monitoring

-------

Updating existing machines in '**bhs-cs**' with rolling strategy

Failed to update machines: failed to update machine 4d899539c1d998: failed to update VM 4d899539c1d998: request returned non-2xx status: 504: upstream request timeout Retrying... update VM 4d899539c1d998: request returned non-2xx status:…

Failed to update machines: failed to update machine 4d899539c1d998: failed to update VM 4d899539c1d998: request returned non-2xx status: 504: upstream request timeout Retrying... update VM 4d899539c1d998: request returned non-2xx status:…

Failed to update machines: failed to update machine 4d899539c1d998: failed to update VM 4d899539c1d998: request returned non-2xx status: 504: upstream request timeout Retrying... update VM 4d899539c1d998: request returned non-2xx status:…
2

A friend suggested the issue is that my service is failing its health check by not returning 200 OK. So I added this to my config.

[[http_service.checks]]
  grace_period = '10s'
  interval = '30s'
  method = 'GET'
  timeout = '5s'
  path = '/health'

which points to the server’s health check route. But I can’t see anywhere whether it’s actually trying to hit that. The “Live logs” at https://fly.io/apps/bhs-cs/monitoring just show “Waiting for logs …”

3

Well, it was just a long sequence of little things including some misconfiguration and maybe not building my Docker image the right way but I’ve powered through and got my thing running. Sorry for the noise.

1 Like
4

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