Immich not launching after update to v1.132.1
fter updating my immich instance to 1.132.1, it fails to start properly.
Seems to be related to a not-null constraint in geodata_places
57 Replies
:wave: Hey @Pendor,
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. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: 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.https://github.com/immich-app/immich/issues/17839
immich_server | [Nest] 7 - 04/24/2025, 3:00:21 PM LOG [Microservices:MapRepository] 100000 geodata records imported
immich_server | Query failed : {
immich_server | durationMs: 1137.0610329999981,
immich_server | error: PostgresError: null value in column "name" of relation "geodata_places" violates not-null constraint
immich_server | at ErrorResponse (/usr/src/app/node_modules/postgres/cjs/src/connection.js:790:26)
immich_server | at handle (/usr/src/app/node_modules/postgres/cjs/src/connection.js:476:6)
immich_server | at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:315:9)
immich_server | at Socket.emit (node:events:518:28)
immich_server | at addChunk (node:internal/streams/readable:561:12)
immich_server | at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
immich_server | at Readable.push (node:internal/streams/readable:392:5)
immich_server | at TCP.onStreamRead (node:internal/stream_base_commons:189:23) {
immich_server | severity_local: 'ERROR',
immich_server | severity: 'ERROR',
immich_server | code: '23502',
immich_server | detail: 'Failing row contains (1059, null, NaN, NaN, null, null, null, null, null, null, null).',
immich_server | schema_name: 'public',
immich_server | table_name: 'geodata_places',
immich_server | column_name: 'name',
immich_server | file: 'execMain.c',
immich_server | line: '1883',
immich_server | routine: 'ExecConstraints'
immich_server | },
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
Hey, thanks for opening the thread
No prob
I'll be with your shortly, do you know how to run SQL commands on your postgres database?
Yeah, take your time, no hurry
I have to update it to the latest release again, cause i downgrade it so I can have a working instance
and that'll take a few mins
yeah, we ran a simple query with alex to search for null names
Alright
but got 0 rows, weird
Have you ever previously restored your database from a backup?
nope
Whenever it's updated, if you could run this query and give me the output, that'd be great π
SELECT * FROM information_schema.columns WHERE table_schema = 'public' AND table_name = 'geodata_places';
Thanks, that all looks correct π€
How about
SELECT * FROM information_schema.columns WHERE table_schema = 'public' AND table_name = 'geodata_places_tmp';
Does that return any rows?nope
0 rows
It's kinda weird that it complains about a null name in geodata_places but I can't find any rows like that
Yea, so that's a bit of a weird one
It won't showup when you query the table because we run all of this in a transaction
what's that first parameter? 1059?
So when it fails, the entire thing is reverted
oh ok
Trying to figure out how we can even debug this
I might have to throw together a branch with some extra debug info that you can run π€£
Is it always 1059?
let me double check
yup
I'm just checking if 1059 even appears for me
what's that 1059 supposed to be? an id?
Yea, it's an id from the source file the data comes from
π€
That file is bundled with the docker build
So idk how it can be wrong specifically for you π€£

There isn't even a place with id 1059 π€
What OS are you running this on?
yeah, same here, that's the second thing I tried
no rows with id 1059
Yea, the only difference with my query is this is on the latest update
So it's imported with the same data you're using
Debian bookworm on an RPI4
what's the storage medium? for both OS and the immich datbaase
OS in on the microSD, immich (i think) is on an SSD
π¬
I'm strongly suspecting this might just be plain old corruption
corruption of what, specifically?
immich files in the storage?
should a new docker pull kinda fix that, if that were the case?
I don't think that can be the case
well, we don't really know that the storage is allocated
Unless micro SD cards are failing, it's unlikely they're going to just cause corruption
The process that occurs for this basically wipes everything clean
im gonna go eat something and then i'll move the images to another disk
and try again
I'm just pushing a branch so I can build an image for you to use
but its not using the microsd for this
(i think)
Presumably the docker images are still on the microsd
microsd should just hold the os
Unless you told docker to use the SSD for that too
i'm pretty sure i did that, yeah
but yeah, i'll double check after lunch
I'll have a docker tag for you to test in 5 minutes or so too
Which should output some debug lines for that 1059 record
awesome, thanks
be back later
send me the docker tag when you have it and i'll look into that as well
Will do
Tag is
commit-f68792bde7df367a8cb4144e5bc5acac1f787172
or pr-17853
Your choice π
I'm heading out for now, but if you can try that, it's basically just 1.132.1 but with some extra debug messages on top
Hopefully you get some output, if you could post that here, that'd be great πok
nevermind
that was it
π€¦ββοΈ
i had moved only the compose files to the hdd
but i was running docker from the microsd
moved docker to main hdd, pulled the image again
and voila
works
so yeah, it was probably corrupted
sorry to waste your time π€¦ββοΈ
Thanks for the update. Micro SD can be pretty notoriously unreliable (same for USB sticks tbh) external SSD will be the most stable results
and thanks for the help
yeah, i know, i guess I thought i migrated everything but i didn't
Well, the OS is a big one π
I have. Had a pi go bad from systemd getting corrupted before and it couldnβt shutdown anymore
π©
(insert openRC joke here)
If it's corrupting things you wanna replace that SD card lol
They shouldn't be doing that in normal operation unless they are dieing
Eh, in my experience this is not abnormal for IO intensive operations on a Pi (micro SD or usb stick)
As in, a new micro SD wonβt necessarily fix it completely
That sounds like a faulty device to me
MicroSDs aren't great but they don't just randomly corrupt stuff without a fault
Can also have a lot to do with the specific MicroSD card
Some of them are just truly awful