psychofaktory

We are now at Unraid version 7.2.1 and Samba is installed in version 4.23.2. What is the currently recommended way to manage permissions?

All I can contribute in this regard is that the problems I have described above still persist.

Here you go. gsr-m-srv01-diagnostics-20250214-2108.zip

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.

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 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’

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)

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?

Now it's working for me too.

Did the update an tried to set back the connection address from the external go-vod transcoder to internal. Then I got this error which wasn't present before: failed to connect to go-vod: cURL error 7: Failed to connect to 127.0.0.1 port 47788 after 0 ms: Couldn't connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://127.0.0.1:47788/config%2Fconfig/config.

Double checked this. The relative paths are identical in both containers. OK. Thanks to your input I played a bit around this and figured out, that both (host paths and container paths) needs to be identically on both containers. I have now adjusted this and it works!! Thank you very much!

Thanks for the information. Tried this, but got this error: $ apt update Reading package lists... Done E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied) E: Unable to lock directory /var/lib/apt/lists/ $ apt install mesa-va-drivers E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root? The same from unraid console: root@ZWB2-SRV01:~# docker exec -it Nextcloud apt update Reading package lists... Done E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied) E: Unable to lock directory /var/lib/apt/lists/ Double checked this. The relative paths are identical in both containers.

Hi, Currently I have a problem getting hardware transcoding to work. My environment is as follows: Unraid 6.12.10 AMD Ryzen 3 PRO 4350G with Radeon Graphics latest Radeon TOP plugin kilrah/nextcloud-ffmpeg:latest /dev/dri is passed through into the container When trying to play a video, the log file reader says "memories: Transcode failed: Transcoder returned 408 " vainfo says: root@ZWB2-SRV01:~# docker exec -it Nextcloud vainfo error: XDG_RUNTIME_DIR is invalid or not set in the environment. error: can't connect to X server! libva info: VA-API version 1.17.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit In Memories configuration transcoding, and acceleration with VA-API are activated. Every check is listed green. I also tried an external transcoder as described here. Again every check green. But then the log of the go-vod container isn't able to find the file to transcode: 2024/07/01 10:35:06 Starting go-vod 0.2.5 on :47788 2024/07/01 10:35:22 &{Version:0.2.5 Configured:true VersionMonitor:true Bind::47788 FFmpeg:/usr/local/bin/ffmpeg FFprobe:/usr/local/bin/ffprobe TempDir:/tmp/go-vod ChunkSize:3 LookBehind:3 GoalBufferMin:1 GoalBufferMax:4 StreamIdleTime:60 ManagerIdleTime:60 QF:24 VAAPI:true VAAPILowPower:false NVENC:false NVENCTemporalAQ:false NVENCScale:cuda UseTranspose:false ForceSwTranspose:false UseGopSize:false} 2024/07/01 10:35:23 /mnt/Share/PATH TO VIDEO.mp4: No such file or directory 2024/07/01 10:35:23 Error creating manager exit status 1 In this case the log file reader says: "memories Transcode failed: Transcoder returned 500" Any ideas what can be done to get transcoding working?

Wow, many thanks for your tireless efforts. I'm stunned that so little attention has apparently been paid to the Samba configuration by the Unraid team for some time now. Hopefully your meticulous analysis will lead to better attention being paid to this issue in the near future and thus make the whole Samba integration under Unraid more reliable.

Wenn ich diesen Post hier richtig verstehe zielt der dort genannte Workaround mit den beiden NICs auf Konstellationen mit MACVLAN ab. Also wenn z.B. die empfohlene Umstellung auf IPVLAN aus welchen Gründen auch immer noch nicht vollzogen werden konnte. In meinem Fall ist es aber so, dass ich bereits in Version 6.12.3 von MACVLAN auf IPVLAN migriert bin. Dabei gab es keinerlei Probleme. Erst mit dem Wechsel von Version 6.12.3 auf 6.12.4 traten die Probleme auf. Daher denke ich dass der Fehler mit der neuen Version hinzukam und der verlinkte Workaround hier nicht relevant sein sollte. IPVLAN auf MACVLAN zurückzustellen und gleichzeitig den Workaround mit den 2 NICs anzuwenden nur um die neue Version installieren zu können halte ich für nicht praktikabel. Da halte ich das Update auf Version 6.12.4 lieber weiter zurück. Zumal mir aktuell ohnehin kein freier NIC zur Verfügung steht.

Vielen Dank für die Info. Dann hoffe ich, dass ein entsprechender Fix bald von offizieller Seite aus eingepflegt wird und zeitnah ein Update erscheinen wird.

Konnte jemand den Bug zwischenzeitlich nachstellen bzw. wird bereits an einer Lösung gearbeitet? Tatsächlich ist das der Dealbreaker für mich 2 Unraid-Installationen von v6.12.3 auf v6.12.4 anzuheben. Das scheint tatsächlich ein Ansatz zu sein. Unter Unraid OS v 6.12.3 ist noch "EnableIPv6": true gesetzt und es wird auch eine Config für IPv6 ausgegeben wenn ich docker network inspect ausführe.

@matty2k Ich denke das sind zwei gänzlich unterschiedliche Probleme.

Leider nicht. Habe inzwischen schon ein Downgrade auf v6.14.3 durchgeführt. Seitdem funktioniert wieder alles wie gehabt. Nein, diese Informationen werden seit jeher über die Router Advertisements meiner Firewall zugewiesen.

Die Diagnostics habe ich dem Post angehängt: adl15-srv01-diagnostics-20230901-1103.zip Ja. Wobei der Bereich für die MacVLAN-Probleme ja nicht relevant sein dürfte da ich ja bereits in der Vorversion zu IpVLAN migriert bin und damit bis dato auch alles funktioniert hatte.

Hallo, seit dem Update von v6.12.3 auf v6.12.4 können alle Container bei denen neben einer festen IPv4-Adresse auch eine feste IPv6-Adresse hinterlegt ist nicht mehr gestartet werden. Hier ein Beispiel von Adguard-Home: Command execution docker run -d --name='AdGuard-Home' --net='br0' --ip='10.10.10.2' --ip6='2003:a:bdce:ae10:0:10:10:2' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Unraid" -e HOST_CONTAINERNAME="AdGuard-Home" -e 'TCP_PORT_3000'='3000' -e 'UDP_PORT_53'='53' -e 'TCP_PORT_53'='53' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:3000]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/SiwatINC/unraid-ca-repository/master/icons/adguard.png' -v '/mnt/user/appdata/adguard_home/workingdir':'/opt/adguardhome/work':'rw' -v '/mnt/user/appdata/adguard_home/config':'/opt/adguardhome/conf':'rw' 'adguard/adguardhome' 1f248b027ddacacdfbe7b1c3ca84518c35938fa6cef35467bd4bddfeb43fb819 docker: Error response from daemon: user specified IP address is supported only when connecting to networks with user configured subnets. The command failed. In den Docker-Einstellungen ist für das Interface "br0" sowohl ein IPv4-Subnetz als Custom Network angelegt, als auch ein IPv6 Subnetz: IPv4 custom network on interface br0: Subnet: 10.10.10.0/24 Gateway: 10.10.10.1 DHCP pool: not set IPv6 custom network on interface br0: Subnet: 2003:a:bdce:ae10::/64 Gateway: DHCP pool: not set Diese Docker-Einstellungen sind ansonsten noch gesetzt: Docker version: 20.10.24 Docker directory: /mnt/user/system/docker/ Default appdata storage location: /mnt/user/appdata/ Docker LOG rotation: Enabled Docker custom network type: ipvlan Host access to custom networks: Disabled Preserve user defined networks: No Mit exakt diesen Einstellungen hat bis zur Version 6.12.3 alles hervorragend funktioniert. Durch Setzen der Einstellungen "Host access to custom networks" auf "Enabled" und "Preserve user defined networks" auf "Yes" konnte das Problem nicht behoben werden. Wie kann ich die betreffenden Container wieder mit fester IPv4 UND fester IPv6 Adresse starten?

Beneath the setting in your proxy you need to add and configure the variables PHP_MEMORY_LIMIT and PHP_UPLOAD_LIMIT https://help.nextcloud.com/t/increase-max-file-size-on-official-docker-container-not-linuxserver/157748/2

Thanks for the write up on this topic. It sounds like the exact same error pattern as I had described here: https://forums.unraid.net/bug-reports/stable-releases/6103-intermittent-smb-issues-after-6102-upgrade-r2028/?do=findComment&comment=20618 I also think that this is a different additional problem than the one mainly described here. I sincerely hope that the Unraid team will take the information you have provided and finally fix this bug. The bug has been known for several months now. And although this is a business issue, nothing has been done about it yet. Even more: it was even noted that the priority of the bug fix was set very low here. Especially for customers who use Unraid in a business environment, this is an absolute core function with the highest security relevance. The question of how many Unraid users use this function and would benefit from the bug fix is irrelevant. Therefore, immediate bug fixing should be absolutely in the interest of the Unraid team.

Can anybody help me with this? Has anyone a working setup with guacamole docker an LDAPS with a Windows Domain Controller? I would also like to change the name of the guacamole printer in the RDP sessions. How could this be accomplished? I also noticed that the clipboard does not seem to work via RDP. What could be the problem here?