Samba doesn’t work after core update 159 -> 160

Add-Ons
1

Samba was working fine before I updated to core 160.

Now I get:

|NetBIOS Nameserver Daemon |LÄUFT|
|SMB Daemon |ANGEHALTEN|
|Winbind Daemon |LÄUFT|

Uninstalled samba with all dependencies and reinstalled it. As expected the old config was still there (always having junk left on the system) and therefore no change.

Log entries before:

18:54:27	nmbd	[2021/10/05 18:54:27.196385, 0] ../../lib/util/become_daemon.c:135(daemon_read y)
18:54:27	nmbd	daemon_ready: daemon 'nmbd' finished starting up and ready to serve connectio ns
18:54:27	smbd	[2021/10/05 18:54:27.565911, 0] ../../lib/util/become_daemon.c:135(daemon_read y)
18:54:27	smbd	daemon_ready: daemon 'smbd' finished starting up and ready to serve connectio ns
18:54:50	nmbd	[2021/10/05 18:54:50.229654, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(becom e_local_master_stage2)
18:54:50	nmbd	*****
18:54:50	nmbd	
18:54:50	nmbd	Samba name server MM-FW-001 is now a local master browser for workgroup MMWOR X on subnet 172.24.0.254
18:54:50	nmbd	
18:54:50	nmbd	*****
18:54:50	nmbd	[2021/10/05 18:54:50.229827, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(becom e_local_master_stage2)
18:54:50	nmbd	*****
18:54:50	nmbd	
18:54:50	nmbd	Samba name server MM-FW-001 is now a local master browser for workgroup MMWOR X on subnet 172.25.0.254
18:54:50	nmbd	
18:54:50	nmbd	*****

Afterwards:

18:57:00	nmbd	[2021/10/05 18:57:00.356830, 0] ../../source3/libsmb/nmblib.c:923(send_udp)
18:57:00	nmbd	Packet send failed to 172.24.3.255(138) ERRNO=Operation not permitted
18:57:00	nmbd	[2021/10/05 18:57:00.356976, 0] ../../source3/libsmb/nmblib.c:923(send_udp)
18:57:00	nmbd	Packet send failed to 172.24.3.255(138) ERRNO=Operation not permitted
18:57:00	nmbd	[2021/10/05 18:57:00.357031, 0] ../../source3/libsmb/nmblib.c:923(send_udp)
18:57:00	nmbd	Packet send failed to 172.25.3.255(138) ERRNO=Operation not permitted
18:57:00	nmbd	[2021/10/05 18:57:00.357074, 0] ../../source3/libsmb/nmblib.c:923(send_udp)
18:57:00	nmbd	Packet send failed to 172.25.3.255(138) ERRNO=Operation not permitted
18:59:43	nmbd	[2021/10/05 18:59:43.546840, 0] ../../source3/nmbd/nmbd.c:60(terminate)
18:59:43	nmbd	Got SIGTERM: going down...
18:59:43	nmbd	[2021/10/05 18:59:43.546983, 0] ../../source3/libsmb/nmblib.c:923(send_udp)
18:59:43	nmbd	Packet send failed to 172.24.3.255(138) ERRNO=Operation not permitted
18:59:43	nmbd	[2021/10/05 18:59:43.547032, 0] ../../source3/libsmb/nmblib.c:923(send_udp)
18:59:43	nmbd	Packet send failed to 172.24.3.255(138) ERRNO=Operation not permitted
18:59:43	nmbd	[2021/10/05 18:59:43.547074, 0] ../../source3/libsmb/nmblib.c:923(send_udp)
18:59:43	nmbd	Packet send failed to 172.25.3.255(138) ERRNO=Operation not permitted
18:59:43	nmbd	[2021/10/05 18:59:43.547110, 0] ../../source3/libsmb/nmblib.c:923(send_udp)
18:59:43	nmbd	Packet send failed to 172.25.3.255(138) ERRNO=Operation not permitted

etc.

2

These error messages have nothing to do with the bug. I restored core 159 and samba works fine with the same messages.

I also reinstalled core 160, restored the config (without samba) and the samba daemon stays down.

3

Have you rebooted after samba update? the old samba sometimes refuse to full terminate and blocks start of the new updated binary. My system is on next (core161) and samba works.

4

I restarted several times but the problem seems to be bigger. I still run 159 and it worked fine after I restored it yesterday. However I just started the fw today and the samba daemon is down and can’t be started. So I updated to 160 again and still not working. I don’t understand the errors. I have no idea why it fails on the subnets 172.24.3.255 and 172.25.3.255. Those nets are DHCP and have no rights on my networks. They are spare holders for new/unknown clients that connect to the network for its first time. However it worked before. Also it’s looking for a guest account samba?!? In the old logs I haven’t seen these errors:

17:46:11	smbd	[2021/10/06 17:46:11.922158, 0] ../../source3/auth/auth_util.c:1313(get_guest_ info3)
17:46:11	smbd	SamInfo3_for_guest: Unable to locate guest account [samba]!
17:46:11	smbd	[2021/10/06 17:46:11.922230, 0] ../../source3/auth/auth_util.c:1385(make_new_s ession_info_guest)
17:46:11	smbd	get_guest_info3 failed with NT_STATUS_NO_SUCH_USER
17:46:11	smbd	[2021/10/06 17:46:11.922260, 0] ../../source3/smbd/server.c:2058(main)
17:46:11	smbd	ERROR: failed to setup guest info.
5

OK that’s the point. Manually created the user “samba” → working again. Deleted the user and restart samba - not working!

I wonder that I didn’t encounter the problem before. However is this a bug or not? Why am I forced to have an user “samba”.

6

I had this problem in the past - had to recreate the samba user.

But that happened long time ago.

I never upgraded above 158…so my problem had to be before this version.