Prevent stalled boot if DC is unavailable
Description
Problem/Justification
Impact
relates to
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Andrew Walker April 23, 2019 at 4:02 PM
The AD side of this issue is fixed in https://github.com/freenas/freenas/pull/2836
Once the server is joined to AD a subsequent reboot will only cause FreeNAS to kinit and restart samba. In case of the DC being down, samba's winbindd_cm will detect when the server comes back up and eventually recover.
Metis IT April 16, 2019 at 9:34 PM
just stumbled across this, wanting to set up a fresh DC with 11.2-u3. didnt find new info elsewhere really.
reading that the DC service / functionality will be retired, what is your take on the best way to set this up now? create a BSD jail myself for the DC? or better a debian VM?
or do it with freenas natively a wait for a magic migration? (if ever?)
should domain controller service be disabled in 11.2 already so new DCs don't get created?
Andrew Walker March 17, 2019 at 10:31 AM
This one will require further investigation. Behavior when a DC is semi-hung is somewhat different from when it is fully powered off. The DC in question is providing DNS for the FreeNAS server. Fundamentally, it's a bad idea to have VMs hosted on a server provide DNS for the server. I don't think we can fully avoid pain here.
William Gryzbowski March 14, 2019 at 7:03 PM
Ah yes, sorry, I totally misread that.
Kevan Brown March 14, 2019 at 6:22 PM
William Grzybowski wrote:
> We are going to retire the DC service as builtin service in freenas for 11.3+ so this will be a non-issue.
>
> I know its not what you would like to hear but maintaining DC on our own has been more trouble then its worth. We plan on having it as a separate plugin instead.
Are we talking about the same thing here? I'm unsure that we are. I'm not talking about FreeNAS acting as a Domain Controller itself. Rather I'm speaking to the domain join capability in FreeNAS via the SMB service, which is used for Active Directory domain authentication and ACLs on FreeNAS resources.
Details
Details
Assignee
Andrew WalkerReporter
Kevan BrownComponents
Fix versions
Priority
Low
More fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
If something happens to the Active Directory DC FreeNAS is using in which the DC becomes semi-hung, the FreeNAS OS startup hangs indefinitely after the smb4.conf load.
Consider the following scenario: Your domain controllers are VMs running on VMware ESXi. Something happens to the FreeNAS OS or hardware that causes storage to become unavailable to ESXi. ESXi keeps the DC VM in a powered on state, and it is semi-hung due to lack of underlying storage. When you reboot or power cycle FreeNAS, it will hang indefinitely after loading smb4.conf. If you power off the semi-hung DC VM and reboot FreeNAS, it will make it past the smb4.conf stage and show the errors related to inability to find a domain controller and continue the boot process as expected.