Immich•6mo ago

Postgres Key Error

my postgres instance has some sort of key error going all the way back to 2024-05-25

I noticed an error cropping up in my logs and after some investigation, it looks like its a pretty old error.

root@immich:~/immich-app/postgres/log# rgrep -l "duplicate key value violates unique constraint" *
postgresql-2024-05-25_180135.log
postgresql-2024-05-26_101735.log
postgresql-2024-05-29_000000.log
postgresql-2024-05-30_000000.log
postgresql-2024-06-01_000000.log
postgresql-2024-07-04_050003.log
postgresql-2024-07-13_050004.log
postgresql-2024-07-16_050003.log
postgresql-2024-08-19_050002.log
postgresql-2024-08-31_050002.log
postgresql-2024-09-20_050002.log
postgresql-2024-10-15_150100.log
postgresql-2024-11-22_000000.log
postgresql-2024-11-22_050002.log
postgresql-2024-12-31_050002.log
postgresql-2025-01-02_050002.log
postgresql-2025-01-04_050002.log
postgresql-2025-01-07_050002.log
postgresql-2025-01-10_050002.log
postgresql-2025-01-17_050002.log
postgresql-2025-01-20_050548.log
postgresql-2025-01-24_050002.log
postgresql-2025-03-22_050002.log

root@immich:~/immich-app/postgres/log# rgrep -l "duplicate key value violates unique constraint" *
postgresql-2024-05-25_180135.log
postgresql-2024-05-26_101735.log
postgresql-2024-05-29_000000.log
postgresql-2024-05-30_000000.log
postgresql-2024-06-01_000000.log
postgresql-2024-07-04_050003.log
postgresql-2024-07-13_050004.log
postgresql-2024-07-16_050003.log
postgresql-2024-08-19_050002.log
postgresql-2024-08-31_050002.log
postgresql-2024-09-20_050002.log
postgresql-2024-10-15_150100.log
postgresql-2024-11-22_000000.log
postgresql-2024-11-22_050002.log
postgresql-2024-12-31_050002.log
postgresql-2025-01-02_050002.log
postgresql-2025-01-04_050002.log
postgresql-2025-01-07_050002.log
postgresql-2025-01-10_050002.log
postgresql-2025-01-17_050002.log
postgresql-2025-01-20_050548.log
postgresql-2025-01-24_050002.log
postgresql-2025-03-22_050002.log

root@immich:~/immich-app/postgres/log# rgrep -l "duplicate key value violates unique constraint" *
postgresql-2024-05-25_180135.log
postgresql-2024-05-26_101735.log
postgresql-2024-05-29_000000.log
postgresql-2024-05-30_000000.log
postgresql-2024-06-01_000000.log
postgresql-2024-07-04_050003.log
postgresql-2024-07-13_050004.log
postgresql-2024-07-16_050003.log
postgresql-2024-08-19_050002.log
postgresql-2024-08-31_050002.log
postgresql-2024-09-20_050002.log
postgresql-2024-10-15_150100.log
postgresql-2024-11-22_000000.log
postgresql-2024-11-22_050002.log
postgresql-2024-12-31_050002.log
postgresql-2025-01-02_050002.log
postgresql-2025-01-04_050002.log
postgresql-2025-01-07_050002.log
postgresql-2025-01-10_050002.log
postgresql-2025-01-17_050002.log
postgresql-2025-01-20_050548.log
postgresql-2025-01-24_050002.log
postgresql-2025-03-22_050002.log

root@immich:~/immich-app/postgres/log# rgrep -l "duplicate key value violates unique constraint" *
postgresql-2024-05-25_180135.log
postgresql-2024-05-26_101735.log
postgresql-2024-05-29_000000.log
postgresql-2024-05-30_000000.log
postgresql-2024-06-01_000000.log
postgresql-2024-07-04_050003.log
postgresql-2024-07-13_050004.log
postgresql-2024-07-16_050003.log
postgresql-2024-08-19_050002.log
postgresql-2024-08-31_050002.log
postgresql-2024-09-20_050002.log
postgresql-2024-10-15_150100.log
postgresql-2024-11-22_000000.log
postgresql-2024-11-22_050002.log
postgresql-2024-12-31_050002.log
postgresql-2025-01-02_050002.log
postgresql-2025-01-04_050002.log
postgresql-2025-01-07_050002.log
postgresql-2025-01-10_050002.log
postgresql-2025-01-17_050002.log
postgresql-2025-01-20_050548.log
postgresql-2025-01-24_050002.log
postgresql-2025-03-22_050002.log

The first instance of this error showing up is pretty long. I think maybe while i was setting up and backing up all my assets?

immich.log58.17KB

immich-2.log329.51KB

Immich•7/6/25, 5:14 PM

:wave: Hey @blotz,

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
```
```
docker compose logs
```
docs
Container Status:
```
docker ps -a
```
```
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

Immich•7/6/25, 5:14 PM

Checklist

I have...

:ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
:ballot_box_with_check: read applicable release notes.
:blue_square: reviewed the FAQs for known issues.
:blue_square: reviewed Github for known issues.
:ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
:ballot_box_with_check: uploaded the relevant information (see below).
: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
```
```
fdisk -l
```
and
```
df -h
```
```
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

/close

command, and re-open it later if needed.

Zeus•7/6/25, 5:16 PM

That’s normal

blotzOP•7/6/25, 5:18 PM

it is?

Zeus•7/6/25, 5:18 PM

Yes

Zeus•7/6/25, 5:19 PM

There’s an issue for it but it’s basically meaningless

blotzOP•7/6/25, 5:21 PM

ahh ty

blotzOP•7/6/25, 5:21 PM

tbf its a spooky ass error

blotzOP•7/6/25, 5:21 PM

i figured it was my fault

ImmichAPP•7/6/25, 5:22 PM

This thread has been closed. To re-open, use the button below.

Postgres Key Error

References

Checklist

Information

Similar Threads

Similar Threads

References

Checklist

Information

Similar Threads