OK, solved that problem. nsupdate worked, even if samba_dnsupdate did not.
New problem:
Lots of entries like this in the log:
[2013/04/09 22:25:39.559029, 2]
../source3/smbd/server.c:436(remove_child_pid)
Could not find child 15172 -- ignoring
[2013/04/09 22:26:39.613172, 2]
../source3/smbd/server.c:436(remove_child_pid)
Could not find child 15175 -- ignoring
I see a bug that describes this problem, but it is marked as fixed since
June 2011.
https://bugzilla.samba.org/show_activity.cgi?id=8269
Simon
On Tue, 9 Apr 2013, simon+sa...@matthews.eu wrote:
Now for the next question. I think (hope?) that I am quite close now.
In order to add a machine to the domain, I think that I need to add a record
to samba's DNS table. But samba_dnsupdate isn't working:
# samba_dnsupdate -d 5
INFO: Current debug levels:
all: 5
tdb: 5
printdrivers: 5
lanman: 5
smb: 5
rpc_parse: 5
rpc_srv: 5
rpc_cli: 5
passdb: 5
sam: 5
auth: 5
winbind: 5
vfs: 5
idmap: 5
quota: 5
acls: 5
locking: 5
msdfs: 5
dmapi: 5
registry: 5
lpcfg_load: refreshing parameters from /usr/local/samba/etc/smb.conf
params.c:pm_process() - Processing configuration file
"/usr/local/samba/etc/smb.conf"
Processing section "[global]"
Processing section "[netlogon]"
Processing section "[sysvol]"
pm_process() returned Yes
added interface eth0 ip=fe80::5054:ff:fefd:9729%eth0
bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff::
added interface eth0 ip=192.168.99.19 bcast=192.168.99.255
netmask=255.255.255.0
schema_fsmo_init: we are master[yes] updates allowed[no]
As you can see updates are not allowed. But my smb.conf looks like this:
[global]
workgroup = MYAD
realm = MYAD.my.domain
netbios name = SAMBA4
server role = active directory domain controller
idmap_ldb:use rfc2307 = yes
# log file = /var/log/samba/samba.log.%m
log level = 3
allow dns updates = True
dns forwarder = 192.168.99.2
Simon
On Tue, 9 Apr 2013, Ricky Nance wrote:
Glad to hear :)
Ricky
On Tue, Apr 9, 2013 at 8:15 PM, Simon Matthews
<si...@matthews-family.org.uk> wrote:
On Tue, 9 Apr 2013, Ricky Nance wrote:
That looks normal... Can you pastebin your log.samba...
first mv or rm
/usr/local/samba/var/log.samba, then restart samba, then
pastebin log.samba.
Also (with samba running) can you give us the output of ps
ax | grep samba
and the output of netstat -anp | grep "LISTEN " | grep
samba
Thanks,
Ricky,
with your help, I fixed the problem. I had started krb5kdc, not
realizing that the krb server was also built into samba. Once I
stopped this and re-started SAMBA, the internal dns server started
working.
Simon
On Tue, Apr 9, 2013 at 7:22 PM, <simon+sa...@matthews.eu>
wrote:
On Tue, 9 Apr 2013, Ricky Nance wrote:
What samba version are you using (samba -V)
# samba -V
Version 4.0.4
? Also what is the output of
samba-tool testparm -v --suppress-prompt | grep
"server
services"
# samba-tool testparm -v --suppress-prompt | grep "server
services"
server services = s3fs, rpc, nbt, wrepl, ldap,
cldap, kdc,
drepl, winbind, ntp_signd, kcc, dnsupdate, dns
Simon
On Tue, Apr 9, 2013 at 6:34 PM,
<simon+sa...@matthews.eu>
wrote:
After running the classicupgrade, configuring
and
starting krb5,
starting the new samba4 server, I started
looking at
DNS.
Nothing is listening on port 53, so I assume
the
internal DNS is
not working. I have NOT specified the use of
the
BIND_DLZ
plugin, so it should be using its internal dns
server.
Where should I start looking for a solution to
this?
--
To unsubscribe from this list go to the
following
URL and read
the
instructions:
https://lists.samba.org/mailman/options/samba
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
