[BUG] Ryot is failing to start due to: migration 'm20241126_changes_for_issue_1113' #1145
Comments
|
Please send me a db dump. You must have an edge case which I didn't account for in the migrations. |
|
Hello, same issue here. Logs: [backend] 2024-12-20T13:46:22.816730Z INFO ryot: Running version: v7.12.4
[backend] 2024-12-20T13:46:22.837811Z INFO sea_orm_migration::migrator: Applying all pending migrations
[backend] 2024-12-20T13:46:22.839654Z ERROR ryot: Database migration failed: Custom Error: Migration file of version 'm20230804_create_user_measurement' is missing, this migration has been applied but its file is missing
[backend] Migration file of version 'm20240416_change_json_to_generic_json' is missing, this migration has been applied but its file is missing
[backend] Migration file of version 'm20240425_add_created_by_user_id_column_to_execise' is missing, this migration has been applied but its file is missing
[backend] Migration file of version 'm20230622_create_exercise' is missing, this migration has been applied but its file is missing
[backend] Migration file of version 'm20240415_is_v5_migration' is missing, this migration has been applied but its file is missing
[backend] Error: There was an error running the database migrations.
[proxy] {"level":"info","ts":1734702382.8406403,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":""}
[proxy] {"level":"warn","ts":1734702382.8416348,"msg":"Caddyfile input is not formatted; run 'caddy fmt --overwrite' to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":30}
[proxy] {"level":"warn","ts":1734702382.8418293,"logger":"admin","msg":"admin endpoint disabled"}
[proxy] {"level":"warn","ts":1734702382.8419316,"logger":"http.auto_https","msg":"automatic HTTPS is completely disabled for server","server_name":"srv0"}
[proxy] {"level":"info","ts":1734702382.8425994,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
[proxy] {"level":"info","ts":1734702382.8427134,"msg":"autosaved config (load with --resume flag)","file":"/home/ryot/.config/caddy/autosave.json"}
[proxy] {"level":"info","ts":1734702382.8427243,"msg":"serving initial configuration"}
[backend] BACKEND_PORT=5000 /usr/local/bin/backend exited with code 1
--> Sending SIGTERM to other processes..
[proxy] {"level":"info","ts":1734702382.8439393,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc00054a500"}
[proxy] {"level":"info","ts":1734702382.8439703,"logger":"tls","msg":"cleaning storage unit","description":"FileStorage:/home/ryot/.local/share/caddy"}
[proxy] {"level":"info","ts":1734702382.843984,"logger":"tls","msg":"finished cleaning storage units"}
[proxy] {"level":"info","ts":1734702382.8529873,"msg":"shutting down apps, then terminating","signal":"SIGTERM"}
[proxy] {"level":"warn","ts":1734702382.853009,"msg":"exiting; byeee!! 👋","signal":"SIGTERM"}
[proxy] {"level":"info","ts":1734702382.8530471,"logger":"http","msg":"servers shutting down with eternal grace period"}
[proxy] {"level":"info","ts":1734702382.853141,"msg":"shutdown complete","signal":"SIGTERM","exit_code":0}
[proxy] caddy run --config /etc/caddy/Caddyfile exited with code SIGTERM
--> Sending SIGTERM to other processes..
[frontend] PORT=3000 npx remix-serve ./build/server/index.js exited with code SIGTERMHow would I send you a db-dump? I actually completely re-did my Ryot instance just a week ago. |
|
Looking at your logs, it seems that you have jumped directly from v6 to v7 without following the migration guide. Is that so? You can perform a db dump using the command described in exporting docs. |
|
I am having the same issue on my unraid server. It was a new installation and not an upgrade so an migration hasn‘t happen |
How can it be a fresh installation and already contain migrations? The error says "this migration has been applied but its file is missing". |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ryot app stopped to work reporting the following error:
The text was updated successfully, but these errors were encountered: