Mailinglist Archive: opensuse (1108 mails)

< Previous Next >
[opensuse] nmb warning spam log problem
Hi,

I get tons of these in one machine:

3.3> 2018-08-24T09:28:18.326441+02:00 Isengard nmbd 1916 - - [2018/08/24
09:28:18.324888, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
<3.3> 2018-08-24T09:28:18.326905+02:00 Isengard nmbd 1916 - -
query_name_response: Multiple (5) responses received for a query on subnet
192.168.1.16 for name VALINOR<1d>.
<3.3> 2018-08-24T09:28:18.327370+02:00 Isengard nmbd 1916 - - This response
was from IP 192.168.1.127, reporting an IP address of 192.168.1.133.
<3.3> 2018-08-24T09:28:18.327828+02:00 Isengard nmbd 1916 - - [2018/08/24
09:28:18.325062, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
<3.3> 2018-08-24T09:28:18.328270+02:00 Isengard nmbd 1916 - -
query_name_response: Multiple (6) responses received for a query on subnet
192.168.1.16 for name VALINOR<1d>.
<3.3> 2018-08-24T09:28:18.328682+02:00 Isengard nmbd 1916 - - This response
was from IP 192.168.1.133, reporting an IP address of 192.168.1.133.



I noticed that my new laptop had two IPs, one for eth0 (192.168.1.127), another
for wlan1 (192.168.1.133):


Legolas:~ # ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.127 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::f8a0:12a3:7a65:18ab prefixlen 64 scopeid 0x20<link>
ether 1c:83:41:1b:d8:33 txqueuelen 1000 (Ethernet)
RX packets 173184437 bytes 261211510301 (243.2 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 13362130 bytes 1740900496 (1.6 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 77400 bytes 528057081 (503.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 77400 bytes 528057081 (503.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.133 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::f034:b90c:d529:7757 prefixlen 64 scopeid 0x20<link>
ether a0:d3:7a:a5:1d:4c txqueuelen 1000 (Ethernet)
RX packets 155595 bytes 10333132 (9.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4087 bytes 420175 (410.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Legolas:~ #


Supposedly, when both wlan and eth are active (there is no button to deactivate
wlan in this laptop), routing makes only eth "work". But other machines are
seeing the wlan connection.

I managed to switch off wlan (rcnetwork stop wlan1), now the messages are:

<3.3> 2018-08-24T10:03:35.127128+02:00 Isengard nmbd 1916 - - [2018/08/24
10:03:35.126858, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
<3.3> 2018-08-24T10:03:35.128335+02:00 Isengard nmbd 1916 - -
query_name_response: Multiple (2) responses received for a query on subnet
192.168.1.16 for name VALINOR<1d>.
<3.3> 2018-08-24T10:03:35.128843+02:00 Isengard nmbd 1916 - - This response
was from IP 192.168.1.127, reporting an IP address of 192.168.1.127.
<3.3> 2018-08-24T10:08:39.210789+02:00 Isengard nmbd 1916 - - [2018/08/24
10:08:39.210362, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
<3.3> 2018-08-24T10:08:39.211933+02:00 Isengard nmbd 1916 - -
query_name_response: Multiple (2) responses received for a query on subnet
192.168.1.16 for name VALINOR<1d>.
<3.3> 2018-08-24T10:08:39.212556+02:00 Isengard nmbd 1916 - - This response
was from IP 192.168.1.127, reporting an IP address of 192.168.1.127.

It still complains about the same IPs. So I restart smb on Legolas.

<3.3> 2018-08-24 10:13:39 Legolas smbd 4378 - - STATUS=daemon 'smbd'
finished starting up and ready to serve connections


Still, same problem on Isengard:

<3.3> 2018-08-24T10:13:48.255147+02:00 Isengard nmbd 1916 - - [2018/08/24
10:13:48.254873, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
<3.3> 2018-08-24T10:13:48.256303+02:00 Isengard nmbd 1916 - -
query_name_response: Multiple (2) responses received for a query on subnet
192.168.1.16 for name VALINOR<1d>.
<3.3> 2018-08-24T10:13:48.256937+02:00 Isengard nmbd 1916 - - This response
was from IP 192.168.1.127, reporting an IP address of 192.168.1.127.



What is it really complaining about, why does it keep filling the log with
thousands of entries like that? How can I stop it?

Notice that it is the WARN log which is filling up.



--
Cheers / Saludos,

Carlos E. R.
(from 42.3 x86_64 "Malachite" at Telcontar)

< Previous Next >