Fly log-shipper is always "suspended"

Questions / Help
1

I’m trying to set up the Fly log-shipper to send logs to Better Stack. I’ve tried following the instructions here: Better Stack Fly.io logging | Better Stack Documentation

No matter what I try, the machine is always in a suspended state.

Here’s my config:

primary_region = 'lax'

[build]
  image = 'flyio/log-shipper:latest'

[[services]]
  http_checks = []
  internal_port = 8686

[[vm]]
  memory = '1gb'
  cpus = 1
  memory_mb = 1024

I’ve also tried updating the services section like this:

[[services]]
  http_checks = []
  internal_port = 8686
  auto_start_machines = true
  auto_stop_machines = false
  min_machines_running = 1

Any help would be greatly appreciated!

2

“suspended” means the app has no machines running. This in turn suggests your machine is failing to start due to the app exiting early. Did you check fly logs for any clues as to what’s happening to the app?

  • Daniel
4

These are the only logs I’m seeing after a deploy:

2026-04-24T17:02:26Z runner[8635e5be65d768] lax [info]Pulling container image docker-hub-mirror.fly.io/flyio/log-shipper@sha256:72c7ff62b6871b86968650a67cec99d2b438b157b1da8f5bb365a8184dcaeeec
2026-04-24T17:02:26Z runner[8635e5be65d768] lax [info]Container image docker-hub-mirror.fly.io/flyio/log-shipper@sha256:72c7ff62b6871b86968650a67cec99d2b438b157b1da8f5bb365a8184dcaeeec already prepared
2026-04-24T17:02:27Z runner[8635e5be65d768] lax [info]Configuring firecracker
5

I’d try a fly m start at this point. Lately, flyctl has gotten a little stubborn about not attempting to start existing Machines after deploys…

6

That seems to have fixed it. Thanks!