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).
Created attachment 10050 [details] log.samba
Created attachment 10051 [details] autotest.log
Looks like port 49154 was already occupied by a different process. The dynamic port range for samba is 49152-65535.
A customer now suggests he has the same issue in different customer environments.
I increased the "feeling level", because in two customer environments it happens at night. In the morning samba has to be started.
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!
This issue has been filed against UCS 4.4. UCS 4.4 is out of maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer versions, please use "Clone this bug" or reopen this issue. In this case please provide information on how this issue is affecting you.