Fly deploy critical health status, was working fine 2 weeks ago

Questions / Help Build debugging
1

Hey guys,
I did a few updates to my app and tried to push and I keep running into a critical error and I can’t figure out why.

I’m not sure where else to look to try and debug. Any help would be much appreciated!

I should note that building and serving the app locally works just fine.

Happy New Year!

2022-01-01T18:47:39.000 [info] Unpacking image
2022-01-01T18:47:57.000 [info] Preparing kernel init
2022-01-01T18:47:58.000 [info] Configuring firecracker
2022-01-01T18:47:58.000 [info] Starting virtual machine
2022-01-01T18:47:59.000 [info] Starting init (commit: 7943db6)...
2022-01-01T18:47:59.000 [info] Preparing to run: `docker-entrypoint.sh npm run start` as root
2022-01-01T18:47:59.000 [info] 2022/01/01 18:47:59 listening on [fdaa:0:3a82:a7b:5b:beb6:9d6f:2]:22 (DNS: [fdaa::3]:53)
2022-01-01T18:47:59.000 [info] > start
2022-01-01T18:47:59.000 [info] > node -r dotenv/config node_modules/.bin/remix-serve build
2022-01-01T18:48:01.000 [info] (node:527) ExperimentalWarning: stream/web is an experimental feature. This feature could change at any time
2022-01-01T18:48:01.000 [info] (Use `node --trace-warnings ...` to show where the warning was created)
2022-01-01T18:48:01.000 [info] (node:527) ExperimentalWarning: buffer.Blob is an experimental feature. This feature could change at any time
2022-01-01T18:48:01.000 [info] Remix App Server started at http://localhost:3000
2022-01-01T18:49:03.000 [error] Health check status changed 'warning' => 'critical'
2

Can you post your fly.toml?

1 Like
3

@jsierles - Thanks for reaching out! I ended up reverting to a build that I knew was working to make sure it wasn’t my code and it completed surprisingly. So I’ve been slowing adding back in the new code saving and redeploying slowly and so far so good. Not sure what I did, but Fly didn’t like it.