No Smart Search
- OS: Rocky9
- Deployment: Docker Compose
- Immich Version: v1.121.0 & 1.134.0
- HW:
- AMD 3600
- ASUS B550 mobo
- Gigabyte 1080ti
- Several TB free storage
- Reverse Proxy: SWAG
I was previously running immich v1.121.0 when I noticed that my smart search was no longer working. I decided I likely just needed an update, and updated to v1.134.0 and checked for updates to the docker-compose.yml & supporting files. I can't remember if I checked the logs before updating to the newer version, but I'm currently seeing the error(s). From what I can gather, I think the models are self contained in the ML image. Which ruled out my first thought that I may be blocking the location hosting the models. I've also tried to open port 3003 on the ML container and that didn't help. Any ideas?
14 Replies
:wave: Hey @brconn,
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.IMMICH_VERSION=v1.134.0
This has occurred with the existing model-cache as well as a new & fresh model-cache
FWIW, when drop
-cuda
from the ML image it works greatERROR Worker (pid:9) was sent code 139!It's segfaulting What driver version are you running?
NVIDIA-SMI 550.100 Driver Version: 575.57.08 CUDA Version: 12.4
Running on a 1080ti which should have compute capability 6.1And do you meet the other requirements from https://immich.app/docs/features/ml-hardware-acceleration#cuda ?
I believe so
@sogan any idea?
Segfaults are generally driver-related. I'm not sure why that specific driver would be problematic though
Looks like that's the latest available nvidia driver on Rocky9 atm. I could try and replace it with the dkms version maybe?
Actually I'm already on dkms
Do you have the latest nvidia-container-toolkit installed?
Yup 1.17.8 is the latest per their GitHub
I did have a kernel update to do. So I did that and let DKMS rebuild but that didn't help
@mertalev If I set the LD_LIBRARY_PATH for the ML container to include the path to cuda I'm able to get farther