Project

General

Profile

Tâche #24926

Scénario #24653: Portage des paquets scribe-ad et horus-ad en 2.7.0

Installation Scribe AD en 2.7.0 : le DNS de Samba ne se lance pas

Added by Fabrice Barconnière over 5 years ago. Updated over 5 years ago.

Status:
Fermé
Priority:
Normal
Assigned To:
Start date:
08/27/2018
Due date:
% Done:

100%

Estimated time:
3.00 h
Spent time:
Remaining (hours):
0.0

Description

Une fois le conteneur généré et le serveur instancié, qq chose empêche de lancer le DNS de Samba dans le conteneur addc :

sept. 07 12:23:46 addc samba[2789]:   Failed to listen on 0.0.0.0:53 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED 
sept. 07 12:23:46 addc samba[2789]: [2018/09/07 12:23:46.101682,  0] ../source4/dns_server/dns_server.c:648(dns_add_socket)                
sept. 07 12:23:46 addc samba[2789]:   Failed to bind to 0.0.0.0:53 TCP - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
sept. 07 12:23:46 addc winbindd[2791]: [2018/09/07 12:23:46.240454,  0] ../source3/winbindd/winbindd_cache.c:3170(initialize_winbindd_cache)
sept. 07 12:23:46 addc winbindd[2791]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
sept. 07 12:23:46 addc systemd[1]: Started Samba AD Daemon.                               

en regardant de plus près, voici le coupable :

root@addc:~# lsof -i|grep 53                                                                                                               
systemd-r  46 systemd-resolve   12u  IPv4  36616      0t0  UDP 127.0.0.53:domain                                       
systemd-r  46 systemd-resolve   13u  IPv4  36617      0t0  TCP 127.0.0.53:domain (LISTEN)

Si on arrête systemd-resolved et qu'on relance samba-ad-dc, le DNS fonctionne.

Associated revisions

Revision 869f8613 (diff)
Added by Laurent Flori over 5 years ago

Deactivate systemd-resolved on port 53

ref: #24926

systemd-resolved start on address 127.0.0.53 and port 53 on all modules
We never want this on EOLE

Revision 3f4172ff (diff)
Added by Laurent Flori over 5 years ago

Deactivation of resolver on 127.0.0.53:53 in addc container

ref: #24926

Revision 5f8d6ebf (diff)
Added by Fabrice Barconnière over 5 years ago

Container in the same timezone as master and no dhcp interface

ref #24933
ref #24926

Revision f2a3d743 (diff)
Added by Laurent Flori over 5 years ago

Fix container creation on scribe etb1 and scribe aca

fix: #24926

Deactivate automatiques services startup in container finalisation

History

#1 Updated by Fabrice Barconnière over 5 years ago

  • Description updated (diff)

#2 Updated by Laurent Flori over 5 years ago

  • Status changed from Nouveau to En cours

#3 Updated by Laurent Flori over 5 years ago

  • Assigned To set to Laurent Flori

#4 Updated by Fabrice Barconnière over 5 years ago

  • % Done changed from 0 to 100
  • Remaining (hours) changed from 3.0 to 0.1

#5 Updated by Fabrice Barconnière over 5 years ago

  • Status changed from En cours to Résolu

#6 Updated by Joël Cuissinat over 5 years ago

  • Status changed from Résolu to Fermé
  • Remaining (hours) changed from 0.1 to 0.0

Also available in: Atom PDF