INFO Main child exited normally with code: 1
INFO Starting clean up.
WARN hallpass exited, pid: 266, status: signal: 15 (SIGTERM)
2023/08/12 16:09:08 listening on [fdaa:2:a3ba:a7b:ea:153b:533c:2]:22 (DNS: [fdaa::3]:53)
[ 3.320330] reboot: Restarting system
machine restart policy set to ‘no’, not restarting
Error: release command failed - aborting deployment. error release_command machine e784ee62fd7658 exited with non-zero status of 1
app = “inspiring-db”
primary_region = “bos”
console_command = “/rails/bin/rails console”
release_command = “./bin/rails db:prepare”
internal_port = 3000
force_https = true
auto_stop_machines = true
auto_start_machines = true
min_machines_running = 0
processes = [“app”]
guest_path = “/rails/public”
url_prefix = “/”
Same here with my Elixir app hosted in LHR
We are getting this error during deployment of a
Phoenix App that was previously working.
2023/08/15 07:22:30 listening on [fdaa:0:78d4:a7b:173:9fb5:5989:2]:22
[ 2.316331] reboot: Restarting system
machine restart policy set to 'no', not restarting
Error: release command failed - aborting deployment.
error release_command machine 784e677f2265d8
exited with non-zero status of 1
fly.toml file. [snapshot]
Can’t seem to find anything in the docs for setting the “machine restart policy” in the config file.
Feels like this should be configured in the
fly.toml file …
Context: our App is auto-deployed by
Tried adding the
--restart on-fail flag to the
got the error:
Error: unknown flag: --restart
More detail: Chore: Error: release command failed - aborting deployment [Review Apps] · Issue #407 · dwyl/mvp · GitHub
Sadly this is a
Blocker for us. Please help!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.