Library folder permission set to 711 instead of 755
Hello all,
The backup script I run as a non-root cron job failed because of an inaccessible folder. Upon investigating, I noticed that said folder (2021-09-08) had permissions set to 711 instead of 755 like all others. The contents of this folder seem to be fine. This folder was automatically created by Immich when assets were uploaded from the web interface.
I've made no changes to the template docker-compose file or .env files. Version 1.76.1
Why would this happen, and how can I prevent it in the future?
7 Replies
There are quite a few Redis and Postgres timeouts in the microservices log.
I think it's possible the culprit might be the "missing file in uploads folder" near the beginning of the logs.
I am, however, completely at sea as to how to pinpoint why this may have happened. All assets were uploaded from the web interface.
i’m guessing it’s related to the umask applied to folder permissions, but i don’t know why exactly it would be different for this folder.
Thank you, Mert. I'm hoping that https://github.com/immich-app/immich/pull/3850 might've fixed it. I'll open a github issue if it happens again and I can find some way to consistently reproduce the bug.
Can you reproduce this? I think the only place immich makes a new directory doesn't pass any mask, so the default should be 755
@jrasm91 I cannot reproduce this. I have spent quite a bit of time wondering how this could've happened, and came up with a blank. Hence why I posted my entire microservices log in the hopes that a more experienced Linux ninja might be able to figure it out.
I will keep an eye out for this bug in the future, and open an issue on github if it happens again.
Sounds good. It does seem pretty strange. Keep us posted.