Problems setting up (fresh) Samba 4 installation
Andrew Bartlett
abartlet at samba.org
Thu Jan 3 18:03:45 MST 2013
On Thu, 2013-01-03 at 15:07 -0600, Ricky Nance wrote:
> I have been adding some advice on how to handle this situation here...
> https://wiki.samba.org/index.php/Samba_troubleshooting_temp
>
> Yes, something is using port 53, fix this and you will likely fix all your
> issues.
Exactly.
[2013/01/03 11:50:22, 0] ../source4/smbd/service_stream.c:342
(stream_setup_socket)
Failed to listen on 0.0.0.0:53 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
[2013/01/03 11:50:22, 0] ../source4/dns_server/dns_server.c:616
(dns_add_socket)
Failed to bind to 0.0.0.0:53 TCP -
NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
[2013/01/03 11:50:22, 0] ../source4/smbd/service_task.c:35
(task_server_terminate)
task_server_terminate: [dns failed to setup interfaces]
Samba's DNS server is failing to start because something else (BIND
probably) is listening to 0.0.0.0:53. It is mandatory to fix this
before anything else.
If you really want to have BIND or dnsmasq and Samba running on the same
host, you need to pick a disjoint set of interfaces (or interface
aliases) to bind each to, or (for BIND) use the DLZ backend. But first
show it all working with Samba's internal DNS server only, and move to
more complex configurations later.
Ricky,
Clearly we more than ever need your 'make all of Samba die' fix, as
having a sort-of-half samba running is causing issues for a number of
folks.
Andrew Bartlett
--
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
More information about the samba-technical
mailing list