SOLVED Problem starting AD service but config all good

Status
Not open for further replies.

Alex9779

Dabbler
Joined
Nov 23, 2012
Messages
10
Hi,

I recently had a problem when trying to join my FreeNAS to my new created Samba4 AD domain. After some configuration issues all seemed fine, the confige saved well but the service did not start. After enabling "Verbose Logging" the log showed me:

Code:
Jan  4 21:08:28 nas02 ActiveDirectory: /usr/sbin/service ix-activedirectory quietstart
Jan  4 21:08:28 nas02 ActiveDirectory: AD_init: config exists, loading values from /etc/ActiveDirectory/config
Jan  4 21:08:28 nas02 ActiveDirectory: activedirectory_start: trying to join domain
Jan  4 21:08:28 nas02 ActiveDirectory: AD_join_domain: net ads join -U administrator
Jan  4 21:08:32 nas02 notifier: Using short domain name -- ALITECS
Jan  4 21:08:32 nas02 notifier: Joined 'NAS02' to realm 'alitecs.local'
Jan  4 21:08:32 nas02 ActiveDirectory: AD_join_domain: Successful
Jan  4 21:08:33 nas02 notifier: umount: unmount of /var/tmp/.cache failed: Device busy
Jan  4 21:08:33 nas02 ActiveDirectory: /usr/sbin/service ix-activedirectory status
Jan  4 21:08:33 nas02 ActiveDirectory: AD_init: config exists, loading values from /etc/ActiveDirectory/config
Jan  4 21:08:33 nas02 ActiveDirectory: activedirectory_status: checking status
Jan  4 21:08:33 nas02 ActiveDirectory: AD_status_domain: net ads status -U administrator
Jan  4 21:08:43 nas02 ActiveDirectory: AD_status_domain: Not okay


So I ran that command
Code:
net ads status -U administrator
manually and saw that there were no errors.
I googled and did not find anything helpful only some link to scripts in FreeNAS.
I opened /etc/rc.freenas, found the line that produces that message and saw that there is a timeout configured at the start of the script set to 10. It seems that this is too low for my setup so I increased to 60 (line 123) and now it works!

Just wanted to share...

Regards,
Alexander
 
Status
Not open for further replies.
Top