V1.140.1 crashed after file upload, downgrade to V.1.138.1 throws corrupted migrations error
This morning I did the upgrade from v135 to v140.1 Everything seems to be fine.
An hour ago I tried to upload more then 100 new images. More the 90% got an error in the UI (is there some a logfile for?)
The Immich server continuously restarts (approx. every 30 seconds) until this log entry:
2025-09-01T15:27:08.190037239Z [Nest] 18 - 09/01/2025, 5:27:08 PM LOG [Api:Bootstrap] Immich Server is listening on http://[::1]:2283 [v1.140.1] [production].
When I try to downgrade to 1.138.1, I get the error message:
[Nest] 7 - 09/01/2025, 6:25:04 PM ERROR [Microservices:DatabaseRepository] Migrations failed: Error: corrupted migrations: previously executed migration 1756318797207-AssetMetadataTables is missing
Error: corrupted migrations: previously executed migration 1756318797207-AssetMetadataTables is missing
at #ensureNoMissingMigrations (/usr/src/app/server/node_modules/kysely/dist/cjs/migration/migrator.js:487:23)
at #getState (/usr/src/app/server/node_modules/kysely/dist/cjs/migration/migrator.js:439:40)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async run (/usr/src/app/server/node_modules/kysely/dist/cjs/migration/migrator.js:409:31)
at async /usr/src/app/server/node_modules/kysely/dist/cjs/kysely.js:569:32
at async DefaultConnectionProvider.provideConnection (/usr/src/app/server/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20)
at async #migrate (/usr/src/app/server/node_modules/kysely/dist/cjs/migration/migrator.js:268:20)
at async DatabaseRepository.runMigrations (/usr/src/app/server/dist/repositories/database.repository.js:325:36)
at async /usr/src/app/server/dist/services/database.service.js:110:17
at async /usr/src/app/server/dist/repositories/database.repository.js:379:27
This Immich instance is currently unusable. It had been running smoothly on a Raspi 4B for over 6 months.
16 Replies
:wave: Hey @kho,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.Downgrading won't work but there's a semi-fix for 1.141 on RPIs
Set the env variable
VIPS_NOVECTOR=1Thanks, it seems working. At least I can start the instance again now. However, I haven't tried uploading anything yet.
is there completely no way to properly downgrade, just noticed this morning it auto updated, forgor to pin version
If you restore from a backup you obviously can
Small downgrades typically might work, it'll tell you if it doesn't
well now half dumb question, does it auto backup
We only have nightly database dumbs, everything else is your job
shouldnt this do it i guess?
Those are the DB dumps I mentioned
right, and the server crashes because of failed migration, so wouldn't that mean if we restore db all technically good
and 1.140 -> 1.139.4
Wait why are you even posting on a completely unrelated thread?
Instead of trying to fix it yourself it might be helpful to just open your own thread and share the actual error there
its not unrelated, having exact same error
So the env variable fixes it for you?
no
Then you don't have the same issue
fair enough