- Urgent
Hi everyone,
Based on my post:
I'm creating a bug report here as requested by @JorgeB.
My goal was to have 1 physical server running Unraid hosting my Server 2019 domain controller that would service all the devices on my network, and authenticate shares from my zfs pool via AD/LDAP.
Unfortunately I experienced long freeze-ups of the Unraid UI under specific circumstances that were around 15 min long.
Things I have learned:
On Unraid, under Settings-SMB-Active Directory Settings, you need to have the DC powered up to join the domain (obviously), however in Unraid, you cannot edit/join AD while the Array is running, which means you can't have the DC VM running. Thus joining Unraid to an AD VM hosted on Unraid won't work, since I will never be able to reach the DC that is a powered off VM in Unraid.
A suggestion was made in an older post to spin up a 2nd DC on another VM host and join that one. This works to get Unraid to join the domain, however it comes at a cost. You must keep that external DC up. If not, you end up with the 15-ish min hang time I was experiencing. By having an external AD running, Unraid is responsive and does not exhibit the aforementioned freezing.
For some reason when
- starting or stopping the array
- loading the "VM Manager" settings window,
- loading the VMS page,
- starting or stopping the VM DC,
Unraid appears to try to reach the DC, and (I'm speculating here)...waits for the DC to time out for a reaaaaaly long time. I'm unsure why Unraid would need to reach out to the DC for any of these operations? Despite the hang time with the only DC being an Unraid VM, once the timeout values expire, and you get the array up and the DC VM running, things run without issue. Despite under Settings-SMB-Active Directory Settings showing as not domain joined, users are indeed authenticated against AD when accessing shares with only the 1 VM DC running. Once you power off (I think reboot too...will have to test) the DC VM, you're back into the 15 min of hang time. Same occurs if trying to start or stop the array, start or stop the DC VM, or load the "VM Manager" settings window, or the VMS page.
Perhaps this could be addressed in a future version, adding a user adjustable timeout value for AD requests, and looking into why Unraid needs the DC to start/stop the array, start the VM, or load those 2 pages.
I'm unsure which priority to assign here. For my use case it is pretty urgent, but I understand not many users leverage AD.
Thanks,
Cal.