Phoenix API Deployment Error - Logs not helpful

Questions / Help
, ,
1

Hi,

I am trying to deploy a Phoenix/Elixir app and keep getting this error:

Error: release command failed - aborting deployment. error release_command machine e2865129a7de68 exited with non-zero status of 1

Nothing in the logs gives me a hint about what is going on.

I am not sure if it is the problem, but this application has two databases attached.

Other info, this is the TOML file (It was autogenerated using fly launch:


app = "po2-sandbox"
primary_region = "mia"
kill_signal = "SIGTERM"
swap_size_mb = 512

[build]

[deploy]
  release_command = "/app/bin/migrate"

[env]
  PHX_HOST = "po2-sandbox.fly.dev"
  PORT = "8080"

[http_service]
  internal_port = 8080
  force_https = true
  auto_stop_machines = true
  auto_start_machines = true
  min_machines_running = 0
  processes = ["app"]
  [http_service.concurrency]
    type = "connections"
    hard_limit = 1000
    soft_limit = 1000

Logs:

2023-09-25T01:44:29Z runner[918575d1c12548] mia [info]Pulling container image registry.fly.io/po2-sandbox:deployment-01HB500JH9FVFEKNM9H58AJSBX
2023-09-25T01:44:47Z runner[918575d1c12548] mia [info]Successfully prepared image registry.fly.io/po2-sandbox:deployment-01HB500JH9FVFEKNM9H58AJSBX (17.657012738s)
2023-09-25T01:44:48Z runner[918575d1c12548] mia [info]Configuring firecracker
2023-09-25T01:44:48Z app[918575d1c12548] mia [info][    0.041546] PCI: Fatal: No config space access function found
2023-09-25T01:44:48Z app[918575d1c12548] mia [info] INFO Starting init (commit: 9fc6a62)...
2023-09-25T01:44:48Z app[918575d1c12548] mia [info] INFO Preparing to run: `/app/bin/migrate` as nobody
2023-09-25T01:44:48Z app[918575d1c12548] mia [info] INFO [fly api proxy] listening at /.fly/api
2023-09-25T01:44:48Z app[918575d1c12548] mia [info]2023/09/25 01:44:48 listening on [fdaa:0:ac7d:a7b:184:f13:ea21:2]:22 (DNS: [fdaa::3]:53)
2023-09-25T01:44:49Z app[918575d1c12548] mia [info]** (EXIT from #PID<0.95.0>) shutdown
2023-09-25T01:44:49Z app[918575d1c12548] mia [info] INFO Main child exited normally with code: 1
2023-09-25T01:44:49Z app[918575d1c12548] mia [info] INFO Starting clean up.
2023-09-25T01:44:49Z app[918575d1c12548] mia [info] WARN hallpass exited, pid: 315, status: signal: 15 (SIGTERM)
2023-09-25T01:44:49Z app[918575d1c12548] mia [info]2023/09/25 01:44:49 listening on [fdaa:0:ac7d:a7b:184:f13:ea21:2]:22 (DNS: [fdaa::3]:53)
2023-09-25T01:44:50Z app[918575d1c12548] mia [info][    2.321652] reboot: Restarting system
2023-09-25T01:44:50Z runner[918575d1c12548] mia [info]machine restart policy set to 'no', not restarting

Any help finding better info in logs will be greatly appreciated.

Andrew

2

I’m getting the same error with an application that has no database at all. The logs really don’t explain what’s going on at all.

$ fly logs -a foxesss

Waiting for logs...

2023-09-30T13:29:40.375 runner[9185933a542558] ams [info] Pulling container image registry.fly.io/foxesss:deployment-01HBK4AAVJJ4F692YXDPWR0V3Z

2023-09-30T13:29:42.755 runner[9185933a542558] ams [info] Successfully prepared image registry.fly.io/foxesss:deployment-01HBK4AAVJJ4F692YXDPWR0V3Z (2.380439665s)

2023-09-30T13:29:43.796 runner[9185933a542558] ams [info] Configuring firecracker

2023-09-30T13:29:43.932 app[9185933a542558] ams [info] [ 0.036354] PCI: Fatal: No config space access function found

2023-09-30T13:29:44.132 app[9185933a542558] ams [info] INFO Starting init (commit: 5d9c42f)...

2023-09-30T13:29:44.197 app[9185933a542558] ams [info] INFO Preparing to run: `/app/bin/migrate` as nobody

2023-09-30T13:29:44.203 app[9185933a542558] ams [info] INFO [fly api proxy] listening at /.fly/api

2023-09-30T13:29:44.209 app[9185933a542558] ams [info] 2023/09/30 13:29:44 listening on [fdaa:3:2b71:a7b:a356:741d:e607:2]:22 (DNS: [fdaa::3]:53)

2023-09-30T13:29:44.831 app[9185933a542558] ams [info] ** (EXIT from #PID<0.98.0>) shutdown

2023-09-30T13:29:45.204 app[9185933a542558] ams [info] INFO Main child exited normally with code: 1

2023-09-30T13:29:45.204 app[9185933a542558] ams [info] INFO Starting clean up.

2023-09-30T13:29:45.205 app[9185933a542558] ams [info] WARN hallpass exited, pid: 315, status: signal: 15 (SIGTERM)

2023-09-30T13:29:45.208 app[9185933a542558] ams [info] 2023/09/30 13:29:45 listening on [fdaa:3:2b71:a7b:a356:741d:e607:2]:22 (DNS: [fdaa::3]:53)

2023-09-30T13:29:46.206 app[9185933a542558] ams [info] [ 2.309173] reboot: Restarting system

2023-09-30T13:29:46.305 runner[9185933a542558] ams [info] machine restart policy set to 'no', not restarting
3

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