Directory Users could not be retrieved, multiple domain controllers

Status
Not open for further replies.

Dotty

Contributor
Joined
Dec 10, 2016
Messages
125
Does anybody knows how FreeNAS handles the failure of a primary domain controller?
In my case, as soon as I shut down the primary DC, FreeNAS starts giving errors if I try to change permissions on a dataset previously configured with Domain users.
Both domain controllers can be seen from FreeNAS (I can ping, both are running DNS and FreeNAS has them both added as nameserver#)

I dont understand why it doesnt work well, the point of having multiple nameservers is so that the client (in this case FreeNAS) can perform all the authentication/resolution when one DC is down.



Dec 26 12:15:04 freenas6 smbd: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Dec 26 12:15:04 freenas6 notifier: Waiting for PIDS: 20761.
Dec 26 12:15:04 freenas6 notifier: Starting mdnsd.
Dec 26 12:22:58 freenas6 manage.py: [common.pipesubr:66] Popen()ing: klist
Dec 26 12:23:19 freenas6 manage.py: [common.freenasusers:346] Directory Users could not be retrieved: {'desc': "Can't contact LDAP server"}
Dec 26 12:23:19 freenas6 manage.py: [common.pipesubr:66] Popen()ing: klist
Dec 26 12:23:39 freenas6 manage.py: [common.freenasusers:229] Directory Groups could not be retrieved: {'desc': "Can't contact LDAP server"}
Dec 26 12:23:39 freenas6 manage.py: [common.pipesubr:66] Popen()ing: klist
Dec 26 12:24:00 freenas6 manage.py: [common.pipesubr:66] Popen()ing: klist
Dec 26 12:24:32 freenas6 manage.py: [common.pipesubr:66] Popen()ing: klist
Dec 26 12:24:33 freenas6 manage.py: [common.pipesubr:66] Popen()ing: klist
Dec 26 12:24:35 freenas6 manage.py: [common.pipesubr:66] Popen()ing: klist
Dec 26 12:24:52 freenas6 manage.py: [common.freenasusers:346] Directory Users could not be retrieved: {'desc': "Can't contact LDAP server"}
Dec 26 12:25:02 freenas6 manage.py: [common.freenasusers:346] Directory Users could not be retrieved: {'desc': "Can't contact LDAP server"}
Dec 26 12:25:12 freenas6 manage.py: [common.freenasusers:346] Directory Users could not be retrieved: {'desc': "Can't contact LDAP server"}
 

Dotty

Contributor
Joined
Dec 10, 2016
Messages
125
And by the way, I just realized that if the primary domain goes down, there is no DNS resolution on the FreeNAS box. Nothing.
Even when I have multiple nameservers configured.
Unless this is "user error" on my side, looks like if one of the DNS is down, then FreeNAS is crippled.
This DNS issue matters a lot, 4 of my jails depend on DNS, specially backups to AWS S3.

I wonder if Im doing anything wrong.
 
D

dlavigne

Guest
Please create a bug report at bugs.freenas.org and post the issue number here.
 
Status
Not open for further replies.
Top