thr3ads.net - samba - [Samba] NT_STATUS_ADDRESS_NOT_ASSOCIATED error msg on DC boot [Jun 2019]

If this information is useful, please help other people find it:
Share via:

Andreas Habel

2019-Jun-11 08:09 UTC

[Samba] NT_STATUS_ADDRESS_NOT_ASSOCIATED error msg on DC boot

Hi,

after rebooting the AD DC i regularly get NT_STATUS_ADDRESS_NOT_ASSOCIATED and -
as a consequence - task_server_terminate: [XXXd failed to setup interfaces]
error messages in log.samba (I removed a couple of "samba: setproctitle not
initialized, please either call setproctitle_init() or link against
libbsd-ctor." lines for better readability):

[2019/06/11 09:23:47.400171,  0] ../source4/smbd/server.c:448(binary_smbd_main)
  samba version 4.7.6-Ubuntu started.
  Copyright Andrew Tridgell and the Samba Team 1992-2017
[2019/06/11 09:23:47.771969,  0] ../source4/smbd/server.c:620(binary_smbd_main)
  samba: using 'standard' process model
 [2019/06/11 09:23:47.777949,  0]
../source4/nbt_server/interfaces.c:205(nbtd_add_socket)
  Failed to bind to 152.94.0.255:137 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
[2019/06/11 09:23:47.778059,  0]
../source4/smbd/service_task.c:35(task_server_terminate)
  task_server_terminate: [nbtd failed to setup interfaces]
[2019/06/11 09:23:47.782712,  0]
../source4/cldap_server/cldap_server.c:130(cldapd_add_socket)
  Failed to bind to ipv4:152.94.0.106:389 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
[2019/06/11 09:23:47.782813,  0]
../source4/smbd/service_task.c:35(task_server_terminate)
  task_server_terminate: [cldapd failed to setup interfaces]
[2019/06/11 09:23:47.788484,  0]
../source4/smbd/service_stream.c:360(stream_setup_socket)
  Failed to listen on 152.94.0.106:88 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
[2019/06/11 09:23:47.788606,  0] ../source4/kdc/kdc-server.c:584(kdc_add_socket)
  Failed to bind to 152.94.0.106:88 TCP - NT_STATUS_ADDRESS_NOT_ASSOCIATED
[2019/06/11 09:23:47.788675,  0]
../source4/smbd/service_task.c:35(task_server_terminate)
  task_server_terminate: [kdc failed to setup interfaces]
 [2019/06/11 09:23:47.853221,  0]
../source4/smbd/service_stream.c:360(stream_setup_socket)
  Failed to listen on 152.94.0.106:0 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
[2019/06/11 09:23:47.853360,  0]
../source4/rpc_server/dcerpc_server.c:3023(add_socket_rpc_tcp_iface)
  service_setup_stream_socket(address=152.94.0.106,port=0) for dnsserver
backupkey eventlog6 browser unixinfo dssetup drsuapi lsarpc mgmt failed -
NT_STATUS_ADDRESS_NOT_ASSOCIATEDtask_server_terminate: [Failed to startup dcerpc
server task]
[2019/06/11 09:23:50.199566,  0]
../source4/smbd/service_stream.c:360(stream_setup_socket)
  Failed to listen on 152.94.0.106:389 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
[2019/06/11 09:23:50.199780,  0]
../source4/ldap_server/ldap_server.c:1030(add_socket)
  ldapsrv failed to bind to 152.94.0.106:389 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
[2019/06/11 09:23:50.200068,  0]
../source4/smbd/service_task.c:35(task_server_terminate)
  task_server_terminate: [Failed to startup ldap server task]

However, after restarting samba-ad-dc everything looks fine, no error messages
at all (despite of "setproctitle..." messages).

Any idea on how to start samba properly on boot?

Thanks,
Andreas


--
Andreas Habel
Petroleum engineering lab
Geosciences | Unix network
Faculty of Science and Technology
University of Stavanger
Norway

Phone: +47-51 83 22 93

Rowland penny

2019-Jun-11 08:19 UTC

head link

[Samba] NT_STATUS_ADDRESS_NOT_ASSOCIATED error msg on DC boot

On 11/06/2019 09:09, Andreas Habel via samba wrote:> Hi,
>
> after rebooting the AD DC i regularly get NT_STATUS_ADDRESS_NOT_ASSOCIATED
and - as a consequence - task_server_terminate: [XXXd failed to setup
interfaces] error messages in log.samba (I removed a couple of "samba:
setproctitle not initialized, please either call setproctitle_init() or link
against libbsd-ctor." lines for better readability):
>
> [2019/06/11 09:23:47.400171,  0]
../source4/smbd/server.c:448(binary_smbd_main)
>    samba version 4.7.6-Ubuntu started.
>    Copyright Andrew Tridgell and the Samba Team 1992-2017
> [2019/06/11 09:23:47.771969,  0]
../source4/smbd/server.c:620(binary_smbd_main)
>    samba: using 'standard' process model
>   [2019/06/11 09:23:47.777949,  0]
../source4/nbt_server/interfaces.c:205(nbtd_add_socket)
>    Failed to bind to 152.94.0.255:137 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:47.778059,  0]
../source4/smbd/service_task.c:35(task_server_terminate)
>    task_server_terminate: [nbtd failed to setup interfaces]
> [2019/06/11 09:23:47.782712,  0]
../source4/cldap_server/cldap_server.c:130(cldapd_add_socket)
>    Failed to bind to ipv4:152.94.0.106:389 -
NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:47.782813,  0]
../source4/smbd/service_task.c:35(task_server_terminate)
>    task_server_terminate: [cldapd failed to setup interfaces]
> [2019/06/11 09:23:47.788484,  0]
../source4/smbd/service_stream.c:360(stream_setup_socket)
>    Failed to listen on 152.94.0.106:88 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:47.788606,  0]
../source4/kdc/kdc-server.c:584(kdc_add_socket)
>    Failed to bind to 152.94.0.106:88 TCP - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:47.788675,  0]
../source4/smbd/service_task.c:35(task_server_terminate)
>    task_server_terminate: [kdc failed to setup interfaces]
>   [2019/06/11 09:23:47.853221,  0]
../source4/smbd/service_stream.c:360(stream_setup_socket)
>    Failed to listen on 152.94.0.106:0 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:47.853360,  0]
../source4/rpc_server/dcerpc_server.c:3023(add_socket_rpc_tcp_iface)
>    service_setup_stream_socket(address=152.94.0.106,port=0) for dnsserver
backupkey eventlog6 browser unixinfo dssetup drsuapi lsarpc mgmt failed -
NT_STATUS_ADDRESS_NOT_ASSOCIATEDtask_server_terminate: [Failed to startup dcerpc
server task]
> [2019/06/11 09:23:50.199566,  0]
../source4/smbd/service_stream.c:360(stream_setup_socket)
>    Failed to listen on 152.94.0.106:389 - NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:50.199780,  0]
../source4/ldap_server/ldap_server.c:1030(add_socket)
>    ldapsrv failed to bind to 152.94.0.106:389 -
NT_STATUS_ADDRESS_NOT_ASSOCIATED
> [2019/06/11 09:23:50.200068,  0]
../source4/smbd/service_task.c:35(task_server_terminate)
>    task_server_terminate: [Failed to startup ldap server task]
>
> However, after restarting samba-ad-dc everything looks fine, no error
messages at all (despite of "setproctitle..." messages).
>
> Any idea on how to start samba properly on boot?
>Are you by any chance trying to start the 'nmbd' binary as well as the 
'samba' binary ?

If so, you must stop this happening. On a DC, starting 'samba' will 
start all other required binaries.

If this isn't the case, can you please post your smb.conf

Rowland

Andreas Habel

2019-Jun-11 08:26 UTC

head link

[Samba] NT_STATUS_ADDRESS_NOT_ASSOCIATED error msg on DC boot

> -----Original Message-----
> From: samba <samba-bounces at lists.samba.org> On Behalf Of Rowland
penny via
> samba
> Sent: 11. juni 2019 10:19
> To: samba at lists.samba.org
> Subject: Re: [Samba] NT_STATUS_ADDRESS_NOT_ASSOCIATED error msg on DC boot
> 
> On 11/06/2019 09:09, Andreas Habel via samba wrote:
> > Hi,
> >
> > after rebooting the AD DC i regularly get
> NT_STATUS_ADDRESS_NOT_ASSOCIATED and - as a consequence -
> task_server_terminate: [XXXd failed to setup interfaces] error messages in
> log.samba (I removed a couple of "samba: setproctitle not initialized,
> please either call setproctitle_init() or link against libbsd-ctor."
lines
> for better readability):
> >
> > [2019/06/11 09:23:47.400171,  0]
> ../source4/smbd/server.c:448(binary_smbd_main)
> >    samba version 4.7.6-Ubuntu started.
> >    Copyright Andrew Tridgell and the Samba Team 1992-2017
> > [2019/06/11 09:23:47.771969,  0]
> ../source4/smbd/server.c:620(binary_smbd_main)
> >    samba: using 'standard' process model
> >   [2019/06/11 09:23:47.777949,  0]
> ../source4/nbt_server/interfaces.c:205(nbtd_add_socket)
> >    Failed to bind to 152.94.0.255:137 -
NT_STATUS_ADDRESS_NOT_ASSOCIATED
> > [2019/06/11 09:23:47.778059,  0]
> ../source4/smbd/service_task.c:35(task_server_terminate)
> >    task_server_terminate: [nbtd failed to setup interfaces]
> > [2019/06/11 09:23:47.782712,  0]
> ../source4/cldap_server/cldap_server.c:130(cldapd_add_socket)
> >    Failed to bind to ipv4:152.94.0.106:389 -
> NT_STATUS_ADDRESS_NOT_ASSOCIATED
> > [2019/06/11 09:23:47.782813,  0]
> ../source4/smbd/service_task.c:35(task_server_terminate)
> >    task_server_terminate: [cldapd failed to setup interfaces]
> > [2019/06/11 09:23:47.788484,  0]
> ../source4/smbd/service_stream.c:360(stream_setup_socket)
> >    Failed to listen on 152.94.0.106:88 -
> NT_STATUS_ADDRESS_NOT_ASSOCIATED
> > [2019/06/11 09:23:47.788606,  0] ../source4/kdc/kdc-
> server.c:584(kdc_add_socket)
> >    Failed to bind to 152.94.0.106:88 TCP -
> NT_STATUS_ADDRESS_NOT_ASSOCIATED
> > [2019/06/11 09:23:47.788675,  0]
> ../source4/smbd/service_task.c:35(task_server_terminate)
> >    task_server_terminate: [kdc failed to setup interfaces]
> >   [2019/06/11 09:23:47.853221,  0]
> ../source4/smbd/service_stream.c:360(stream_setup_socket)
> >    Failed to listen on 152.94.0.106:0 -
NT_STATUS_ADDRESS_NOT_ASSOCIATED
> > [2019/06/11 09:23:47.853360,  0]
> ../source4/rpc_server/dcerpc_server.c:3023(add_socket_rpc_tcp_iface)
> >    service_setup_stream_socket(address=152.94.0.106,port=0) for
> dnsserver backupkey eventlog6 browser unixinfo dssetup drsuapi lsarpc mgmt
> failed - NT_STATUS_ADDRESS_NOT_ASSOCIATEDtask_server_terminate: [Failed to
> startup dcerpc server task]
> > [2019/06/11 09:23:50.199566,  0]
> ../source4/smbd/service_stream.c:360(stream_setup_socket)
> >    Failed to listen on 152.94.0.106:389 -
> NT_STATUS_ADDRESS_NOT_ASSOCIATED
> > [2019/06/11 09:23:50.199780,  0]
> ../source4/ldap_server/ldap_server.c:1030(add_socket)
> >    ldapsrv failed to bind to 152.94.0.106:389 -
> NT_STATUS_ADDRESS_NOT_ASSOCIATED
> > [2019/06/11 09:23:50.200068,  0]
> ../source4/smbd/service_task.c:35(task_server_terminate)
> >    task_server_terminate: [Failed to startup ldap server task]
> >
> > However, after restarting samba-ad-dc everything looks fine, no error
> messages at all (despite of "setproctitle..." messages).
> >
> > Any idea on how to start samba properly on boot?
> >
> Are you by any chance trying to start the 'nmbd' binary as well as
the
> 'samba' binary ?
> 
No, nmbd is not started separately:
systemctl status nmbd
? nmbd.service - Samba NMB Daemon
   Loaded: loaded (/lib/systemd/system/nmbd.service; disabled; vendor preset:
enabled)
   Active: inactive (dead)
     Docs: man:nmbd(8)
           man:samba(7)
           man:smb.conf(5)

> If so, you must stop this happening. On a DC, starting 'samba' will
> start all other required binaries.
> 
> If this isn't the case, can you please post your smb.conf
> 
Here is my smb.conf:

[global]
        netbios name = GEO22
        realm = IERLAB.UX.UIS.NO
        server role = active directory domain controller
        server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl,
winbindd, ntp_signd, kcc, dnsupdate
        workgroup = IERLAB
        idmap_ldb:use rfc2307 = yes
        interfaces = 152.94.0.106/24 127.0.0.1
        bind interfaces only = yes
        template shell = /bin/bash
        template homedir = /home/%U
[netlogon]
        path = /var/lib/samba/sysvol/ierlab.ux.uis.no/scripts
        read only = No

[sysvol]
        path = /var/lib/samba/sysvol
        read only = No


Andreas


-- 
Andreas Habel
Petroleum engineering lab
Geosciences | Unix network
Faculty of Science and Technology
University of Stavanger
Norway

Phone: +47-51 83 22 93

Apparently Analagous Threads

Search for more reasonably related threads

samba - Jun 2019 - NT_STATUS_ADDRESS_NOT_ASSOCIATED error msg on DC boot

[Samba] NT_STATUS_ADDRESS_NOT_ASSOCIATED error msg on DC boot

[Samba] NT_STATUS_ADDRESS_NOT_ASSOCIATED error msg on DC boot

[Samba] NT_STATUS_ADDRESS_NOT_ASSOCIATED error msg on DC boot

Apparently Analagous Threads