Immich•2mo ago

immich-server container boot-loops after changing smart search model

Hey, after the update to 1.130 i changed the Ai model from "ViT-B-32openai" to "ViT-SO400M-16-SigLIP2-512webli" and than my server just crashed and now wont start back on : / What can i do. Like how can i go back to the old ai model if i cant reach the WebUI. I already tried restarting my debian server and docker compose down for Immich. Thanks for your help.

11 Replies

Immich•2mo ago

:wave: Hey @Keanu Malzbier, 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. :blue_square: reviewed the FAQs for known issues. 4. :blue_square: 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.

Keanu MalzbierOP•2mo ago

output_docker_logs_i...

docker-compose.yml

env

sogan•2mo ago

Okay, so somehow you don’t have the clip index at all. It might have been lost when you restored from a backup. Can you start by bringing down all the containers, then bringing up the database alone? The next steps would be

docker exec -it immich_postgres sh
psql -U postgres immich
SET vectors.pgvector_compatibility=on;
SET search_path TO "$user", public, vectors;
CREATE INDEX clip_index ON smart_search USING hnsw (embedding vector_cosine_ops) WITH (ef_construction = 300, m = 16);

docker exec -it immich_postgres sh
psql -U postgres immich
SET vectors.pgvector_compatibility=on;
SET search_path TO "$user", public, vectors;
CREATE INDEX clip_index ON smart_search USING hnsw (embedding vector_cosine_ops) WITH (ef_construction = 300, m = 16);