search for: nt_status_address_already_associ

...0alpha19-GIT-40a4aea openSUSE 12.1 with bind9.8.1-SP + samba dlz I just ran make install over the top of a working build from a week ago. Everything seems to work but I get this during startup from d3: <snip> WARNING: no socket to connect to <snip> Failed to listen on 192.168.1.3:53 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED Failed to bind to 192.168.1.3:53 TCP - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED task_server_terminate: [dns failed to setup interfaces] standard_terminate: reason[dns failed to setup interfaces] Any ideas? As I say, no bad effects of yet. Cheers, Steve

.../ samba-i-M single-d 1 Samba version 4.1.0pre1-GIT-05a5974 started. Copyright Andrew Tridgell and the Samba Team 1992-2012 samba: using 'single' process model Started with smbd server config file / usr/local/samba4-migracao/private/smbd.tmp/fileserver.conf Failed to listen on 0.0.0.0:636 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED ldapsrv failed to bind to 0.0.0.0:636 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED task_server_terminate: [Failed to startup ldap server task] / usr/local/samba4-migracao/sbin/smbd: smbd version 4.1.0pre1-GIT-05a5974 started. / usr/local/samba4-migracao/sbin/smbd: Copyright Andrew Tridgell and the Sa...

...smbd_main: samba: using 'standard' process model Jul 23 10:19:26 samba4-dc samba: task[dns][838]: [2019/07/23 10:19:26.025682, 0] ../../source4/smbd/service_stream.c:374(stream_setup_socket) Jul 23 10:19:26 samba4-dc samba: task[dns][838]: stream_setup_socket: Failed to listen on :::53 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED Jul 23 10:19:26 samba4-dc samba: task[dns][838]: [2019/07/23 10:19:26.025819, 0] ../../source4/dns_server/dns_server.c:649(dns_add_socket) Jul 23 10:19:26 samba4-dc samba: task[dns][838]: Failed to bind to :::53 TCP - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED Jul 23 10:19:26 samba4-dc samba: task...

On 23/07/2020 18:12, James B. Byrne via samba wrote: > > On Thu, July 23, 2020 16:16:30, Mani Wieser wrote: > >>>> ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket) >>>> Failed to bind to 127.0.162.1:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED >> check where has port 137 occupied > There is nothing listening on 137 > > [root at smb4-2 ~ (master)]# netstat -an | grep -i listen > tcp4 0 0 192.168.18.162.22 *.* LISTEN > tcp4 0 0 192.168.216.162.22 *.*...

...8.04 Idea is to use Host OS for Domain Controler (dc1.smb.domain.tld) and a LXC container (ubuntu 18.04 too) as Domain Member with File Server (fs.smb.domain.tld). Administration through Windows OS will be done with a Qemu KVM. Bad thing is that I get : > Failed to bind to 0.0.0.0:53 TCP - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED as dnsmasq is using port 53 : > netstat -tulpn | grep ":53" > tcp        0      0 192.168.122.1:53 0.0.0.0:*               > LISTEN      1283/dnsmasq > tcp        0      0 10.0.3.1:53 0.0.0.0:*               LISTEN      > 1062/dnsmasq > tcp6       0      0 :::53...

...samba_terminate: samba_terminate of samba 21886: kdc failed to setup interfaces Nov 03 18:54:19 AD samba[21925]: [2020/11/03 18:54:19.319591, 0] ../../source4/smbd/service_stream.c:374(stream_setup_socket) Nov 03 18:54:19 AD samba[21925]: stream_setup_socket: Failed to listen on 0.0.0.0:53 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED Nov 03 18:54:19 AD samba[21925]: [2020/11/03 18:54:19.319686, 0] ../../source4/dns_server/dns_server.c:649(dns_add_socket) Nov 03 18:54:19 AD samba[21925]: Failed to bind to 0.0.0.0:53 TCP - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED Nov 03 18:54:19 AD systemd[1]: samba-ad-dc.service: Main proc...

...xited, status=1/FAILURE) CPU: 12.734s ---- Cut Here ---- ---- Cut Here: Journalctl -xe ---- Nov 19 05:09:49 pluto samba[1098]: [2020/11/19 05:09:49.004709, 0] ../../source4/dns_server/dns_server.c:648(dns_add_socket) Nov 19 05:09:49 pluto samba[1098]: Failed to bind to 0.0.0.0:53 TCP - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED Nov 19 05:09:49 pluto systemd[1]: samba.service: Got notification message from PID 1063, but reception only permitted for main PID 1054 Nov 19 05:09:49 pluto systemd[1]: samba.service: Got notification message from PID 1090, but reception only permitted for main PID 1054 Nov 19 05:09:51 pluto w...

...9, 0] >> ../../source4/smbd/server.c:773(binary_smbd_main) >> binary_smbd_main: samba: using 'standard' process model >> [2020/07/22 12:48:50.103387, 0] >> ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket) >> Failed to bind to 127.0.162.1:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED >> [2020/07/22 12:48:50.150866, 0] >> ../../lib/util/become_daemon.c:136(daemon_ready) >> daemon_ready: daemon 'samba' finished starting up and ready to serve >> connections >> [2020/07/22 12:48:50.184811, 0] >> ../../source4/smbd/service_task.c:...

...-signed keys for https for hostname 'SOMEDOM.somedom.local' samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor. [2015/03/17 14:49:46.848705, 0] ../source4/smbd/service_stream.c:346(stream_setup_socket) Failed to listen on 0.0.0.0:464 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED [2015/03/17 14:49:46.848876, 0] ../source4/kdc/kdc.c:672(kdc_add_socket) Failed to bind to 0.0.0.0:464 TCP - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED [2015/03/17 14:49:46.848976, 0] ../source4/smbd/service_task.c:35(task_server_terminate) task_server_terminate: [kdc failed to setup interfaces...

...a wrote: >> On 23/07/2020 18:12, James B. Byrne via samba wrote: >>> On Thu, July 23, 2020 16:16:30, Mani Wieser wrote: >>> >>>>>> ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket) >>>>>> Failed to bind to 127.0.162.1:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED >>>> check where has port 137 occupied >>> There is nothing listening on 137 >>> >>> [root at smb4-2 ~ (master)]# netstat -an | grep -i listen >>> tcp4 0 0 192.168.18.162.22 *.* LISTEN >>> tcp4 0...

...NET [2018/11/11 19:42:09.029483, 0] ../source3/lib/util_sock.c:1250(create_pipe_sock) bind failed on pipe socket /run/samba/nmbd/unexpected: Address already in use [2018/11/11 19:42:09.029889, 0] ../source3/nmbd/nmbd_packets.c:48(nmbd_init_packet_server) ERROR: nb_packet_server_create failed: NT_STATUS_ADDRESS_ALREADY_ASSOCIATED [2018/11/11 19:42:09.030065, 0] ../lib/util/become_daemon.c:111(exit_daemon) STATUS=daemon failed to start: NMBD failed to setup packet server., error code 13

...UBUNTU_CODENAME=bionic > On 10 Oct 2020, at 15:09, Rowland penny via samba <samba at lists.samba.org> wrote: > > On 10/10/2020 14:00, Philip Offermans wrote: >> Ok I am running the command from an domain member. >> > >> ldapsrv failed to bind to 0.0.0.0:389 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED >> >> >> I am fairly new. I don?t fully understand this. >> > It looks like something else is running that is using port 389, do you have openldap installed as well, or did Samba not shut down correctly ? > > Can you post what I asked for in my last post ? &...

...2 samba-02 samba[37571]: binary_smbd_main: samba: using 'standard' process model May 5 15:13:12 samba-02 samba[37578]: [2020/05/05 15:13:12.765718, 0] ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket) May 5 15:13:12 samba-02 samba[37578]: Failed to bind to 192.168.8.66:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED May 5 15:13:12 samba-02 samba[37578]: [2020/05/05 15:13:12.766128, 0] ../../source4/smbd/service_task.c:36(task_server_terminate) May 5 15:13:12 samba-02 samba[37578]: task_server_terminate: task_server_terminate: [nbtd failed to setup interfaces] May 5 15:13:12 samba-02 samba[37571]: [20...

Dear samba-mailinglist, We're using samba 4.0.5 as an active directory domain controller. We used to set up some file shares on basis security=user in the old samba version. I was able to set up the shares as they used to be . My Question: How can I set up "wich user kan read/write which share?" Do I have to do this in den Active Directory or in smb.conf? This maybe a trivial

...ot at dc1:~ # [2019/02/17 18:15:35.379881, 0] ../source4/smbd/server.c:674(binary_smbd_main) > binary_smbd_main: samba: using 'standard' process model > [2019/02/17 18:15:35.384663, 0] ../source4/nbt_server/interfaces.c:228(nbtd_add_socket) > Failed to bind to 10.1.2.34:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED > [2019/02/17 18:15:35.384752, 0] ../source4/smbd/service_task.c:36(task_server_terminate) > task_server_terminate: task_server_terminate: [nbtd failed to setup interfaces] > [2019/02/17 18:15:35.396234, 0] ../lib/util/become_daemon.c:138(daemon_ready) > daemon_ready: STATUS=d...

...(code=exited, status=1/FAILURE) Feb 27 16:35:18 adc1 samba[17837]: task[ldapsrv][17837]: [2020/02/27 16:35:18.492522, 0] ../source4/smbd/service_stream.c:371(stream_setup_socket) Feb 27 16:35:18 adc1 samba[17837]: task[ldapsrv][17837]: stream_setup_socket: Failed to listen on 0.0.0.0:389 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED Feb 27 16:35:18 adc1 samba[17837]: task[ldapsrv][17837]: [2020/02/27 16:35:18.492563, 0] ../source4/ldap_server/ldap_server.c:1036(add_socket) Feb 27 16:35:18 adc1 samba[17837]: task[ldapsrv][17837]: ldapsrv failed to bind to 0.0.0.0:389 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED Feb 27 16:35...

On Wed, July 22, 2020 21:47, Andrew Bartlett wrote: > Are you using DLZ_BIND9? There is a bug where it doesn't know the locking rules for those files. No. I am using the internal dns service. > Otherwise, work out which commend it is waiting on (the child) and > what lock that is waiting on (lslocks on linux is what I used to > debug this stuff). There does not appear to be

...t; Feb 27 16:35:18 adc1 samba[17837]: task[ldapsrv][17837]: > [2020/02/27 16:35:18.492522, 0] > ../source4/smbd/service_stream.c:371(stream_setup_socket) > > Feb 27 16:35:18 adc1 samba[17837]: task[ldapsrv][17837]: > stream_setup_socket: Failed to listen on 0.0.0.0:389 - > NT_STATUS_ADDRESS_ALREADY_ASSOCIATED > > Feb 27 16:35:18 adc1 samba[17837]: task[ldapsrv][17837]: > [2020/02/27 16:35:18.492563, 0] > ../source4/ldap_server/ldap_server.c:1036(add_socket) > > Feb 27 16:35:18 adc1 samba[17837]: task[ldapsrv][17837]: > ldapsrv failed to bind to 0.0.0.0:389 - > NT_STA...

...togenerate TLS self-signed keys for https for hostname 'MYTHTV-0.dmz.meanspc.com' Mar 17 17:39:07 mythtv-0 samba[9964]: [2014/03/17 17:39:07.758518, 0] ../source4/smbd/service_stream.c:346(stream_setup_socket) Mar 17 17:39:07 mythtv-0 samba[9964]: Failed to listen on 192.168.101.170:53 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED Mar 17 17:39:07 mythtv-0 samba[9964]: [2014/03/17 17:39:07.781551, 0] ../source4/dns_server/dns_server.c:623(dns_add_socket) Mar 17 17:39:07 mythtv-0 samba[9964]: Failed to bind to 192.168.101.170:53 TCP - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED Mar 17 17:39:07 mythtv-0 samba[9964]: [2014/03/17...

FreeBSD-12.1p7 jail running Samba-4.10.15 on ZFS. When I run 'samba-tool domain backup offline targetdir=/tmp' I see this: running backup on dirs: /var/db/samba4/private /var/db/samba4 /usr/local/etc Starting transaction on /var/db/samba4/private/secrets At which point samba-tool enters a permanent wait state. 86064 root 1 52 0 131M 78M wait 3 0:01 0.00%