I
Immich•3w ago
miasinterestinglife

Issues with OCR - Permission denied

After updating to 2.2.0 I wanted to run OCR on all assets (as was recommended in the update post). I got suspicious when it took really long and always processed 12 images at the exact same time according to the ui (the amount of concurrency I set it to). Checking the logs, I saw this: 
2025-11-01 20:52:56.034676+00:00                             ╰─────────────────────────────────────────────────╯
2025-11-01 20:52:56.034693+00:00                             PermissionError: [Errno 13] Permission denied:     
2025-11-01 20:52:56.034709+00:00                             '/opt/venv/lib/python3.11/site-packages/rapidocr/mo
2025-11-01 20:52:56.034727+00:00                             dels/FZYTK.TTF'                                    
2025-11-01 20:53:01.739019+00:00[11/01/25 21:53:01] ERROR    Worker (pid:251) was sent SIGKILL! Perhaps out of  
2025-11-01 20:53:01.739069+00:00                             memory?                                            
2025-11-01 20:52:56.034676+00:00                             ╰─────────────────────────────────────────────────╯
2025-11-01 20:52:56.034693+00:00                             PermissionError: [Errno 13] Permission denied:     
2025-11-01 20:52:56.034709+00:00                             '/opt/venv/lib/python3.11/site-packages/rapidocr/mo
2025-11-01 20:52:56.034727+00:00                             dels/FZYTK.TTF'                                    
2025-11-01 20:53:01.739019+00:00[11/01/25 21:53:01] ERROR    Worker (pid:251) was sent SIGKILL! Perhaps out of  
2025-11-01 20:53:01.739069+00:00                             memory?
Now I am definitely not out of memory and I am somewhat unsure what the Permission Error means. (Really sorry for the broken Encoding, that's what TrueNAS shows to me.
6 Replies
Immich
Immich•3w ago
:wave: Hey @miasinterestinglife, 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. :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.
bo0tzz
bo0tzz•3w ago
Update to 2.2.1
miasinterestinglife
miasinterestinglifeOP•3w ago
still getting the following error: 
2025-11-01 21:09:58.182167+00:00[11/01/25 22:09:58] ERROR    Worker (pid:141) was sent SIGKILL! Perhaps out of  
2025-11-01 21:09:58.182255+00:00                             memory?
2025-11-01 21:09:58.182167+00:00[11/01/25 22:09:58] ERROR    Worker (pid:141) was sent SIGKILL! Perhaps out of  
2025-11-01 21:09:58.182255+00:00                             memory?
Mraedis
Mraedis•3w ago
Have you considered the worker is perhaps out of memory
miasinterestinglife
miasinterestinglifeOP•3w ago
i have, but my server currently has 6 GB of free memory so I doubt that would be the issue I'm gonna try raising the memory limit in truenas (currently at 4GB) still throwing the same error with 8GB of memory (the app is using 3GB while throwing that error) actually seems to be fine now and the log didn't update thanks for the help!
Immich
Immich•3w ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?