Debian 9 Stretch / Erreur Samba nmbd, smbd "query_name_response: Multiple (2)"

DjoMenTunes · Janvier 17, 2019, 3:49pm

Bonjour à tous les membres de debian-fr.org.

Serveur : nasdjo ip 192.168.0.10
H96 pro+ : TvBox Android ip 192.168.0.45
W7Pro : ssh ip 192.168.0.30

Je viens poster ici un problème que je n’arrive pas à solutionner sur ma Debian, serveur faisant office de NAS.
Depuis que j’ai installé Bind9, Resolve et voulu reconfigurer un partage NFS, j’ai des erreurs :
En root : etc/init.d/samba status -l

● nmbd.service - Samba NMB Daemon
   Loaded: loaded (/lib/systemd/system/nmbd.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-01-17 15:34:45 CET; 17min ago
     Docs: man:nmbd(8)
           man:samba(7)
           man:smb.conf(5)
 Main PID: 878 (nmbd)
   Status: "nmbd: ready to serve connections..."
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/nmbd.service
           └─878 /usr/sbin/nmbd

janv. 17 15:34:42 nasdjo.casa.it systemd[1]: Starting Samba NMB Daemon...
janv. 17 15:34:45 nasdjo.casa.it systemd[1]: nmbd.service: Supervising process 878 which is not our child. We'll most likely not notice when it exits.
janv. 17 15:34:45 nasdjo.casa.it systemd[1]: Started Samba NMB Daemon.
janv. 17 15:34:45 nasdjo.casa.it nmbd[878]: [2019/01/17 15:34:45.280980,  0] ../lib/util/become_daemon.c:124(daemon_ready)
janv. 17 15:34:45 nasdjo.casa.it nmbd[878]:   STATUS=daemon 'nmbd' finished starting up and ready to serve connections
● smbd.service - Samba SMB Daemon
   Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-01-17 15:34:48 CET; 16min ago
     Docs: man:smbd(8)
           man:samba(7)
           man:smb.conf(5)
 Main PID: 936 (smbd)
   Status: "smbd: ready to serve connections..."
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/smbd.service
           ├─ 936 /usr/sbin/smbd
           ├─ 937 /usr/sbin/smbd
           ├─ 938 /usr/sbin/smbd
           └─1030 /usr/sbin/smbd

janv. 17 15:34:45 nasdjo.casa.it systemd[1]: Starting Samba SMB Daemon...
janv. 17 15:34:47 nasdjo.casa.it systemd[1]: smbd.service: Supervising process 936 which is not our child. We'll most likely not notice when it exits.
janv. 17 15:34:48 nasdjo.casa.it systemd[1]: Started Samba SMB Daemon.
janv. 17 15:34:48 nasdjo.casa.it smbd[936]: [2019/01/17 15:34:48.151006,  0] ../lib/util/become_daemon.c:124(daemon_ready)
janv. 17 15:34:48 nasdjo.casa.it smbd[936]:   STATUS=daemon 'smbd' finished starting up and ready to serve connections

En root : tail -n 100 /var/log/samba/log.nmbd

Got SIGTERM: going down...
[2019/01/15 17:07:24.243427,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2019/01/15 17:08:28.490206,  0] ../source3/nmbd/nmbd.c:58(terminate)
  Got SIGTERM: going down...
[2019/01/15 17:13:25.921673,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2019/01/15 17:24:21.686138,  0] ../source3/nmbd/nmbd.c:58(terminate)
  Got SIGTERM: going down...
[2019/01/15 17:24:21.740545,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2019/01/15 17:29:58.060726,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
  *****

  Samba name server NASDJO is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.10

  *****
[2019/01/15 17:32:23.432012,  0] ../source3/nmbd/nmbd.c:58(terminate)
[2019/01/15 17:32:23.484206,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2019/01/15 17:42:58.957421,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
  *****

  Samba name server NASDJO is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.10

  *****
[2019/01/15 17:54:12.304484,  0] ../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success)
  *****

  Samba name server NASDJO has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.0.10

  *****
[2019/01/15 18:13:17.573248,  0] ../source3/nmbd/nmbd.c:58(terminate)
  Got SIGTERM: going down...
[2019/01/15 18:13:17.628984,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2019/01/15 23:51:52.065371,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2019/01/15 23:55:00.833421,  0] ../source3/nmbd/nmbd.c:58(terminate)
  Got SIGTERM: going down...
[2019/01/15 23:55:00.939603,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2019/01/16 00:25:41.096266,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.10 for name WORKGROUP<1d>.
  This response was from IP 192.168.0.30, reporting an IP address of 192.168.56.1.
[2019/01/16 00:30:26.329254,  0] ../source3/nmbd/nmbd.c:58(terminate)
[2019/01/16 00:30:26.381256,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2019/01/16 00:50:48.877151,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.10 for name WORKGROUP<1d>.
  This response was from IP 192.168.0.30, reporting an IP address of 192.168.56.1.
[2019/01/16 00:56:19.069104,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
  *****

  Samba name server NASDJO is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.10

  *****
[2019/01/17 01:20:43.637833,  0] ../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success)
  *****

  Samba name server NASDJO has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.0.10

  *****
[2019/01/17 01:39:44.223851,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.10 for name WORKGROUP<1d>.
  This response was from IP 192.168.0.48, reporting an IP address of 192.168.0.48.
[2019/01/17 11:28:26.155576,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
  *****

  Samba name server NASDJO is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.10

  *****
[2019/01/17 11:33:29.225888,  0] ../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success)
  *****

  Samba name server NASDJO has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.0.10

  *****
[2019/01/17 12:24:30.059440,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
  *****

  Samba name server NASDJO is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.10

  *****
[2019/01/17 15:27:57.286113,  0] ../source3/nmbd/nmbd.c:58(terminate)
  Got SIGTERM: going down...
[2019/01/17 15:27:57.344003,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2019/01/17 15:29:29.159223,  0] ../source3/nmbd/nmbd.c:169(nmbd_sig_hup_handler)
  Got SIGHUP dumping debug info.
[2019/01/17 15:29:29.159365,  0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
  dump_workgroups()
   dump workgroup on subnet    192.168.0.10: netmask=  255.255.255.0:
        WORKGROUP(1) current master browser = FREEBOX
                NASDJO 40819a03 (Samba 4.5.12-Debian)
                FREEBOX 40849a03 (Freebox Server)
[2019/01/17 15:29:50.268890,  0] ../source3/nmbd/nmbd.c:58(terminate)
  Got SIGTERM: going down...
[2019/01/17 15:34:45.280980,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'nmbd' finished starting up and ready to serve connections

Aujourd’hui, c’est une adresse IP attribué par le DHCP qui fait partie de ma plage réseau mais
qui ne répond pas : ping 192.168.0.48

PING 192.168.0.48 (192.168.0.48) 56(84) bytes of data.
From 192.168.0.10 icmp_seq=1 Destination Host Unreachable
From 192.168.0.10 icmp_seq=2 Destination Host Unreachable
From 192.168.0.10 icmp_seq=3 Destination Host Unreachable
From 192.168.0.10 icmp_seq=4 Destination Host Unreachable
From 192.168.0.10 icmp_seq=5 Destination Host Unreachable
From 192.168.0.10 icmp_seq=6 Destination Host Unreachable
^C
--- 192.168.0.48 ping statistics ---
7 packets transmitted, 0 received, +6 errors, 100% packet loss, time 6125ms
pipe 4

Voila, si quelqu’un peut aidé, merci d’avance.

Almtesh · Janvier 18, 2019, 7:53am

Bonjour à toi.

Je n’ai pas suivi, c’est quelle machine qui a cette adresse IP ?

DjoMenTunes · Janvier 19, 2019, 4:51pm

Bonjour Almtesh,

J’ai retrouvé le client 192.168.0.48, c’est un client windows qui fait parti du réseau Workgroup.
Configuration dhcp freebox:
Mon ip serveur est fixe et en dehors du dhcp : 192.168.0.10
Début de plage d’adresses : 192.168.0.11
Fin de plages d’adresses : 192.168.0.50
Serveur dns 1 : 208.67.222.222
Serveur dns 2 : 208.67.220.220
Les baux statiques sont : 10, 15, 30, 45.
J’ai changé ma passerelle en 192.168.0.250.
J’ai essayé de changer mon dns-nameservers en 192.168.0.50 sans plus de résultats, pour l’erreur. Mais maintenant, je n’ai plus de réponse avec la commande nslookup, dig casa.it et dig -x 192.168.0.10. Les autres clients ne répondent pas non plus.
Je vais devoir reconfigurer avec l’ip de la passerelle. Il n’y a que comme cela que ça fonctionne.
Il y a un conflit entre les groupes de travail (WORKGROUP)du serveur et celui de ma debian.