Postgres error during migrations
Hello! I'm trying to get immich running for the first time and have been running into some trouble. I've made it to this error, which happens while the server spins up for the first time and runs migrations, and I'm coming up empty looking for a solution.
This appears in the server during migrations, and then the container exits with an error.
- Running immich v1.132.3
- I installed pgvecto.rs version 0.3.0 on my postgres instance
- I've made the
immich
user a superuser
- I've made the immich
user the owner of the vectors
schema as was the solution here
So far have not been successful in getting past this error. Anyone else seen this before? I'd really appreciate any suggestions anyone has!11 Replies
:wave: Hey @Matt,
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.How are you running postgres?
Also in kubernetes, so I wrote a docker image that looks like this (following the pgvectors docs on installing via a deb package):
FROM postgres:16-bullseye
RUN wget https://github.com/tensorchord/pgvecto.rs/releases/download/v0.3.0/vectors-pg16_0.3.0_amd64.deb
RUN apt install -y ./vectors-pg16_0.3.0_amd64.deb
Are you just running raw Postgres in a Deployment, or using an operator or such?
Just raw Postgres in a statefulset with a longhorn PVC
Hmm, that should be fine
(though I usually recommend using an operator like cloudnative-pg, that shouldn't be relevant for this problem)
The only time I've seen an error remotely similar to this was in the logs for #11090, where someone's database was pretty badly corrupted
Can you try wiping the postgres data completely for a fresh start?
yeah good call, I think I had not installed pgvecto.rs properly or something. It's a shared postgres instance so I was hoping to add an immich db to it, but instead I just spun up a dedicated immich postgres with the official pgvecto.rs image instead of my custom postgres image, and it is working now 🎉
Thanks a lot for your help
This thread has been closed. To re-open, use the button below.