-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Storage template stuck on default, no errors in logs #14046
Comments
Can you set the log level to verbose, run the job, and post the logs here? Also please share a screenshot of your storage template settings. |
Sure:
|
Hmm, I don't know what happened, but after rebooting the whole PC I had some troubles with my mount order. After fixing them (and removing the bind mount) the storage template migration is now running correctly. So yeah, if someone finds this: if you are using bind mounts, try removing them |
I too am having this problem! Could we reopen please. |
@lpil: are you mounting directories via NFS and/or bind mounts as I was? Share your setup and versions please, maybe there is more to that, then. |
I'm using a docker volume like so:
I am not using NFS or such. After some testing I've found that Immich will use the template if I restart it (Immich, not the whole server) after changing the template in Immich's settings. |
@zackpollard I think your config (re)loading refactor may be the issue here. |
The bug
Getting started with immich and I can't seem to make it apply my storage template with 1.120.1. There are no errors related to running the storage template job in the logs.
The OS that Immich Server is running on
Debian bookworm
Version of Immich Server
v1.120.1
Version of Immich Mobile App
v1.120.1
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
-> the default storage template is used
-> the default storage template is still used
-> the default storage template is still being used
Relevant log output
Additional information
The setup is as follows:
no_root_squash
option enabledThe text was updated successfully, but these errors were encountered: