#ERROR [Microservices:{"source":"upload","id":"7c1ccf38-3730-4342-aa3d-11386d069f05"}] Unable to run

1 messages · Page 1 of 1 (latest)

brittle swallow
#

running docker on pi5.
i have the following error:
Nest] 7 - 12/23/2025, 6:01:17 AM LOG [Microservices:PersonService] Creating new person for face cd59f731-23a3-44d5-abb9-27499d197164

[Nest] 7 - 12/23/2025, 6:01:17 AM WARN [Microservices:MachineLearningRepository] Machine learning request to "http://immich-machine-learning:3003" failed: fetch failed

[Nest] 7 - 12/23/2025, 6:01:17 AM ERROR [Microservices:{"source":"upload","id":"7c1ccf38-3730-4342-aa3d-11386d069f05"}] Unable to run job handler (SmartSearch): Error: Machine learning request '{"clip":{"visual":{"modelName":"ViT-B-32__openai"}}}' failed for all URLs

Error: Machine learning request '{"clip":{"visual":{"modelName":"ViT-B-32__openai"}}}' failed for all URLs

at MachineLearningRepository.predict (/usr/src/app/server/dist/repositories/machine-learning.repository.js:117:15)

at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

at async MachineLearningRepository.encodeImage (/usr/src/app/server/dist/repositories/machine-learning.repository.js:135:26)

at async SmartInfoService.handleEncodeClip (/usr/src/app/server/dist/services/smart-info.service.js:91:27)

at async JobService.onJobRun (/usr/src/app/server/dist/services/job.service.js:51:30)

at async EventRepository.onEvent (/usr/src/app/server/dist/repositories/event.repository.js:91:13)

at async /usr/src/app/server/node_modules/.pnpm/[email protected]/node_modules/bullmq/dist/cjs/classes/worker.js:566:32

machine learinging docker is up and running and showing no errors.

strange bronzeBOT
#

:wave: Hey @brittle swallow,

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

#

Checklist

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.

knotty drum
#

What's the uptime of the containers? How much RAM does your Pi have? Are there any other services running?

My first guess would be OOM

brittle swallow
#

pi@raspberrypi:~ $ free -mh
total used free shared buff/cache available
Mem: 15Gi 8.0Gi 239Mi 661Mi 4.9Gi 7.9Gi
Swap: 199Mi 199Mi 576Ki
pi@raspberrypi:~ $

#

the uptime is a couple of hours