Wrong permission on samba folders

[Diondk]

Hi,

 

After every reboot the samba permission on the following folders are reset to 0755 instead of 0700. And then samba will not start. 

 

Any one can point me in the right direction to fix this ?

I have put the permissions to 0700 now but after a reboot it will be back to 0755

 

See also the error code of samba below.

 

Aug 22 11:21:51 Tower wsdd2[5764]: 'Terminated' signal received.
Aug 22 11:21:51 Tower wsdd2[5764]: terminating.
Aug 22 11:21:56 Tower smbd[8603]: [2022/08/22 11:21:56.505823,  0] ../../source3/smbd/server.c:1734(main)
Aug 22 11:21:56 Tower smbd[8603]:   smbd version 4.15.7 started.
Aug 22 11:21:56 Tower smbd[8603]:   Copyright Andrew Tridgell and the Samba Team 1992-2021
Aug 22 11:21:56 Tower nmbd[8607]: [2022/08/22 11:21:56.540409,  0] ../../source3/nmbd/nmbd.c:901(main)
Aug 22 11:21:56 Tower nmbd[8607]:   nmbd version 4.15.7 started.
Aug 22 11:21:56 Tower nmbd[8607]:   Copyright Andrew Tridgell and the Samba Team 1992-2021
Aug 22 11:21:56 Tower wsdd2[8621]: starting.
Aug 22 11:21:56 Tower winbindd[8622]: [2022/08/22 11:21:56.653910,  0] ../../source3/winbindd/winbindd.c:1722(main)
Aug 22 11:21:56 Tower winbindd[8622]:   winbindd version 4.15.7 started.
Aug 22 11:21:56 Tower winbindd[8622]:   Copyright Andrew Tridgell and the Samba Team 1992-2021
Aug 22 11:21:56 Tower winbindd[8626]: [2022/08/22 11:21:56.659024,  0] ../../source3/winbindd/winbindd_cache.c:3085(initialize_winbindd_cache)
Aug 22 11:21:56 Tower winbindd[8626]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Aug 22 11:21:56 Tower winbindd[8626]: [2022/08/22 11:21:56.659592,  0] ../../lib/util/util.c:336(directory_create_or_exist_strict)
Aug 22 11:21:56 Tower winbindd[8626]:   invalid permissions on directory '/var/lib/samba/winbindd_privileged': has 0755 should be 0750
Aug 22 11:21:56 Tower winbindd[8626]: [2022/08/22 11:21:56.659618,  0] ../../lib/util/become_daemon.c:119(exit_daemon)
Aug 22 11:21:56 Tower winbindd[8626]:   exit_daemon: daemon failed to start: Winbindd failed to setup listeners, error code 32

 

Kind Regards,

Dion

[itimpi]

The thing I could see causing that is a plugin that installs something into a folder along that path and has been built slightly incorrectly so is over-riding the Unraid default ones   You could check this by booting in Safe Mode (which suppresses loading plugins) to see if it occurs then.  If so it is going to be a case of identifying the culprit.