[Alvaro Cordero Retana]

Hello, I have a newly installed OTOBO 10.1.x with ArticleStorageBackend set to FS on CentOS 8 Stream. All articles are readable and fine, but when it has to create the new folder for the day, it gives permissions otobo.otobo thus, it becomes unreadable by the web user and system starts giving internal server errors.

If we run /opt/otobo/bin/otobo.SetPermissions.pl it sets its permissions or if we manually change them to otobo.apache it works, but it shouldn’t happen. Why are the new directory’s being created as otobo otobo instead of otobo apache?

Best Regards

[Alvaro Cordero Retana]

Hello, I have a newly installed OTOBO 10.1.x with ArticleStorageBackend set to FS on CentOS 8 Stream. All articles are readable and fine, but when it has to create the new folder for the day, it gives permissions otobo.otobo thus, it becomes unreadable by the web user and system starts giving internal server errors.

If we run /opt/otobo/bin/otobo.SetPermissions.pl it sets its permissions or if we manually change them to otobo.apache it works, but it shouldn’t happen. Why are the new directory’s being created as otobo otobo instead of otobo apache?

Best Regards

[Alvaro Cordero Retana]

I found out that if the Path for the article Storage is not under common otobo path (opt/otobo/var/articles) it will not by default set the sticky bit on the directories, so it won’t inherit the group permissions for the web server. Setting the sticky bit to it, will make it work as expected and the new directories will inherit the group permissions.

Hope this helps someone else.

[Autor]

Beiträge