nmbd service problem

Borygo77 · November 26, 2019 at 12:55 AM

Hi guys! Not sure if I should care much about it but my journalctl is flooded with this warning everytime I'm going in to it....

Have three libreelec devices at home with 192.168.1.111, 112, 113.

Any chance to fix it somehow ?

Code

Nov 26 00:00:59 HTPC nmbd[939]: [2019/11/26 00:00:59.543359,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:00:59 HTPC nmbd[939]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:00:59 HTPC nmbd[939]:   This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:05:59 HTPC nmbd[939]: [2019/11/26 00:05:59.786246,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:05:59 HTPC nmbd[939]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:05:59 HTPC nmbd[939]:   This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:10:59 HTPC nmbd[939]: [2019/11/26 00:10:59.609231,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:10:59 HTPC nmbd[939]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:10:59 HTPC nmbd[939]:   This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:16:02 HTPC nmbd[939]: [2019/11/26 00:16:02.725912,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:16:02 HTPC nmbd[939]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:16:02 HTPC nmbd[939]:   This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:16:33 HTPC connmand[399]: ntp: adjust (slew): +0.000165 sec
Nov 26 00:21:09 HTPC nmbd[939]: [2019/11/26 00:21:09.523679,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:21:09 HTPC nmbd[939]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:21:09 HTPC nmbd[939]:   This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:26:19 HTPC nmbd[939]: [2019/11/26 00:26:19.811415,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:26:19 HTPC nmbd[939]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:26:19 HTPC nmbd[939]:   This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:31:12 HTPC nmbd[939]: [2019/11/26 00:31:12.158004,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:31:12 HTPC nmbd[939]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:31:12 HTPC nmbd[939]:   This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:33:37 HTPC connmand[399]: ntp: adjust (slew): +0.000423 sec
Nov 26 00:36:19 HTPC nmbd[939]: [2019/11/26 00:36:19.670959,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:36:19 HTPC nmbd[939]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:36:19 HTPC nmbd[939]:   This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:41:19 HTPC nmbd[939]: [2019/11/26 00:41:19.912215,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:41:19 HTPC nmbd[939]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:41:19 HTPC nmbd[939]:   This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.
Nov 26 00:46:19 HTPC nmbd[939]: [2019/11/26 00:46:19.539168,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 26 00:46:19 HTPC nmbd[939]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.111 for name WORKGROUP<1d>.
Nov 26 00:46:19 HTPC nmbd[939]:   This response was from IP 192.168.1.112, reporting an IP address of 192.168.1.112.

Display More

**chewitt** · November 26, 2019 at 10:13 AM Official Post

Multiple devices think they are the master browser. Eventually one of them will win the election process and the noise will stop.

Borygo77 · November 26, 2019 at 10:18 AM

It's not stopping at all Can I add something to smb.conf to change behaviour of less important two ?

Thanks for looking after

**chewitt** · November 29, 2019 at 7:07 AM Official Post

Rename /storage/.config/samba.conf.sample to /storage/.config/samba.conf and edit the file; there's a section that needs to be uncommented to make one of the devices the local browse master. You don't change the behaviour of the less important devices; you change the most important. The thing to remember is that the browse master should be something that's always on (or almost always) else you're forever forcing elections.

Borygo77 · November 29, 2019 at 7:18 AM

Thanks Chewitt! Got my own samba.conf for ages but never been checking journalctl for warnings/errors. So it was bugging me as hell.

Had this sorted same day after finding some sources in google and added line for master browser

This machine is serving files mostly so it's always on...

There is one thing I need help with. How do I stop recreating folders from /storage/ ?

If I delete videos,music,tvshows etc those always coming back after reboot. Don't like this mess really.

If there is any way to stop it can you help please ? If not I can live with it

Here is my samba journalctl

Code

Nov 29 04:09:42 HTPC nmbd[1027]: [2019/11/29 04:09:42.076960,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Nov 29 04:09:42 HTPC nmbd[1027]:   *****
Nov 29 04:09:42 HTPC nmbd[1027]: 
Nov 29 04:09:42 HTPC nmbd[1027]:   Samba name server HTPC is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1
Nov 29 04:09:42 HTPC nmbd[1027]: 
Nov 29 04:09:42 HTPC nmbd[1027]:   *****
Nov 29 04:09:42 HTPC nmbd[1027]: [2019/11/29 04:09:42.077527,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Nov 29 04:09:42 HTPC nmbd[1027]:   *****
Nov 29 04:09:42 HTPC nmbd[1027]: 
Nov 29 04:09:42 HTPC nmbd[1027]:   Samba name server HTPC is now a local master browser for workgroup WORKGROUP on subnet 172.18.0.1
Nov 29 04:09:42 HTPC nmbd[1027]: 
Nov 29 04:09:42 HTPC nmbd[1027]:   *****
Nov 29 04:09:42 HTPC nmbd[1027]: [2019/11/29 04:09:42.077948,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Nov 29 04:09:42 HTPC nmbd[1027]:   *****
Nov 29 04:09:42 HTPC nmbd[1027]: 
Nov 29 04:09:42 HTPC nmbd[1027]:   Samba name server HTPC is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.111
Nov 29 04:09:42 HTPC nmbd[1027]: 
Nov 29 04:09:42 HTPC nmbd[1027]:   *****

Display More

**chewitt** · November 29, 2019 at 8:36 AM Official Post

The /storage/folders are hard-coded and will be recreated on boot if removed. To stop that behaviour you'd need to compile a custom image with modifications to packages/mediacenter/kodi/tmpfiles.d/kodi-userdirs.conf .. just ignore them, they're harmless.

Borygo77 · November 29, 2019 at 3:58 PM

No worries! Thanks Chewitt