I need help, around last week sometime my machine stopped, and for whatever reason I have been able to do nothing to restart it. I try to restart in rolling and immediate mode but it just doesn’t What more can I do?
Might be worth getting some logs from flyctl, and posting them here, so readers can see them.
025-11-12T18:13:15.127 app[48ed194f7d9098] dfw [info] INFO Starting init (commit: fad6f82)…
2025-11-12T18:13:15.687 app[48ed194f7d9098] dfw [info] INFO Checking filesystem on /data
2025-11-12T18:13:15.692 app[48ed194f7d9098] dfw [info] /dev/vdc: clean, 25/64512 files, 10116/258048 blocks
2025-11-12T18:13:15.694 app[48ed194f7d9098] dfw [info] INFO Mounting /dev/vdc at /data w/ uid: 0, gid: 0 and chmod 0755
2025-11-12T18:13:15.770 app[48ed194f7d9098] dfw [info] INFO Resized /data to 1056964608 bytes
2025-11-12T18:13:15.848 app[48ed194f7d9098] dfw [info] INFO Preparing to run: `/usr/bin/tini -g – node --max-old-space-size=180 app.js` as root
2025-11-12T18:13:15.850 app[48ed194f7d9098] dfw [info] INFO [fly api proxy] listening at /.fly/api
2025-11-12T18:13:16.121 runner[48ed194f7d9098] dfw [info] Machine started in 2.629s
2025-11-12T18:13:16.122 proxy[48ed194f7d9098] dfw [info] machine started in 2.743974499s
2025-11-12T18:13:19.611 app[48ed194f7d9098] dfw [info] 2025/11/12 18:13:19 INFO SSH listening listen_address=[fdaa:9:5e03:a7b:18c:8ace:ff51:2]:22
2025-11-12T18:13:22.050 proxy[48ed194f7d9098] dfw [info] waiting for machine to be reachable on 0.0.0.0:5006 (waited 5.927437388s so far)
2025-11-12T18:13:25.207 proxy[48ed194f7d9098] dfw [error] [PM05] failed to connect to machine: gave up after 15 attempts (in 9.084960736s)
2025-11-12T18:13:37.134 app[48ed194f7d9098] dfw [info] Checking if there are any migrations to run for direction “up”…
2025-11-12T18:13:37.770 app[48ed194f7d9098] dfw [info] Rejection: Error: Missing migration file: 1718889148000-openid.js
2025-11-12T18:13:37.770 app[48ed194f7d9098] dfw [info] at /app/node_modules/migrate/lib/load-migrations.js:64:44
2025-11-12T18:13:37.770 app[48ed194f7d9098] dfw [info] at Array.forEach ()
2025-11-12T18:13:37.770 app[48ed194f7d9098] dfw [info] at /app/node_modules/migrate/lib/load-migrations.js:62:44
2025-11-12T18:13:38.848 app[48ed194f7d9098] dfw [info] INFO Main child exited normally with code: 0
2025-11-12T18:13:38.866 app[48ed194f7d9098] dfw [info] INFO Starting clean up.
2025-11-12T18:13:38.871 app[48ed194f7d9098] dfw [info] INFO Umounting /dev/vdc from /data
2025-11-12T18:13:38.873 app[48ed194f7d9098] dfw [info] [ 25.159841] reboot: Restarting system
2025-11-12T18:13:39.146 runner[48ed194f7d9098] dfw [info] machine exited with exit code 0, not restarting
2025-11-12T18:13:41.696 proxy[48ed194f7d9098] dfw [info] Starting machine
2025-11-12T18:13:41.848 app[48ed194f7d9098] dfw [info] 2025-11-12T18:13:41.848509199 [01K8WSMJ8AHEXZ0K2X8MGJDYY2:main] Running Firecracker v1.12.1
2025-11-12T18:13:41.848 app[48ed194f7d9098] dfw [info] 2025-11-12T18:13:41.848683733 [01K8WSMJ8AHEXZ0K2X8MGJDYY2:main] Listening on API socket (“/fc.sock”).
I saw a pop up from fly doctor say something about a proxy? I tabbed off and when I tabbed back it was no longer there
There you go; you have an application-level error, and your app is crashing.
This causes a knock-on error too: an iteration loop fails because of a missing file:
If you can, start testing your app locally before you deploy. Get Docker installed, if you’ve not already.
The app is Actual Budget not one of mine, I suppose I can bring it to their attention
A quick search indicates that Actual Budget is self-hosted software. I would guess you’ve missed a build or configuration step, rather than it being a bug in the software. Have you got a Dockerfile? If so, show it here (in a Markdown code block please).
I do not have a docker file, I have had it running for almost a year now perfectly fine and changed nothing when the error occured (basically set and forget and only use the actual application) , I settled on deleting the app and reinstalling it and now it works fine so not sure what the issue was
Ah, I’ve just read the instructions; you’re deploying from an image, not from a Dockerfile:
actualbudget/actual-server:latest
So there will be a Dockerfile somewhere, but you don’t have to deal with it.
There was a corrupted config, perhaps. Since it uses a volume mounted at /data, you could restore the volume back one day or something, rather than blatting the whole lot. Or perhaps the app will let you export data and reimport, saving you having to enter it all in again manually.
There was actually a way to export the data within the app itself but I’ll keep this in mind on the off chance it does cause an issue again. Thank you
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.