Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#837679: samba: Start fails for Samba as 'active directory domain controller'

387 views
Skip to first unread message

Axel Dürrbaum

unread,
Sep 13, 2016, 9:10:03 AM9/13/16
to
Package: samba
Version: 2:4.4.5+dfsg-3
Severity: important

Dear Maintainer,

after updating Samba from 2:4.3.8+dfsg-1 to 2:4.4.5+dfsg-3 I cannot start it
anymore:

[2016/09/13 10:13:29.504945, 0] ../source3/nmbd/nmbd.c:923(main)
server role = 'active directory domain controller' not compatible with
running nmbd standalone.
You should start 'samba' instead, and it will control starting the internal
nbt server

Result: there will be no nmbd daemon running.

When switching to server role = 'standalone' or 'auto' Samba starts but I loose
all domain users ...

Reinstalling 2:4.3.8+dfsg-1 does not help, the error stills remains.


smb.conf:
[global]
workgroup = MRT
realm = MRT.MASCHINENBAU.UNI-KASSEL.DE
netbios name = MRT-PC2

server role = active directory domain controller

dns forwarder = 141.51.x.x
dns forwarder = 141.51.x.x

wins support = yes
os level = 65
dns proxy = yes

idmap_ldb:use rfc2307 = yes

log level = 2 auth:2 passdb:2 winbind:2
debug timestamp = yes

remote announce = 141.51.x.x/MRT, 141.51.y.x/MRT

logon path = \\141.51.x.x\profiles\%U
logon drive = Z:
logon home = \\141.51.x.x\%U

server services = +web

unix password sync = yes
passwd program = /usr/bin/passwd %u


[Shares.and printers ...]


TIA
Axel Dürrbaum




-- System Information:
Debian Release: stretch/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages samba depends on:
ii adduser 3.115
ii dpkg 1.18.10
ii init-system-helpers 1.44
ii libbsd0 0.8.3-1
ii libc6 2.24-2
ii libldb1 2:1.1.26-1
ii libpam-modules 1.1.8-3.3
ii libpam-runtime 1.1.8-3.3
ii libpopt0 1.16-10
ii libpython2.7 2.7.12-3
ii libtalloc2 2.1.7-1
ii libtdb1 1.3.9-1
ii libtevent0 0.9.28-1
ii libwbclient0 2:4.4.5+dfsg-3
ii lsb-base 9.20160629
ii procps 2:3.3.12-2
ii python 2.7.11-2
ii python-dnspython 1.14.0-3
ii python-samba 2:4.4.5+dfsg-3
pn python2.7:any <none>
ii samba-common 2:4.4.5+dfsg-3
ii samba-common-bin 2:4.4.5+dfsg-3
ii samba-libs 2:4.4.5+dfsg-3
ii tdb-tools 1.3.9-1
ii update-inetd 4.43

Versions of packages samba recommends:
ii attr 1:2.4.47-2
ii logrotate 3.8.7-2
ii samba-dsdb-modules 2:4.4.5+dfsg-3
ii samba-vfs-modules 2:4.4.5+dfsg-3

Versions of packages samba suggests:
pn bind9 <none>
pn bind9utils <none>
pn ctdb <none>
ii ldb-tools 2:1.1.26-1
ii ntp 1:4.2.8p8+dfsg-1
ii smbldap-tools 0.9.9-1
pn ufw <none>
ii winbind 2:4.4.5+dfsg-3

-- Configuration Files:
/etc/logrotate.d/samba changed [not included]

-- no debconf information

Mathieu Parent

unread,
Oct 9, 2016, 4:30:03 PM10/9/16
to
"

2016-09-13 14:58 GMT+02:00 Axel Dürrbaum <ax...@uni-kassel.de>:
> Package: samba
> Version: 2:4.4.5+dfsg-3
> Severity: important
>
> Dear Maintainer,
>
> after updating Samba from 2:4.3.8+dfsg-1 to 2:4.4.5+dfsg-3 I cannot start it
> anymore:
>
> [2016/09/13 10:13:29.504945, 0] ../source3/nmbd/nmbd.c:923(main)
> server role = 'active directory domain controller' not compatible with
> running nmbd standalone.
> You should start 'samba' instead, and it will control starting the internal
> nbt server

This check (upstream commit 8c71dc3505ab83ce95ab40a56f77313c4448be16,
from 2012) is here since samba 4.0.

As written, the nbt "server service" takes care of "NetBIOS over
TCP/IP. You don't need nmbd in your setup.


> Result: there will be no nmbd daemon running.

But do you have any missing feature?

What does "service samba-ad-dc status" outputs (with "server role =
'active directory domain controller' ")?

> When switching to server role = 'standalone' or 'auto' Samba starts but I loose
> all domain users ...

Yes.

> Reinstalling 2:4.3.8+dfsg-1 does not help, the error stills remains.

Not a surprise.

Regards

--
Mathieu Parent
0 new messages