Deploy error - Failed due to unhealthy allocations

Questions / Help
1

Hi,

I’m having trouble deploying, even though I have successfully deployed with this same configuration +100 times prior to this. I have seen this error a couple of times before, but it has resolved itself after trying again, or I have fixed it by altering regions. But this time nothing seems to work, I’m stuck. So I need help to fix whatever is wrong.

My app’s name is “siddler”, and the error is:

v125 is being deployed
c2243102: fra pending
c2243102: fra pending
c2243102: fra running unhealthy [health checks: 1 total]
c2243102: fra pending
c2243102: fra pending
c2243102: fra pending
c2243102: fra pending
v125 failed - Failed due to unhealthy allocations - not rolling back to stable job version 125 as current job has same specification
Failed Instances

Would appreciate any help. Thanks!

2

Seems like this one is related.

3

It appears the VMs have been crashing on deploy.

If you run fly status -a siddler --all you can see the failed instances. Then run fly logs -a siddler -i <id> to get logs for one of them, here’s what I see:

2021-10-18T09:54:28.689 app[4989544c] fra [info]  FATAL  Cannot resolve "~/api/startingPoints.js" from "/usr/src/app/api/startingPoints.js"
2021-10-18T09:54:28.689 app[4989544c] fra [info]   at Resolver.resolvePath (node_modules/@nuxt/core/dist/core.js:347:11)
2021-10-18T09:54:28.689 app[4989544c] fra [info]   at Server._requireMiddleware (node_modules/@nuxt/server/dist/server.js:831:32)
2021-10-18T09:54:28.689 app[4989544c] fra [info]   at Server._normalizeMiddleware (node_modules/@nuxt/server/dist/server.js:805:38)
2021-10-18T09:54:28.689 app[4989544c] fra [info]   at Server.resolveMiddleware (node_modules/@nuxt/server/dist/server.js:856:23)
2021-10-18T09:54:28.689 app[4989544c] fra [info]   at Server.useMiddleware (node_modules/@nuxt/server/dist/server.js:885:36)
2021-10-18T09:54:28.689 app[4989544c] fra [info]   at Server.setupMiddleware (node_modules/@nuxt/server/dist/server.js:715:12)
2021-10-18T09:54:28.689 app[4989544c] fra [info]   at async Server.ready (node_modules/@nuxt/server/dist/server.js:640:5)
2021-10-18T09:54:28.689 app[4989544c] fra [info]   at async Nuxt._init (node_modules/@nuxt/core/dist/core.js:482:7)
2021-10-18T09:54:28.695 app[4989544c] fra [info]    ╭──────────────────────────────────────────────────────────╮
2021-10-18T09:54:28.695 app[4989544c] fra [info]    │                                                          │
2021-10-18T09:54:28.695 app[4989544c] fra [info]    │   ✖ Nuxt Fatal Error                                     │
2021-10-18T09:54:28.695 app[4989544c] fra [info]    │                                                          │
2021-10-18T09:54:28.695 app[4989544c] fra [info]    │   Error: Cannot resolve "~/api/startingPoints.js" from   │
2021-10-18T09:54:28.695 app[4989544c] fra [info]    │   "/usr/src/app/api/startingPoints.js"                   │
2021-10-18T09:54:28.695 app[4989544c] fra [info]    │                                                          │
2021-10-18T09:54:28.695 app[4989544c] fra [info]    ╰──────────────────────────────────────────────────────────╯
2021-10-18T09:54:28.705 app[4989544c] fra [info] npm ERR! code ELIFECYCLE
2021-10-18T09:54:28.705 app[4989544c] fra [info] npm ERR! errno 1
2021-10-18T09:54:28.708 app[4989544c] fra [info] npm ERR! siddler@1.0.0 start: `nuxt start --modern=server`
2021-10-18T09:54:28.708 app[4989544c] fra [info] npm ERR! Exit status 1
2021-10-18T09:54:28.708 app[4989544c] fra [info] npm ERR!
2021-10-18T09:54:28.708 app[4989544c] fra [info] npm ERR! Failed at the siddler@1.0.0 start script.
2021-10-18T09:54:28.709 app[4989544c] fra [info] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
4

Oh crap, that’s a silly mistake by me :exploding_head: Didn’t get this in my test environment for some strange reason.
Thanks for getting me back on track!

1 Like