Bug 49581 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED - samba startup failed during setup
NT_STATUS_ADDRESS_ALREADY_ASSOCIATED - samba startup failed during setup
Status: NEW
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-05-31 12:22 CEST by Felix Botner
Modified: 2020-05-28 10:20 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.171
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments
log.samba (5.03 KB, text/plain)
2019-05-31 12:26 CEST, Felix Botner
Details
autotest.log (968.19 KB, text/x-log)
2019-05-31 12:27 CEST, Felix Botner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Botner univentionstaff 2019-05-31 12:22:31 CEST
Recently seen in our jenkins tests. 

Samba startup failed with 

[2019/05/30 23:54:18.852551,  0, pid=8495] ../../source4/smbd/service_stream.c:374(stream_setup_socket)
  stream_setup_socket: Failed to listen on 10.210.8.221:49154 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
[2019/05/30 23:54:18.852637,  0, pid=8495] ../../source4/rpc_server/dcerpc_server.c:3221(add_socket_rpc_tcp_iface)
  service_setup_stream_socket(address=10.210.8.221,port=49154) for samr rpcecho wkssvc mgmt failed - NT_STATUS_ADDRESS_ALREADY_ASSOCIATEDtask_server_terminate: task_server_terminate: [dcerpc: Failed to initialise end points]
[2019/05/30 23:54:18.930989,  0, pid=8477] ../../lib/util/become_daemon.c:136(daemon_ready)
  daemon_ready: daemon 'samba' finished starting up and ready to serve connections
[2019/05/30 23:54:18.944930,  0, pid=8477] ../../source4/smbd/server.c:371(samba_terminate)
  samba_terminate: samba_terminate of samba 8477: dcerpc: Failed to initialise end points
[2019/05/30 23:54:25.238502,  0, pid=8694] ../../source4/smbd/server.c:587(binary_smbd_main)

half an our later it worked

[2019/05/31 00:24:27.718606,  0, pid=1323] ../../source4/smbd/server.c:587(binary_smbd_main)
  samba version 4.10.1-Univention started.
  Copyright Andrew Tridgell and the Samba Team 1992-2019

This broke the test because the the s4connector was unable to sync objects to samba (samba was not running) and therefor the join script 98univention-samba4-dns.inst failed (looking for spn account "dns-master091c" in local samba).
Comment 1 Felix Botner univentionstaff 2019-05-31 12:26:19 CEST
Created attachment 10050 [details]
log.samba
Comment 2 Felix Botner univentionstaff 2019-05-31 12:27:46 CEST
Created attachment 10051 [details]
autotest.log
Comment 3 Arvid Requate univentionstaff 2019-06-03 20:29:22 CEST
Looks like port 49154 was already occupied by a different process. The dynamic port range for samba is 49152-65535.
Comment 4 Christina Scheinig univentionstaff 2020-05-26 09:17:02 CEST
A customer now suggests he has the same issue in different customer environments.
Comment 5 Christina Scheinig univentionstaff 2020-05-26 15:49:32 CEST
I increased the "feeling level", because in two customer environments it happens at night. In the morning samba has to be started.
Comment 6 Christina Scheinig univentionstaff 2020-05-28 10:20:27 CEST
In the support case this seems to be an other issue. The error message is similar to this, but it is the normal 135 port.

I reset the flags!