Error: ENOENT: no such file or directory when importing using immich-go
Having done much testing and cross referencing with immich-go, I think I have found a bug in Immich, unless someone can point something I'm doing wrong...
I get a lot of errors such as the following in immich-server logs when doing an immich-go import. The immich-go client says it works with no errors during upload, but there are problems in the server.
In my original 1.130.3 setup I didn't realize the storage label was admin instead of my username, so I changed my storage label and did a migration that subsequently had problems. So I canned the whole setup and decided to start from scratch with the latest 1.132.1
Observation #1. I noted that my original immich-machine-learning setup was using the "release" tag from the
This is what causes the immich-server errors. I noted that if I changed the tag for immich-machine-learning to "v1.132.1" it doesn't give these errors.
I also note that the upload/upload/<filename> directory doesn't exist, and the path is probably correct with just a single upload/<filename>
Am I doing something wrong or is this a legitimate problem?
I get a lot of errors such as the following in immich-server logs when doing an immich-go import. The immich-go client says it works with no errors during upload, but there are problems in the server.
immich_server | [Nest] 7 - 04/25/2025, 12:23:59 PM ERROR [Microservices:{"id":"7e66b675-ad40-4e90-886f-9e6faca4b264","source":"sidecar-write"}] Unable to run job handler (metadataExtraction/metadata-extraction): Error: ENOENT: no such file or directory, stat 'upload/upload/9f276f9e-c6fe-4c53-8264-85431576082c/d9/90/d990ea3d-d5b7-4b0f-9757-fb2b24e2f551.jp
In my original 1.130.3 setup I didn't realize the storage label was admin instead of my username, so I changed my storage label and did a migration that subsequently had problems. So I canned the whole setup and decided to start from scratch with the latest 1.132.1
Observation #1. I noted that my original immich-machine-learning setup was using the "release" tag from the
.envdocker-compose.ymlextends: service: openvinov1.132.1-openvinoThis is what causes the immich-server errors. I noted that if I changed the tag for immich-machine-learning to "v1.132.1" it doesn't give these errors.
I also note that the upload/upload/<filename> directory doesn't exist, and the path is probably correct with just a single upload/<filename>
Am I doing something wrong or is this a legitimate problem?
