-
-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 IMMICH - Failed to write /share/immich/encoded-video/.immich: #1624
Comments
I found out that after creating the file manually the error message changed fom "Failed to read" of "Failed to write" created the file with the following command: touch encoded-video/.immich [Nest] 3654 - 11/04/2024, 1:42:47 PM ERROR [Api:StorageService] Failed to read /share/immich/encoded-video/.immich: Error: ENOENT: no such file or directory, open '/share/immich/encoded-video/.immich' [Nest] 3621 - 11/04/2024, 1:42:40 PM ERROR [Api:StorageService] Failed to write /share/immich/encoded-video/.immich: Error: EACCES: permission denied, open '/share/immich/encoded-video/.immich' |
i'm a liitle further. i ran "chown -R 1000:1000 media/immich/ " that did not solve the issue. But when i set PUID 0, PGID 0 in the configuration options the addon started and the folder sturcture is made automatically. |
Hi thanks for the coffees! I have a big week at work and will look in a couple days! Nice investigational process so far |
I've had the same issues that last few days and might have to add something. |
You could try :
|
1st bullet - I did, all files and folders are owned by 1000. Reacting to "TScj92", I'm using the same database time after time. I do not throw away the database and start over. |
To be totally clear. Im now running the addon with PUID 0 and PGID 0. This works supposably well. |
Honestly not much in my opinion, I'm running all my addons as root on my system. The most important element that I see is to prevent the app from accidentally accessing & modifying stuff it shouldn't. But you can control that by selecting what data you mount in HA. The other element about data safety (avoiding the app to "check" your files) is a bit moot as anyway all containers runs as root ; only the app itself (so immich) is run with a different user. Well the most important is that it's working for you!! |
@niekbruggeman are you connecting to a share with or without password? |
I'm using CIFS protected with username and password. |
Description
Hi Alex and developers,
I bought you two coffee so that you have something to drink while looking into my issue.
I am having trouble with a fresh install of the Immich-addon (v1.119.1) within my HA instance (latest stable).
After setting up the required configuration options, I get the following error I'm not able solve.
\share\immich is a CIFS share mounted on my synology NAS.
When i start the addon the share is empty, containing no folders and no files.
After starting the addon, i see one folder \library is automatically created by the addon.
I double and triple checked the access-rights of the addon and on the file share.
The addon is running with the highest privileges, and the user used for mounting the share is owner of the mounted share having full read and write access on files folders an sub files and folders.
I can only assume where are sufficient write privileges as the \library folder is created by the addon.
While searching for the error i found that there was a similar issue with v1.115.0 last month.
immich-app/immich#12798
The solution there was to create the necessary folder structure and .immich files by hand.
This was not a solution in my situation with the addon. (used folder stucture below)
Then I tried placing the data_location: not on a mounted drive, but on local storage of my HA instance.
I set data_location: \media\immichlocal. This resulted in the same behavior.
As you can see, only the folder \library is created. And the error remains.
I'm unable to start the addon.
As last resort I tried installing the official docker image (in a totally different docker-contrainer manager, not as an addon) and mounting the same location. I ran into the same issue, but with the official docker image I was able to workaround the error by creating the folder structure by hand als below (as mentioned in /discussions/12798) .
After creation the structure the docker image in de containermanager started and functioned like supposed.
Like i mentioned above, this was not a workaround with the immich addon from your repository.
With the most basic installation and new installation from scratch, I'm not able to successfully start the addon.
So there for i reported a bug, but it is always possible that i'm doing something wrong.
Please advise. Thanks in advance.
I will reply on questions and reportback test results ASAP.
Reproduction steps
Addon Logs
Architecture
No response
OS
No response
The text was updated successfully, but these errors were encountered: