timeout reached waiting for machine to started failed

Questions / Help
1

hi i always got this timeout

# fly.toml app configuration file generated for summer-sound-6337 on 2023-08-21T17:17:03+07:00
#
# See https://fly.io/docs/reference/configuration/ for information about how to use this file.
#

app = "summer-sound-6337"
primary_region = "sin"

[build]
  dockerfile = "dev.dockerfile"

[deploy]
  release_command = "python manage.py migrate"

[processes]
  app = "gunicorn config.wsgi --bind=0.0.0.0:8000  --workers=2 --threads=2 --worker-class=gthread --log-level=debug --worker-tmp-dir=/dev/shm --chdir=/app"
  worker = "celery -A config.celery_app worker --concurrency=5 --loglevel=ERROR --loglevel=INFO --loglevel=DEBUG --pidfile=/tmp/celeryworker.pid"
  flower = "celery -A config.celery_app flower --port=5751"
  beat = "celery -A config.celery_app beat --loglevel=ERROR --loglevel=INFO --loglevel=DEBUG --pidfile=/tmp/celerybeatprocess.pid"
  cronjob = "supercronic /app/crontab"

[http_service]
  internal_port = 8000
  force_https = true
  auto_stop_machines = false
  auto_start_machines = true
  min_machines_running = 1
  processes = ["app"]

[[services]]
  internal_port = 5751
  protocol = "tcp"
  auto_stop_machines = true
  auto_start_machines = true
  min_machines_running = 0
  processes = ["flower"]


Updating existing machines in '**summer-sound-6337**' with rolling strategy

-------

⠧ [1/5] Waiting for **148e435b340789 [cronjob]** to have state: started

[2/5] Waiting for job

[3/5] Waiting for job

[4/5] Waiting for job

[5/5] Waiting for job

-------

Error: timeout reached waiting for machine to started failed to wait for VM 148e435b340789 in started state: Get "https://api.machines.dev/v1/apps/summer-sound-6337/machines/148e435b340789/wait?instance_id=01HCCNM5XBC295S9W9ZJ2SFTEW&state=started&timeout=60": net/http: request canceled

You can increase the timeout with the --wait-timeout flag

any solution?

2

We have the same issue on a v2 machine.

Error: failed to update VM 148e276f312ed8: request returned non-2xx status, 504 (Request ID: 01HCCXCRKNWQH8Q6J92GAXN6VV-arn)

We’ve tried to increase the wait timeout to two minutes, but that didn’t help. Running the latest version of flyctl.

3

Same for us on V2 machines

4

Hi :wave:,
Same issue for us since yesterday, impossible to deploy.

Using V2 machines

Error: failed to update VM 3d8d31db1e19d8: request returned non-2xx status, 504 (Request ID: 01HCESJGX1YV1EK6K0Y23WDJMS-sin)

Every 2-3 retry we got this error that coming

Error: failed to fetch an image or build from source: error rendering push status stream: received unexpected HTTP status: 502 Bad Gateway
5

same issue deploy hangs up

6

yeah, same issue happen to me as well.

I tried to destroy all machine and launch a new one also return the same result

Error: timeout reached waiting for machine to started failed to wait for VM 3d8d34df15d689 in started state
8

I can’t even create a new app, I’m getting this error when running fly launch and selecting any region:
Error: server returned a non-200 status code: 500

1 Like
9

We had a bad deploy about 20 minutes ago that was quickly reverted. You should not have any issues now.

10

Sadly not, still can’t launch an app – always 500. I also upgraded the fly CLI, but same problem.

11

Yea, sorry about that. We’re actively working to recover the deploy.

1 Like
12

Facing the same issue

Error: server returned a non-200 status code: 500

While running fly launch

13

Thanks, it’s working now! :slight_smile:

1 Like
14

Well, the remote builder is failing now :sweat_smile: I will wait a bit longer then

15

Also facing this issue. Increasing the timeout did not make a difference.

With bluegreen deployment:
Deployment failed after error: could not get all green machines into started state: wait timeout
Error: could not get all green machines into started state: wait timeout

With canary:
Error: timeout reached waiting for machine to started failed to wait for VM in started state

16

Thanks! It’s working now

17

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