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"}
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"}