@scytale Since that region is lhr, it may be related to this:
I’m getting my requests timing out for an app that’s in three regions, but I’m closest to lhr so I guess my requests are always routed there. And failing.
It shows:
Deployment Status
Registry = registry.fly.io
Repository =
Tag = deployment-1646088842
Version = N/A
Digest = sha256:3430fd5f7a97313bc242a4ce16e2c77e39bc4b7e63cff3f82927113e82a211f8
The log is different now, and appears to be up, but still cannot connect to it, and the dashboard wont load either
@shaun Looks like the DB is back (upgraded it) and I can get to it externally. Now trying to work around the sea packet loss issue… we moved the app out of sea but that’s having issues, so guessing it will come good once the packet loss resolves. Thanks for the help!
$ flyctl image update --app production-db
? Update `production-db` from flyio/postgres:13.5 v0.0.9 to flyio/postgres:13.5 v0.0.16? Yes
Release v14 created
You can detach the terminal anytime without stopping the update
==> Monitoring deployment
2 desired, 1 placed, 0 healthy, 1 unhealthy [health checks: 3 total]
Failed Instances
Failure #1
Instance
ID PROCESS VERSION REGION DESIRED STATUS HEALTH CHECKS RESTARTCREATED
628d8681 14 iad run failed 3 total 0 20s ago
Recent Events
TIMESTAMP TYPE MESSAGE
2022-03-10T22:08:50Z Received Task received by client
2022-03-10T22:09:07Z Task Setup Building Task Directory
2022-03-10T22:09:09Z Started Task started by client
2022-03-10T22:09:11Z Terminated Exit Code: 2
2022-03-10T22:09:11Z Not Restarting Policy allows no restarts
2022-03-10T22:09:11Z Alloc Unhealthy Unhealthy because of failed task
2022-03-10T22:09:12Z Killing Sent interrupt. Waiting 5m0s before force killing
2022-03-10T22:09:07Z [info]Starting instance
2022-03-10T22:09:07Z [info]Configuring virtual machine
2022-03-10T22:09:07Z [info]Unpacking image
2022-03-10T22:09:08Z [info]Setting up volume 'pg_data'
2022-03-10T22:09:09Z [info]Configuring firecracker
2022-03-10T22:09:09Z [info]Starting virtual machine
2022-03-10T22:09:09Z [info]Starting init (commit: 0c50bff)...
2022-03-10T22:09:09Z [info]Preparing to run: `docker-entrypoint.sh start` as root
2022-03-10T22:09:09Z [info]2022/03/10 22:09:09 listening on [fdaa:0:309a:a7b:ab9:0:30e5:2]:22 (DNS: [fdaa::3]:53)
2022-03-10T22:09:10Z [info]Main child exited normally with code: 2
2022-03-10T22:09:10Z [info]Starting clean up.
2022-03-10T22:09:10Z [info]Umounting /dev/vdc from /data
--> v14 failed - Failed due to unhealthy allocations and deploying as v15
--> Troubleshooting guide at https://fly.io/docs/getting-started/troubleshooting/
Error abort
This should be good now, we’ve moved you off of an old etcd coordinator and on to a consul coordinator. It seems like the image upgrade made the etcd stuff not work properly.