Upgraded to pgvecto-rs:pg16-v0.3.0 from pgvecto-rs:pg16-v0.2.0 now Immich won't start api worker

I updated the pgvecto container and now the immich container just loops an error I assume there is some step I need to do for upgrading? I tried restarting like the warning says and I tried going to the docs, but that domain is for sale...
15 Replies
Immich
Immich3mo ago
:wave: Hey @FlexibleToast, 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.
Daniel
Daniel3mo ago
I tried going to the docs, but that domain is for sale...
Our domain? Also, please post the information the bot asks for and don't just tick the boxes
FlexibleToast
FlexibleToastOP3mo ago
I'm trying to post the log but it's too long...
Mraedis
Mraedis3mo ago
Put it in a file and upload the file
FlexibleToast
FlexibleToastOP3mo ago
Sounds good
FlexibleToast
FlexibleToastOP3mo ago
Not that domain. The one that's in the log I haven't posted yet
Mraedis
Mraedis3mo ago
They changed domains indeed
FlexibleToast
FlexibleToastOP3mo ago
Okay, there is the log. This is being run with docker on unraid
Daniel
Daniel3mo ago
Have you tried restarting the database? As it says
FlexibleToast
FlexibleToastOP3mo ago
I ran the ALTER EXTENSION vectors UPDATE; command Yes, I have. Like I said in the original post
Daniel
Daniel3mo ago
https://docs.vectorchord.ai/admin/upgrading.html this is the correct URL as Mraedis said
Upgrading | pgvecto.rs
Scalable Vector Search in Postgres
FlexibleToast
FlexibleToastOP3mo ago
Okay, looks like there might be a couple more steps that just that one ALTER command Cool, I got it fixed following the pgvectors upgrade docs. It was something like this:
psql -U postgres immich
ALTER EXTENSION vectors UPDATE;
SELECT pgvectors_upgrade();
SELECT
I.relname AS indexname
FROM pg_index X JOIN
pg_class I ON I.oid = X.indexrelid JOIN
pg_am A ON A.oid = I.relam
WHERE A.amname = 'vectors';
# Then I ran the REINDEX against the two that resulted from the previous SELECT
REINDEX INDEX clips_index;
REINDEX INDEX faces_index;
psql -U postgres immich
ALTER EXTENSION vectors UPDATE;
SELECT pgvectors_upgrade();
SELECT
I.relname AS indexname
FROM pg_index X JOIN
pg_class I ON I.oid = X.indexrelid JOIN
pg_am A ON A.oid = I.relam
WHERE A.amname = 'vectors';
# Then I ran the REINDEX against the two that resulted from the previous SELECT
REINDEX INDEX clips_index;
REINDEX INDEX faces_index;
Then restarted the pgvector container and started the immich container.
Immich
Immich3mo ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?