9.2.1.8 - Samba not working anymore

[rhdd]

I just upgraded from 9.2.1.7 to 9.2.1.8 - no other changes. Now samba refuses to start.

Oct 1 13:04:58 home samba[3914]: [2014/10/01 13:04:58.350340, 0] ../source4/smbd/server.c:370(binary_smbd_main)
Oct 1 13:04:58 home kernel: OK
Oct 1 13:04:58 home samba[3914]: samba version 4.1.12 started.
Oct 1 13:04:58 home samba[3914]: Copyright Andrew Tridgell and the Samba Team 1992-2013
Oct 1 13:04:59 home samba[3915]: [2014/10/01 13:04:59.288799, 0] ../source4/smbd/server.c:488(binary_smbd_main)
Oct 1 13:04:59 home samba[3915]: samba: using 'standard' process model
Oct 1 13:04:59 home samba[3915]: [2014/10/01 13:04:59.327856, 0] ../source4/smbd/service.c:98(server_service_startup)
Oct 1 13:04:59 home samba[3915]: Failed to start service 'dns' - NT_STATUS_INVALID_SYSTEM_SERVICE
Oct 1 13:04:59 home samba[3915]: [2014/10/01 13:04:59.328696, 0] ../lib/util/become_daemon.c:124(exit_daemon)
Oct 1 13:04:59 home samba[3915]: STATUS=daemon failed to start: Samba failed to start services, error code -1073741796
Oct 1 13:05:02 home su: in openpam_check_error_code(): pam_sm_setcred(): unexpected return value 12​

The problem seems to have something to do with DNS.

How can I troubleshoot this?

 

[anodos]

Post smb4.conf and output of 'testparm'.

 

[rhdd]

/usr/local/etc/smb4.conf:

[global]
server max protocol = SMB3
encrypt passwords = yes
dns proxy = no
strict locking = no
oplocks = yes
deadtime = 15
max log size = 51200
max open files = 11070
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes
getwd cache = yes
guest account = nobody
map to guest = Bad User
obey pam restrictions = Yes
directory name cache size = 0
kernel change notify = no
panic action = /usr/local/libexec/samba/samba-backtrace
server string = FreeNAS Server
ea support = yes
store dos attributes = yes
unix extensions = no
time server = yes
acl allow execute always = true
local master = yes
idmap config *:backend = tdb
idmap config *:range = 90000000-100000000
server role = active directory domain controller
netbios name = HOME
workgroup = MYDOMAIN
realm = MYDOMAIN.LOCAL
dns forwarder = 10.10.10.1
idmap_ldb:use rfc2307 = yes
create mask = 0666
directory mask = 0777
client ntlmv2 auth = yes
dos charset = CP437
unix charset = UTF-8
log level = 3
disable netbios = yes
allow dns updates = nonsecure

...​

samba-tool testparm

You have some share names that are longer than 12 characters. These may not be accessible to some older clients. (Eg. Windows9x, WindowsMe, and not listed in smbclient in Samba 3.0.)
Press enter to see a dump of your service definitions​

 

[rhdd]

After some hours of searching and trying I downgraded to 9.2.1.7 and restored yesterday's config backup. -> It is working again.

 

[anodos]

You're running samba as an AD domain controller. Samba 4 has its own DNS that it uses when configured as a DC. The samba version apparently got bumped up to 4.1.12 (FreeNAS 9.2.1.7 was on 4.1.11). My best guess is that 4.1.12 may have introduced a bug when samba is configured as a DC. You should increase logging verbosity for CIFS and try it again. Copy the detailed error messages. Also, you can go into "Directory Services" --> "Domain Controller" and see if the backend changed in the change from 9.2.1.7 --> 9.2.1.8. If it is the same, experiment with a different DNS backend. If you still can't get it working make a bug report on bugs.freenas.org and attach all the info you've gathered.

 

[rhdd]

Thanks anodos! I'm quite happy that my server is back to life. I cannot do the update again at the moment.

Before downgrading I increased the logging verbosity to "debug". This did not add anything to these lines:

...
Oct 1 13:04:59 home samba[3915]: [2014/10/01 13:04:59.327856, 0] ../source4/smbd/service.c:98(server_service_startup)
Oct 1 13:04:59 home samba[3915]: Failed to start service 'dns' - NT_STATUS_INVALID_SYSTEM_SERVICE
...​

I checked the configured DNS backend as well. The setting ("SAMBA_INTERNAL") was correct. Changing this is not an option as I don't have a bind server with all the requirements running.

 

[anodos]

Sounds then like you should make a bug report and link to it from here.

 

[rhdd]

https://bugs.freenas.org/issues/6241