All our phoenix apps are suspended. start 43 minutes ago. the db servers are still up.
We tried restarting:
$ fly apps restart lyn-pay
Restarting machine 18579eda435778
Error: could not stop machine 18579eda435778: failed to restart VM 18579eda435778: internal: internal server error (Request ID: 01HV8EKW05MPDG72JJBT8P9EW2-fra)
We also tried redeploying:
$ fly deploy -c prod.fly.toml
==> Verifying app config
Validating prod.fly.toml
✓ Configuration is valid
--> Verified app config
==> Building image
WARN Remote builder did not start in time. Check remote builder logs with `flyctl logs -a fly-builder-falling-thunder-5451`
WARN Failed to start remote builder heartbeat: remote builder app unavailable
WARN Remote builder did not start in time. Check remote builder logs with `flyctl logs -a fly-builder-falling-thunder-5451`
Error: failed to fetch an image or build from source: error connecting to docker: remote builder app unavailable
Seeing something similar on my machines. App server went down and I can’t restart them. Here’s the message I’m getting on fly apps restart.
Error: could not stop machine e784927a630738: failed to restart VM e784927a630738: unknown: failed to compare "/opt/firecracker-v0.24.x/bin/firecracker" and "/opt/flyd/firefly/01HV3EC3HVV5J2GRBMVE2TPSRH/root/firecracker": stat /opt/firecracker-v0.24.x/bin/firecracker: no such file or directory (Request ID: 01HV8F8PFQHPAZWRJEBXA3JGPA-jnb)
Same for me. The status page showed “A fix has been implemented…” but didn’t seem to be working.
2024-04-12T06:36:14.412 proxy[918571d0a924d8] hkg [error] timed out while connecting to your instance. this indicates a problem with your app (hint: look at your logs and metrics)
2024-04-12T06:36:18.476 proxy[918571d0a924d8] hkg [error] timed out while connecting to your instance. this indicates a problem with your app (hint: look at your logs and metrics)
2024-04-12T06:36:22.517 proxy[918571d0a924d8] hkg [error] timed out while connecting to your instance. this indicates a problem with your app (hint: look at your logs and metrics)
Also facing an issue. My app went down and i am unable to get a machine to start. Seeing this in the logs:
2024-04-12T06:39:06Z runner[080e091f650218] sin [info]Configuring firecracker
2024-04-12T06:39:07Z app[080e091f650218] sin [info][ 0.070891] PCI: Fatal: No config space access function found
2024-04-12T06:39:07Z app[080e091f650218] sin [info] INFO Starting init (commit: 5b8fb02)...
2024-04-12T06:39:07Z app[080e091f650218] sin [info] INFO Preparing to run: `/app/bin/server` as nobody
2024-04-12T06:39:07Z app[080e091f650218] sin [info] INFO [fly api proxy] listening at /.fly/api
2024-04-12T06:39:07Z app[080e091f650218] sin [info]2024/04/12 06:39:07 listening on [fdaa:0:4d47:a7b:185:eaf5:5fd:2]:22 (DNS: [fdaa::3]:53)
2024-04-12T06:39:07Z runner[080e091f650218] sin [info]Machine created and started in 4.47s
2024-04-12T06:39:12Z app[080e091f650218] sin [info]Protocol 'inet6_tcp': invalid node name: reggu-prod-prod@sha256:3e1793d3272cef58b31c512fd85176f33e2f4610bb7176373525235a0ab586e3@fdaa:0:4d47:a7b:185:eaf5:5fd:2
2024-04-12T06:39:12Z app[080e091f650218] sin [info][ 5.543704] reboot: Restarting system
2024-04-12T06:39:13Z runner[080e091f650218] sin [info]machine did not have a restart policy, defaulting to restart
2024-04-12T06:39:13Z app[080e091f650218] sin [info][ 0.078333] PCI: Fatal: No config space access function found
2024-04-12T06:39:14Z app[080e091f650218] sin [info] INFO Starting init (commit: 5b8fb02)...
2024-04-12T06:39:14Z app[080e091f650218] sin [info] INFO Preparing to run: `/app/bin/server` as nobody
2024-04-12T06:39:14Z app[080e091f650218] sin [info] INFO [fly api proxy] listening at /.fly/api
2024-04-12T06:39:14Z runner[080e091f650218] sin [info]Machine started in 777ms
2024-04-12T06:39:18Z app[080e091f650218] sin [info]Protocol 'inet6_tcp': invalid node name: reggu-prod-prod@sha256:3e1793d3272cef58b31c512fd85176f33e2f4610bb7176373525235a0ab586e3@fdaa:0:4d47:a7b:185:eaf5:5fd:2
2024-04-12T06:39:19Z app[080e091f650218] sin [info] INFO Main child exited normally with code: 1
2024-04-12T06:39:19Z app[080e091f650218] sin [info] WARN Reaped child process with pid: 363 and signal: SIGUSR1, core dumped? false
2024-04-12T06:39:19Z app[080e091f650218] sin [info] INFO Starting clean up.
2024-04-12T06:39:19Z app[080e091f650218] sin [info][ 5.591877] reboot: Restarting system
2024-04-12T06:39:19Z runner[080e091f650218] sin [info]machine did not have a restart policy, defaulting to restart
2024-04-12T06:39:19Z app[080e091f650218] sin [info][ 0.068293] PCI: Fatal: No config space access function found
2024-04-12T06:39:20Z app[080e091f650218] sin [info] INFO Starting init (commit: 5b8fb02)...
2024-04-12T06:39:20Z app[080e091f650218] sin [info] INFO Preparing to run: `/app/bin/server` as nobody
2024-04-12T06:39:20Z app[080e091f650218] sin [info] INFO [fly api proxy] listening at /.fly/api
2024-04-12T06:39:20Z app[080e091f650218] sin [info]2024/04/12 06:39:20 listening on [fdaa:0:4d47:a7b:185:eaf5:5fd:2]:22 (DNS: [fdaa::3]:53)
2024-04-12T06:39:20Z runner[080e091f650218] sin [info]Machine started in 722ms
2024-04-12T06:39:24Z app[080e091f650218] sin [info]Protocol 'inet6_tcp': invalid node name: reggu-prod-prod@sha256:3e1793d3272cef58b31c512fd85176f33e2f4610bb7176373525235a0ab586e3@fdaa:0:4d47:a7b:185:eaf5:5fd:2
2024-04-12T06:39:25Z app[080e091f650218] sin [info] INFO Main child exited normally with code: 1
2024-04-12T06:39:25Z app[080e091f650218] sin [info] WARN Reaped child process with pid: 363 and signal: SIGUSR1, core dumped? false
2024-04-12T06:39:25Z app[080e091f650218] sin [info] INFO Starting clean up.
I have tried restarting existing machines and creating new machines. Have been trying repeatedly since the status page said the fix has been deployed.
Hey @smarties and @Ziwen. Looks like your machines got stuck in an invalid state. Can you please try force destroying them and re-creating them if possible?
My app suddenly went down with this incident and i cannot get a machine to successfully start again.
Machine stuck in a stopped state
fly machines list
1 machines have been retrieved from app reggu-prod.
View them in the UI here (https://fly.io/apps/reggu-prod/machines/)
reggu-prod
ID NAME STATE REGION IMAGE IP ADDRESS VOLUME CREATED LAST UPDATED APP PLATFORM PROCESS GROUP SIZE
683d610a716418 cold-violet-4297 stopped sin reggu-prod: fdaa:0:4d47:a7b:185:c50b:a577:2 2024-04-12T06:43:08Z 2024-04-12T06:44:16Z v2 app shared-cpu-1x:1024MB
I force destroy it
fly machines destroy 683d610a716418 --force
machine 683d610a716418 was found and is currently in stopped state, attempting to destroy...
683d610a716418 has been destroyed
Create a new machine
fly scale count 1 --region sin
App 'reggu-prod' is going to be scaled according to this plan:
+1 machines for group 'app' on region 'sin' of size 'shared-cpu-1x'
? Scale app reggu-prod? Yes
Executing scale plan
Created 48ed192a71ded8 group:app region:sin size:shared-cpu-1x
Machine fails to start repeatedly.
2024-04-12T06:45:01Z runner[48ed192a71ded8] sin [info]Successfully prepared image registry.fly.io/reggu-prod@sha256:3e1793d3272cef58b31c512fd85176f33e2f4610bb7176373525235a0ab586e3 (2.970973845s)
2024-04-12T06:45:02Z runner[48ed192a71ded8] sin [info]Configuring firecracker
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info][ 0.077384] PCI: Fatal: No config space access function found
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info] INFO Starting init (commit: 5b8fb02)...
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info] INFO Preparing to run: `/app/bin/server` as nobody
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info] INFO [fly api proxy] listening at /.fly/api
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info]2024/04/12 06:45:03 listening on [fdaa:0:4d47:a7b:185:c1c6:c461:2]:22 (DNS: [fdaa::3]:53)
2024-04-12T06:45:03Z runner[48ed192a71ded8] sin [info]Machine created and started in 4.627s
2024-04-12T06:45:07Z app[48ed192a71ded8] sin [info]Protocol 'inet6_tcp': invalid node name: reggu-prod-prod@sha256:3e1793d3272cef58b31c512fd85176f33e2f4610bb7176373525235a0ab586e3@fdaa:0:4d47:a7b:185:c1c6:c461:2
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info] INFO Main child exited normally with code: 1
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info] WARN Reaped child process with pid: 363 and signal: SIGUSR1, core dumped? false
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info] INFO Starting clean up.
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info][ 5.532757] reboot: Restarting system
2024-04-12T06:45:08Z runner[48ed192a71ded8] sin [info]machine did not have a restart policy, defaulting to restart
My app went down with this incident too and i cannot get machines up again.
I created a machine and it is stuck in a stopped state
fly machines list
1 machines have been retrieved from app reggu-prod.
View them in the UI here (https://fly.io/apps/reggu-prod/machines/)
reggu-prod
ID NAME STATE REGION IMAGE IP ADDRESS VOLUME CREATED LAST UPDATED APP PLATFORM PROCESS GROUP SIZE
683d610a716418 cold-violet-4297 stopped sin reggu-prod: fdaa:0:4d47:a7b:185:c50b:a577:2 2024-04-12T06:43:08Z 2024-04-12T06:44:16Z v2 app shared-cpu-1x:1024MB
So I destroy the machine
fly machines destroy 683d610a716418 --force
machine 683d610a716418 was found and is currently in stopped state, attempting to destroy...
683d610a716418 has been destroyed
Create a new machine
fly scale count 1 --region sin
App 'reggu-prod' is going to be scaled according to this plan:
+1 machines for group 'app' on region 'sin' of size 'shared-cpu-1x'
? Scale app reggu-prod? Yes
Executing scale plan
Created 48ed192a71ded8 group:app region:sin size:shared-cpu-1x
Then the machine fails to start repeatedly.
2024-04-12T06:45:01Z runner[48ed192a71ded8] sin [info]Successfully prepared image registry.fly.io/reggu-prod@sha256:3e1793d3272cef58b31c512fd85176f33e2f4610bb7176373525235a0ab586e3 (2.970973845s)
2024-04-12T06:45:02Z runner[48ed192a71ded8] sin [info]Configuring firecracker
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info][ 0.077384] PCI: Fatal: No config space access function found
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info] INFO Starting init (commit: 5b8fb02)...
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info] INFO Preparing to run: `/app/bin/server` as nobody
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info] INFO [fly api proxy] listening at /.fly/api
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info]2024/04/12 06:45:03 listening on [fdaa:0:4d47:a7b:185:c1c6:c461:2]:22 (DNS: [fdaa::3]:53)
2024-04-12T06:45:03Z runner[48ed192a71ded8] sin [info]Machine created and started in 4.627s
2024-04-12T06:45:07Z app[48ed192a71ded8] sin [info]Protocol 'inet6_tcp': invalid node name: reggu-prod-prod@sha256:3e1793d3272cef58b31c512fd85176f33e2f4610bb7176373525235a0ab586e3@fdaa:0:4d47:a7b:185:c1c6:c461:2
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info] INFO Main child exited normally with code: 1
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info] WARN Reaped child process with pid: 363 and signal: SIGUSR1, core dumped? false
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info] INFO Starting clean up.
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info][ 5.532757] reboot: Restarting system
2024-04-12T06:45:08Z runner[48ed192a71ded8] sin [info]machine did not have a restart policy, defaulting to restart
2024-04-12T06:45:09Z app[48ed192a71ded8] sin [info][ 0.066917] PCI: Fatal: No config space access function found
2024-04-12T06:45:09Z app[48ed192a71ded8] sin [info] INFO Starting init (commit: 5b8fb02)...
2024-04-12T06:45:09Z app[48ed192a71ded8] sin [info] INFO Preparing to run: `/app/bin/server` as nobody
2024-04-12T06:45:09Z app[48ed192a71ded8] sin [info] INFO [fly api proxy] listening at /.fly/api
2024-04-12T06:45:09Z runner[48ed192a71ded8] sin [info]Machine started in 702ms
flyd m destroy --force <your machine id> and then starting a machine on your app as usual. The issue was caused due to a bad configuration being deployed on some workers. We rolled back the configuration change, but some machines got stuck in an invalid state. We are sorry for the inconvenience caused.
My app went down with this incident too and i cannot get machines up again.
I created a machine and it is stuck in a stopped state
fly machines list
1 machines have been retrieved from app reggu-prod.
View them in the UI here (https://fly.io/apps/reggu-prod/machines/)
reggu-prod
ID NAME STATE REGION IMAGE IP ADDRESS VOLUME CREATED LAST UPDATED APP PLATFORM PROCESS GROUP SIZE
683d610a716418 cold-violet-4297 stopped sin reggu-prod: fdaa:0:4d47:a7b:185:c50b:a577:2 2024-04-12T06:43:08Z 2024-04-12T06:44:16Z v2 app shared-cpu-1x:1024MB
So I destroy the machine
fly machines destroy 683d610a716418 --force
machine 683d610a716418 was found and is currently in stopped state, attempting to destroy...
683d610a716418 has been destroyed
Create a new machine
fly scale count 1 --region sin
App 'reggu-prod' is going to be scaled according to this plan:
+1 machines for group 'app' on region 'sin' of size 'shared-cpu-1x'
? Scale app reggu-prod? Yes
Executing scale plan
Created 48ed192a71ded8 group:app region:sin size:shared-cpu-1x
Then the machine fails to start repeatedly.
2024-04-12T06:45:01Z runner[48ed192a71ded8] sin [info]Successfully prepared image registry.fly.io/reggu-prod@sha256:3e1793d3272cef58b31c512fd85176f33e2f4610bb7176373525235a0ab586e3 (2.970973845s)
2024-04-12T06:45:02Z runner[48ed192a71ded8] sin [info]Configuring firecracker
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info][ 0.077384] PCI: Fatal: No config space access function found
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info] INFO Starting init (commit: 5b8fb02)...
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info] INFO Preparing to run: `/app/bin/server` as nobody
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info] INFO [fly api proxy] listening at /.fly/api
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info]2024/04/12 06:45:03 listening on [fdaa:0:4d47:a7b:185:c1c6:c461:2]:22 (DNS: [fdaa::3]:53)
2024-04-12T06:45:03Z runner[48ed192a71ded8] sin [info]Machine created and started in 4.627s
2024-04-12T06:45:07Z app[48ed192a71ded8] sin [info]Protocol 'inet6_tcp': invalid node name: reggu-prod-prod@sha256:3e1793d3272cef58b31c512fd85176f33e2f4610bb7176373525235a0ab586e3@fdaa:0:4d47:a7b:185:c1c6:c461:2
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info] INFO Main child exited normally with code: 1
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info] WARN Reaped child process with pid: 363 and signal: SIGUSR1, core dumped? false
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info] INFO Starting clean up.
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info][ 5.532757] reboot: Restarting system
2024-04-12T06:45:08Z runner[48ed192a71ded8] sin [info]machine did not have a restart policy, defaulting to restart
2024-04-12T06:45:09Z app[48ed192a71ded8] sin [info][ 0.066917] PCI: Fatal: No config space access function found
2024-04-12T06:45:09Z app[48ed192a71ded8] sin [info] INFO Starting init (commit: 5b8fb02)...
2024-04-12T06:45:09Z app[48ed192a71ded8] sin [info] INFO Preparing to run: `/app/bin/server` as nobody
2024-04-12T06:45:09Z app[48ed192a71ded8] sin [info] INFO [fly api proxy] listening at /.fly/api
2024-04-12T06:45:09Z runner[48ed192a71ded8] sin [info]Machine started in 702ms
$ fly m destroy --force 784e935f435378
machine 784e935f435378 was found and is currently in starting state, attempting to destroy...
784e935f435378 has been destroyed
But how do we start them again?
restart command still doesn’t work:
$ fly apps restart lyn-pay
Restarting machine 18579eda435778
Error: could not stop machine 18579eda435778: failed to restart VM 18579eda435778: failed_precondition: unable to restart machine, not currently started or stopped (Request ID: 01HV8HTP2Y11T8R5HGFHBRHX83-fra)
I am still having an issue getting machines to start and my app is fully down. I have tried force deleting machines and starting new ones. None actually start and I am seeing this restart loop in the logs:
2024-04-12T07:02:10Z runner[185716eb427568] sin [info]Machine started in 770ms
2024-04-12T07:02:10Z app[185716eb427568] sin [info]2024/04/12 07:02:10 listening on [fdaa:0:4d47:a7b:185:6d4d:9726:2]:22 (DNS: [fdaa::3]:53)
2024-04-12T07:02:14Z app[185716eb427568] sin [info]Protocol 'inet6_tcp': invalid node name: reggu-prod-prod@sha256:3e1793d3272cef58b31c512fd85176f33e2f4610bb7176373525235a0ab586e3@fdaa:0:4d47:a7b:185:6d4d:9726:2
2024-04-12T07:02:15Z app[185716eb427568] sin [info] INFO Main child exited normally with code: 1
2024-04-12T07:02:15Z app[185716eb427568] sin [info] WARN Reaped child process with pid: 363 and signal: SIGUSR1, core dumped? false
2024-04-12T07:02:15Z app[185716eb427568] sin [info] INFO Starting clean up.
2024-04-12T07:02:15Z app[185716eb427568] sin [info][ 5.587404] reboot: Restarting system
My app went down with this incident too and i cannot get machines up again.
I created a machine and it is stuck in a stopped state
fly machines list
1 machines have been retrieved from app reggu-prod.
View them in the UI here (https://fly.io/apps/reggu-prod/machines/)
reggu-prod
ID NAME STATE REGION IMAGE IP ADDRESS VOLUME CREATED LAST UPDATED APP PLATFORM PROCESS GROUP SIZE
683d610a716418 cold-violet-4297 stopped sin reggu-prod: fdaa:0:4d47:a7b:185:c50b:a577:2 2024-04-12T06:43:08Z 2024-04-12T06:44:16Z v2 app shared-cpu-1x:1024MB
So I destroy the machine
fly machines destroy 683d610a716418 --force
machine 683d610a716418 was found and is currently in stopped state, attempting to destroy...
683d610a716418 has been destroyed
Create a new machine
fly scale count 1 --region sin
App 'reggu-prod' is going to be scaled according to this plan:
+1 machines for group 'app' on region 'sin' of size 'shared-cpu-1x'
? Scale app reggu-prod? Yes
Executing scale plan
Created 48ed192a71ded8 group:app region:sin size:shared-cpu-1x
Then the machine fails to start repeatedly.
2024-04-12T06:45:01Z runner[48ed192a71ded8] sin [info]Successfully prepared image registry.fly.io/reggu-prod@sha256:3e1793d3272cef58b31c512fd85176f33e2f4610bb7176373525235a0ab586e3 (2.970973845s)
2024-04-12T06:45:02Z runner[48ed192a71ded8] sin [info]Configuring firecracker
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info][ 0.077384] PCI: Fatal: No config space access function found
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info] INFO Starting init (commit: 5b8fb02)...
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info] INFO Preparing to run: `/app/bin/server` as nobody
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info] INFO [fly api proxy] listening at /.fly/api
2024-04-12T06:45:03Z app[48ed192a71ded8] sin [info]2024/04/12 06:45:03 listening on [fdaa:0:4d47:a7b:185:c1c6:c461:2]:22 (DNS: [fdaa::3]:53)
2024-04-12T06:45:03Z runner[48ed192a71ded8] sin [info]Machine created and started in 4.627s
2024-04-12T06:45:07Z app[48ed192a71ded8] sin [info]Protocol 'inet6_tcp': invalid node name: reggu-prod-prod@sha256:3e1793d3272cef58b31c512fd85176f33e2f4610bb7176373525235a0ab586e3@fdaa:0:4d47:a7b:185:c1c6:c461:2
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info] INFO Main child exited normally with code: 1
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info] WARN Reaped child process with pid: 363 and signal: SIGUSR1, core dumped? false
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info] INFO Starting clean up.
2024-04-12T06:45:08Z app[48ed192a71ded8] sin [info][ 5.532757] reboot: Restarting system
2024-04-12T06:45:08Z runner[48ed192a71ded8] sin [info]machine did not have a restart policy, defaulting to restart
2024-04-12T06:45:09Z app[48ed192a71ded8] sin [info][ 0.066917] PCI: Fatal: No config space access function found
2024-04-12T06:45:09Z app[48ed192a71ded8] sin [info] INFO Starting init (commit: 5b8fb02)...
2024-04-12T06:45:09Z app[48ed192a71ded8] sin [info] INFO Preparing to run: `/app/bin/server` as nobody
2024-04-12T06:45:09Z app[48ed192a71ded8] sin [info] INFO [fly api proxy] listening at /.fly/api
2024-04-12T06:45:09Z runner[48ed192a71ded8] sin [info]Machine started in 702ms
@smarties18579eda435778 was the machine that was in the bad state. You can destroy that one and bring up more machines first in your preferred region using fly scale -r <region> count <number of machines you want>.
@xwiles looks like your machine 48ed192a71ded8 was destroyed. Can you try to scale up again, and let me know if it solves the issue.
I have repeated the process described and I am still having the issue.
The new machine id is 78113d5f9420d8 and I am still seeing a restart loop (logs below). I will keep this machine around
2024-04-12T07:11:15Z runner[78113d5f9420d8] sin [info]machine did not have a restart policy, defaulting to restart
2024-04-12T07:11:16Z app[78113d5f9420d8] sin [info][ 0.066774] PCI: Fatal: No config space access function found
2024-04-12T07:11:16Z app[78113d5f9420d8] sin [info] INFO Starting init (commit: 5b8fb02)...
2024-04-12T07:11:16Z app[78113d5f9420d8] sin [info] INFO Preparing to run: `/app/bin/server` as nobody
2024-04-12T07:11:16Z app[78113d5f9420d8] sin [info] INFO [fly api proxy] listening at /.fly/api
2024-04-12T07:11:16Z app[78113d5f9420d8] sin [info]2024/04/12 07:11:16 listening on [fdaa:0:4d47:a7b:185:6577:c25b:2]:22 (DNS: [fdaa::3]:53)
2024-04-12T07:11:16Z runner[78113d5f9420d8] sin [info]Machine started in 749ms
2024-04-12T07:11:21Z app[78113d5f9420d8] sin [info]Protocol 'inet6_tcp': invalid node name: reggu-prod-prod@sha256:3e1793d3272cef58b31c512fd85176f33e2f4610bb7176373525235a0ab586e3@fdaa:0:4d47:a7b:185:6577:c25b:2
2024-04-12T07:11:21Z app[78113d5f9420d8] sin [info] INFO Main child exited normally with code: 1
2024-04-12T07:11:21Z app[78113d5f9420d8] sin [info] WARN Reaped child process with pid: 363 and signal: SIGUSR1, core dumped? false
2024-04-12T07:11:21Z app[78113d5f9420d8] sin [info] INFO Starting clean up.
2024-04-12T07:11:21Z app[78113d5f9420d8] sin [info][ 5.515875] reboot: Restarting system
2024-04-12T07:11:22Z runner[78113d5f9420d8] sin [info]machine did not have a restart policy, defaulting to restart
2024-04-12T07:11:22Z app[78113d5f9420d8] sin [info][ 0.073521] PCI: Fatal: No config space access function found