Face Recognition or Machine Learning not working after an update
I've recently started using immich on a Raspberry Pi 5 (8GB RAM). Until now, I've been uploading all my photos from every device to immich and to do so, I set the Machine Learning feature to do it remotely (on a more powerful PC). Everything worked fine until a couple of days ago (maybe last week), when faces stopped being recognized without touching anything. I've done deep research reading logs trough portainer from immich_server container and immich_machine_learning container from docker on the PC wich manage ML feature remotely. I attached the following logs:
- immich_server log when uploading a photo (from portainer). I think most important part are last lines from that point: [Nest] 7 - 02/01/2025, 3:27:42 PM ERROR [Microservices:JobService] Unable to run job handler (faceDetection/face-detection): PostgresError: pgvecto.rs: Bad literal.
INFORMATION: hint = Bad character with ascii 0x31.
- immich_machine_learning log when uploading a photo (from docker on the powerful PC)
I found some people having the same issue and seems they can solved it, but couldn't find how the did. Thanks in advance.
8 Replies
:wave: Hey @Tomito,
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_01GY0DAKGXDEHE263BCAYEGFJAChecklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: 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.GitHub
immich-app immich · Discussions
Explore the GitHub Discussions forum for immich-app immich. Discuss code, ask questions & collaborate with the developer community.
FAQ | Immich
User
GitHub
Issues · immich-app/immich
High performance self-hosted photo and video management solution. - Issues · immich-app/immich
Are you updating your remote ML container too when updating?
How can I check that? However, I don't think that's the problem because I change the machine learning to the deafault setting (http://immich-machine-learning:3003 instead of remote ML) and there's another error message which I think came from the same problem.
If you're updating through
docker compose up -d then the local ML should be up to date yes. But for your remote ML you should do the same of course
I think there is a bad character in the DB somewhere
So changing ML service won't fix this, we need to dive in the DB
Unfortunately I need to leave right now so I hope someone else sees this 😅Okey, thanks for your help btw
This sure looks like outdated ML to me
Can you set IMMICH_VERSION in the env file to v1.125.7, bring the stack up again, post all of the logs after that, and share a screenshot of your ML config?
Unfortunately, I need to leave too, in fact, i'm gona take i fly in a couple of hour and it will be difficult to try new things these days, maybe when i come back it's fine, or maybe i need to open a new thread hahahah
gonna try quickly
I have this inside env file
You can find documentation for all the supported env variables at https://immich.app/docs/install/env>
The location where your uploaded files are stored
UPLOAD_LOCATION=./home/tomas/immich_fotos
The location where your database files are stored
DB_DATA_LOCATION=./postgres
To set a timezone, uncomment the next line and change Etc/UTC to a TZ identifier from this list: http>
TZ=Etc/UTC
The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=release
Connection secret for postgres. You should change it to a random password
Please use only the characters
A-Za-z0-9, without special characters or spaces
DB_PASSWORD=.......
The values below this line do not need to be changed
###################################################################################
DB_USERNAME=postgres
DB_DATABASE_NAME=immich
I need to leave, so sorry, if you have an idea I'll try it next week. Btw thanks to both of you