Since April 8th none of my new pictures have been assigned to people. I have manually run the "missing" job for Face detection and Facial Recognition however that has made not difference. Looking at the micro-service logs, the error is the same as in #8153. I'm assuming some how my faces have been corrupted and that I will need to run the two jobs again across all of my pictures?
#Faces not being found in new Pictures
1 messages · Page 1 of 1 (latest)
:wave: Hey @old crystal,
Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich
.
References
- Container Logs:
docker compose logsdocs - Container Status:
docker compose psdocs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
Checklist
- :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
- :ballot_box_with_check: I have read applicable release notes.
- :ballot_box_with_check: I have reviewed the FAQs for known issues.
- :ballot_box_with_check: I have reviewed Github for known issues.
- :ballot_box_with_check: I have tried accessing Immich via local ip (without a custom reverse proxy).
- :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the
/uploadcommand. - :blue_square: I have 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)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
[Issue] Facial Recognition - PersonService Face Not Found (#8153)
@old crystal uploaded
@old crystal uploaded
@old crystal uploaded
For other users of the system, does this problem also exist?
Could you paste it with the URL of the machine Immich was running on?
/api/face?id=2be202c8-a7ef-4f99-a602-60e1494d469b
{"message":"Not found or no asset.read access","error":"Bad Request","statusCode":400}
Maybe in this case you should make a backup of the database and then clear the face table, this will reset all face data including the names assigned to them.
@raw gate Maybe you have a different opinion about it?
Would I need to delete the table or could I just disable and re-enable face recognition in the admin settings?
Disabling facial recognition won’t delete existing face data. In the job panel, you can run Face Detection on all assets and that will nuke the existing data.
Exactly, I managed to forget that this option already exists because it is too dangerous to click on it after you have assigned names to over 100 faces 🤯
By the way, if you are here, do you know how to avoid this problem? It doesn't seem to be a common problem but it does come back from time to time.
I don’t know why this would happen systematically. This error should only really happen if a user does something in between queueing and running the facial recognition jobs.