January 8, 20251 yr I would like to test the new settings as I am still affected by the problems described here. The help texts for the various options were not very helpful for me. Are there any recommendations regarding the settings for connecting to a simple Windows Server 2019 Active Directory with only one DC? For example, should I choose “rid”, “ad”, or “tdb” as the domain backend database, and rather specify “tdb”, or “ldap” as backend database?
January 8, 20251 yr Author 3 minutes ago, psychofaktory said: I would like to test the new settings as I am still affected by the problems described here. The help texts for the various options were not very helpful for me. Are there any recommendations regarding the settings for connecting to a simple Windows Server 2019 Active Directory with only one DC? For example, should I choose “rid”, “ad”, or “tdb” as the domain backend database, and rather specify “tdb”, or “ldap” as backend database? I recommend you use the defaults as they are the best for general use. TIt should work fine for you. The other database options are used for special needs that an Unraid user will not generally need. I only included them for completeness. Click on the link in the page for more information about setting up AD on Samba. Please let me know if the new settings will work for you. We would like to resolve the issues with AD.
January 8, 20251 yr 1 hour ago, dlandon said: Please let me know if the new settings will work for you. After some initial tests, the new plugin seems to work very well. My initial environment: Unraid 6.12.13 Active Directory Plugin v2024.12.28 Joined to a Windows Server 2019 Active Directory My goal: Shares created in Unraid are to be used as shares in the Windows environment and assigned individual rights for specific AD groups. Simultaneously, the shares are to be integrated as external storage in a Nextcloud Docker installed under Unraid. The data contained therein should be equally accessible and editable for both Windows users and Nextcloud users. What I did: I set the recommended default values under the Active Directory Extras. I upgraded from Unraid 6.12.13 to 6.12.14 and rebooted the system. I used the “Fix Common Problems” plugin to specify which directories should be excluded from resetting folder permissions. Of particular note here are the Nextcloud data directory and the appdata directory. I then reset the permissions for the shares via “Tools” -> “Docker Safe New Perms”. I then cleaned up the remnants of the directory permissions from previous attempts using “setfacl -bn -R /mnt/user/*share*”. I then logged into the Windows domain controller as an administrator and took ownership of the relevant shares. After taking ownership, I removed all existing permission entries via the “Security” tab in Windows Explorer and only added the desired Windows users and adjusted the permissions according to my wishes. Result: The authorizations can now be assigned granularly without losing access to the shares from Windows. At the same time, it is possible to edit the relevant directories from Nextcloud. For directories created under Nextcloud within the shares, however, the permissions of the parent folders are not inherited. This means, for example, that deleting such folders under Windows is only possible if ownership has been transferred again beforehand. During my tests, several error messages also appeared in the log: Jan 8 17:40:15 UNRAID-SERVER rpcd_classic[17126]: [2025/01/08 17:40:15.145747, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 17:40:15 UNRAID-SERVER rpcd_classic[17126]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 17:41:18 UNRAID-SERVER rpcd_classic[17126]: [2025/01/08 17:41:18.518610, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 17:41:18 UNRAID-SERVER rpcd_classic[17126]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 17:42:52 UNRAID-SERVER rpcd_classic[22613]: [2025/01/08 17:42:52.993376, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 17:42:52 UNRAID-SERVER rpcd_classic[22613]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 17:45:51 UNRAID-SERVER rpcd_classic[28754]: [2025/01/08 17:45:51.961097, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 17:45:51 UNRAID-SERVER rpcd_classic[28754]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 17:47:03 UNRAID-SERVER rpcd_classic[28754]: [2025/01/08 17:47:03.209800, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 17:47:03 UNRAID-SERVER rpcd_classic[28754]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 17:47:40 UNRAID-SERVER rpcd_classic[28754]: [2025/01/08 17:47:40.500857, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 17:47:40 UNRAID-SERVER rpcd_classic[28754]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 17:50:32 UNRAID-SERVER rpcd_classic[28754]: [2025/01/08 17:50:32.989898, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 17:50:32 UNRAID-SERVER rpcd_classic[28754]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 17:50:40 UNRAID-SERVER flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Jan 8 17:52:49 UNRAID-SERVER smbd[6288]: [2025/01/08 17:52:49.935118, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 17:52:49 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10001, gid=10015, 4 groups: 10015 10005 10006 10007 Jan 8 17:52:54 UNRAID-SERVER smbd[6288]: [2025/01/08 17:52:54.750373, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 17:52:54 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10001, gid=10015, 4 groups: 10015 10005 10006 10007 Jan 8 17:53:07 UNRAID-SERVER smbd[6288]: [2025/01/08 17:53:07.558010, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 17:53:07 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10001, gid=10015, 4 groups: 10015 10005 10006 10007 Jan 8 17:53:07 UNRAID-SERVER smbd[6288]: [2025/01/08 17:53:07.558387, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 17:53:07 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10001, gid=10015, 4 groups: 10015 10005 10006 10007 Jan 8 17:57:08 UNRAID-SERVER smbd[6288]: [2025/01/08 17:57:08.563687, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 17:57:08 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 17:57:08 UNRAID-SERVER smbd[6288]: [2025/01/08 17:57:08.564307, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 17:57:08 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 17:57:08 UNRAID-SERVER smbd[6288]: [2025/01/08 17:57:08.564755, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 17:57:08 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 17:57:08 UNRAID-SERVER smbd[6288]: [2025/01/08 17:57:08.565285, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 17:57:08 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 17:57:15 UNRAID-SERVER rpcd_classic[19851]: [2025/01/08 17:57:15.132291, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 17:57:15 UNRAID-SERVER rpcd_classic[19851]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:01:30 UNRAID-SERVER rpcd_classic[28454]: [2025/01/08 18:01:30.934558, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:01:30 UNRAID-SERVER rpcd_classic[28454]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: [2025/01/08 18:01:58.328534, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: [2025/01/08 18:01:58.328744, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: [2025/01/08 18:01:58.329036, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: [2025/01/08 18:01:58.329577, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: [2025/01/08 18:01:58.331757, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: [2025/01/08 18:01:58.332609, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: [2025/01/08 18:01:58.333336, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: [2025/01/08 18:01:58.334069, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: [2025/01/08 18:01:58.341275, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:01:58 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:01:59 UNRAID-SERVER smbd[6288]: [2025/01/08 18:01:59.415531, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:01:59 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:02:00 UNRAID-SERVER smbd[6288]: [2025/01/08 18:02:00.694283, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:02:00 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:02:00 UNRAID-SERVER smbd[6288]: [2025/01/08 18:02:00.997567, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:02:00 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: [2025/01/08 18:02:01.000125, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: [2025/01/08 18:02:01.000342, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: [2025/01/08 18:02:01.001105, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: [2025/01/08 18:02:01.002564, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: [2025/01/08 18:02:01.003950, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: [2025/01/08 18:02:01.004296, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: [2025/01/08 18:02:01.004724, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: [2025/01/08 18:02:01.010698, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:02:01 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:02:02 UNRAID-SERVER smbd[6288]: [2025/01/08 18:02:02.071838, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:02:02 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:02:02 UNRAID-SERVER smbd[6288]: [2025/01/08 18:02:02.938790, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) Jan 8 18:02:02 UNRAID-SERVER smbd[6288]: chdir_current_service: vfs_ChDir(/mnt/user/Backup) failed: Permission denied. Current token: uid=10000, gid=10000, 13 groups: 10000 10008 10001 10009 10010 10011 10012 10013 10005 10006 10007 10003 10002 Jan 8 18:02:21 UNRAID-SERVER rpcd_classic[28454]: [2025/01/08 18:02:21.754213, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:02:21 UNRAID-SERVER rpcd_classic[28454]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:02:44 UNRAID-SERVER rpcd_classic[28454]: [2025/01/08 18:02:44.972566, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:02:44 UNRAID-SERVER rpcd_classic[28454]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:03:03 UNRAID-SERVER rpcd_classic[28454]: [2025/01/08 18:03:03.354716, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:03:03 UNRAID-SERVER rpcd_classic[28454]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:03:18 UNRAID-SERVER rpcd_classic[28454]: [2025/01/08 18:03:18.178304, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:03:18 UNRAID-SERVER rpcd_classic[28454]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:04:12 UNRAID-SERVER rpcd_classic[28454]: [2025/01/08 18:04:12.665815, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:04:12 UNRAID-SERVER rpcd_classic[28454]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:05:06 UNRAID-SERVER rpcd_classic[28454]: [2025/01/08 18:05:06.513927, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:05:06 UNRAID-SERVER rpcd_classic[28454]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:05:58 UNRAID-SERVER rpcd_classic[28454]: [2025/01/08 18:05:58.352066, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:05:58 UNRAID-SERVER rpcd_classic[28454]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:08:00 UNRAID-SERVER rpcd_classic[28454]: [2025/01/08 18:08:00.467278, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:08:00 UNRAID-SERVER rpcd_classic[28454]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:09:21 UNRAID-SERVER rpcd_classic[12054]: [2025/01/08 18:09:21.442056, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:09:21 UNRAID-SERVER rpcd_classic[12054]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:09:29 UNRAID-SERVER rpcd_classic[12054]: [2025/01/08 18:09:29.150278, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:09:29 UNRAID-SERVER rpcd_classic[12054]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:10:02 UNRAID-SERVER rpcd_classic[12054]: [2025/01/08 18:10:02.214329, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:10:02 UNRAID-SERVER rpcd_classic[12054]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:10:35 UNRAID-SERVER rpcd_classic[12054]: [2025/01/08 18:10:35.153151, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:10:35 UNRAID-SERVER rpcd_classic[12054]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:11:20 UNRAID-SERVER rpcd_classic[12054]: [2025/01/08 18:11:20.813715, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:11:20 UNRAID-SERVER rpcd_classic[12054]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:11:49 UNRAID-SERVER rpcd_classic[12054]: [2025/01/08 18:11:49.153780, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:11:49 UNRAID-SERVER rpcd_classic[12054]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:12:15 UNRAID-SERVER rpcd_classic[12054]: [2025/01/08 18:12:15.016505, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:12:15 UNRAID-SERVER rpcd_classic[12054]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:12:37 UNRAID-SERVER rpcd_classic[12054]: [2025/01/08 18:12:37.023356, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:12:37 UNRAID-SERVER rpcd_classic[12054]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied) Jan 8 18:12:57 UNRAID-SERVER rpcd_classic[12054]: [2025/01/08 18:12:57.175650, 0] ../../source3/lib/sharesec.c:161(share_info_db_init) Jan 8 18:12:57 UNRAID-SERVER rpcd_classic[12054]: Failed to open share info database /var/lib/samba/share_info.tdb (Permission denied)
January 8, 20251 yr Author The share /mnt/user/Backup has a permission issue. Check your permissions, but you might try this: chmod -R 770 /mnt/user/Backup chown -R 10000:10000 /mnt/user/Backup The var/lib/samba/ permissions can probably be fixed with this: chmod 644 /var/lib/samba/share_info.tdb chown root:samba /var/lib/samba/share_info.tdb If that fixes the permission, I'll add that to the plugin to fix this when it installs.
January 8, 20251 yr 1 hour ago, dlandon said: The share /mnt/user/Backup has a permission issue. Check your permissions, but you might try this: I have noticed that the error in the log files always occurs when I try to access the 'backup' share as the 'administrator' user. It is completely correct that access is denied because I have entered the user 'backup' as the owner and the administrator should not have authorization to access this share. Perhaps there is a way to avoid the log being flooded with such entries in such cases. 1 hour ago, dlandon said: The var/lib/samba/ permissions can probably be fixed with this: chmod 644 /var/lib/samba/share_info.tdb chown root:samba /var/lib/samba/share_info.tdb If that fixes the permission, I'll add that to the plugin to fix this when it installs. This message also only appeared if an attempt was made to access the 'backup' share with the unauthorized 'administrator'. chmod 644 /var/lib/samba/share_info.tdb This command was enough to stop the error message from appearing. When I tried to enter the second command I got the following error message: chown: invalid group: ‘root:samba’ Edited January 8, 20251 yr by psychofaktory
January 8, 20251 yr Author 8 minutes ago, psychofaktory said: I have noticed that the error in the log files always occurs when I try to access the 'backup' share as the 'administrator' user. It is completely correct that access is denied because I have entered the user 'backup' as the owner and the administrator should not have authorization to access this share. Perhaps there is a way to avoid the log being flooded with such entries in such cases. This message also only appeared if an attempt was made to access the 'backup' share with the unauthorized 'administrator'. chmod 644 /var/lib/samba/share_info.tdb This command was enough to stop the error message from appearing. When I tried to enter the second command I got the following error message: chown: invalid group: ‘root:samba’ Thanks for the feedback. I'll add the permission adjustment to the plugin installation. This probably occurs when restoring the database from the flash as that would reset the permissions. I don't think Unraid has a group "root:samba", but I think you might be set now. 10 minutes ago, psychofaktory said: I have noticed that the error in the log files always occurs when I try to access the 'backup' share as the 'administrator' user. It is completely correct that access is denied because I have entered the user 'backup' as the owner and the administrator should not have authorization to access this share. Perhaps there is a way to avoid the log being flooded with such entries in such cases. I'll have to take a look, but I'm pleased that things seem to be working for you.
January 15, 20251 yr Today I updated from 6.12.14 to version 7.0.0. Unfortunately, after the restart, all permissions under /mnt/user/ were reset to the AD initial owner and AD initial group defined in the Active Directory settings. I then clicked “Clear Cache” in the Active Directory Extras. Now, instead of the names for owner and group, only numerical sequences (user 1938817524 and group 1938817536) were displayed. In Windows, the individual authorizations that I had assigned were still available. However, additional users and groups with the authorization “Full access” or “None” had been added (Everyone, Creator-owner, User, etc...). Instead of the administrator, Unix “User\1938817524” was specified as the owner, so that I first had to take over the ownership again to restore the authorizations. So there still seems to be some mess here.
January 15, 20251 yr Author 2 hours ago, psychofaktory said: Today I updated from 6.12.14 to version 7.0.0. Unfortunately, after the restart, all permissions under /mnt/user/ were reset to the AD initial owner and AD initial group defined in the Active Directory settings. I then clicked “Clear Cache” in the Active Directory Extras. Now, instead of the names for owner and group, only numerical sequences (user 1938817524 and group 1938817536) were displayed. In Windows, the individual authorizations that I had assigned were still available. However, additional users and groups with the authorization “Full access” or “None” had been added (Everyone, Creator-owner, User, etc...). Instead of the administrator, Unix “User\1938817524” was specified as the owner, so that I first had to take over the ownership again to restore the authorizations. So there still seems to be some mess here. I believe this may be related to the restoration of the databases. I've released an update that will restart samba when the databases are restored.
January 19, 20251 yr Plugin works, but seeing a log message during bootup - not sure if this is causing any actual issue or not...
January 29, 20251 yr Author 13 hours ago, shwa87 said: The above error has returned; line 170 now. Update the plugin. It's a different error, but should be fixed this time.
February 14, 20251 yr Unfortunately, the situation is still anything but satisfactory. After restarting the Unraid server, the permissions in the /mnt/user directory were all reset to owner “administrator” and group “domain-user”. In other words, the values that were set in the Active Directory settings in the SMB options as initial owner and initial group. These should also only be initial values and not be reapplied at every start, as there are also shares in the directory that require different permissions. After the restart, I also noticed that the shares stored as external storage in the Nextcloud Docker, which are also used as shares in Windows, are now no longer accessible in Nextcloud. Only when I granted full access to the “Everyone” group in Windows was it possible to access the folders in Nextcloud again. However, this makes the meaningfulness of authorization concepts completely obsolete. How can authorizations be assigned in an AD connection so that individual authorizations can be assigned within the shares under Windows, but these can still be integrated into Docker containers as volumes? Until Unraid version 6.9.2, this was still possible and my original reason for using Unraid as a system in the first place.
February 14, 20251 yr Author 1 hour ago, psychofaktory said: Unfortunately, the situation is still anything but satisfactory. After restarting the Unraid server, the permissions in the /mnt/user directory were all reset to owner “administrator” and group “domain-user”. In other words, the values that were set in the Active Directory settings in the SMB options as initial owner and initial group. These should also only be initial values and not be reapplied at every start, as there are also shares in the directory that require different permissions. After the restart, I also noticed that the shares stored as external storage in the Nextcloud Docker, which are also used as shares in Windows, are now no longer accessible in Nextcloud. Only when I granted full access to the “Everyone” group in Windows was it possible to access the folders in Nextcloud again. However, this makes the meaningfulness of authorization concepts completely obsolete. How can authorizations be assigned in an AD connection so that individual authorizations can be assigned within the shares under Windows, but these can still be integrated into Docker containers as volumes? Until Unraid version 6.9.2, this was still possible and my original reason for using Unraid as a system in the first place. Post your diagnostics and I'll look into it.
February 14, 20251 yr 1 minute ago, dlandon said: Post your diagnostics and I'll look into it. Here you go. gsr-m-srv01-diagnostics-20250214-2108.zip
March 26, 20251 yr seeing this in my fix common problems plugin today: The plugin active.directory.plg is not known to Community Applications and is possibly incompatible with your server
March 27, 20251 yr I installed this plugin on two of my Unraid system and wanted to install it on another system but can't find it. I am also pretty sure I did not use the URL install so am I dreaming, or this plugin is no longer available in the CA ? 😔
April 1, 20251 yr Is there any kind of update to this? Not in CA, and The plugin active.directory.plg is not known to Community Applications and is possibly incompatible with your server? Edited April 1, 20251 yr by Cloggy error message added
April 16, 20251 yr Does anyone have any updates for this? It looks like the whole project was deleted by @dlandon.
April 17, 20251 yr All I can contribute in this regard is that the problems I have described above still persist.
April 20, 20251 yr @dlandon Have you abandoned this plugin/project? Should users remove it or what is the status? Please provide some definitive commentary - if you have ended development - that's totally your choice - and I support that if that's what you chose to do, but confirmation of that would be awesome. Thanks!
Saturday at 03:24 AM5 days Hi all,Since there's been no response here regarding the plugin's status — including direct questions about it — since dlandon's last post on February 14, 2025, and the original GitHub repository has since been removed, I've forked the plugin to keep it working and maintained on current Unraid releases:GitHubGitHub - joshmans/unraid-active-directory-extrasContribute to joshmans/unraid-active-directory-extras development by creating an account on GitHub.All credit for the original work goes to dlandon — this is purely to keep it functional and maintained, not a rewrite or a replacement of his efforts. If he resumes maintenance of the original, I'd encourage everyone to go back to using his version.Since forking, the following have been addressed:- Per-file TDB backup retention (the original could silently drop the only backup of a less-frequently-updated database)- Atomic staging for TDB backup/restore, and integrity validation on restore with fallback to an older generation if needed- Settings page errors (Apply, Clear Cache) now actually show up in the GUI instead of failing silently- Live AD join status check (replacing the built-in Unraid indicator, which is frequently inaccurate)- Enabled and validated the Domain Range / Backend Range fields (previously present but disabled)- Removed the incomplete LDAP backend option from the dropdown (it was never fully implemented)- Confirmation prompt before Clear Cache, since it restarts Samba and drops active SMB connections- Configurable TDB backup location (flash or array/cache, not just flash)- Package integrity now uses SHA256, and the plugin manifest has an upper Unraid version bound (tested through 7.3.2)Current version is 2026.09.04, tested on Unraid 7.3.2.For bugs, questions, or feature requests going forward, please use GitHub Issues on the repo linked above rather than this thread:https://github.com/joshmans/unraid-active-directory-extras/issuesPlease note that I did test this completely on my system, but I welcome further testing.Thanks to dlandon for building this in the first place.I will submit to CA soon.
Tuesday at 02:15 PM1 day Author The problem I was having with this plugin is I had no way to test the plugin since I don't have a Windows server. As you found out, there was a lot lacking and some bugs. I took it down because I didn't want anyone using it in it's current form with all the issues and bugs I had no way to reasonably resolve.I will make my GitHub Public Archive and add a link to your GitHub with a note the work is carrying on there.Thanks for the recognition of the work I did. Feel free to carry on the effort.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.