non-HTTP app never starts after remote deploy, can be manually started

I’ve got an app that does some internal database housekeeping, so exposes no http services. When I deploy a new version from Github actions it builds the image and pushes it, then times out waiting for it to start, meaning that I get an error and an email:

> Waiting for 3d8d342a1d7389 [app] to have state: started

The app only runs for a few tens of milliseconds every day (it’s a scheduled machine), and I can get the new machine id and run it using fly m start [id], which works fine.

Here’s my fly.toml:

# fly.toml app configuration file generated for userwipe on 2023-06-02T12:09:09+01:00
#
# See https://fly.io/docs/reference/configuration/ for information about how to use this file.
#

app = "userwipe"
primary_region = "fra"

processes = []

kill_signal = "SIGINT"
kill_timeout = "5s"

[experimental]
  auto_rollback = true
  allowed_public_ports = []

[build]
  dockerfile = "Dockerfile"

[env]
  RUST_LOG = "info"

deployed with `flyctl deploy --remote-only`

What am I missing here?

Switching my deploy strategy to immediate worked. This should be fine since there are no health checks to wait for and the machine runs for at most a couple of seconds per day.

1 Like

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