Hi all,
Tumbleweed, Xfce, running in VBox on Win 10 host.
For the last few days, when booting Tumbleweed I see the message “Failed to start Samba NMB Daemon” twice near the end of the boot messages. As a consequence, I cannot access network shares via the file manager. I tried enabling the service in YaST, but that fails too.
This seems to be a consequence of a recent update, since network was fine before.
Any ideas will be most welcome!
I don’t have any personal experience with this. I’m not running a samba service on my Tumbleweed system.
However, there have been reports of problem.
What I gather, is that people who have been using their desktop update applet are having problems, and people who have been using “zypper up” have been having problems. But people using “zypper dup” apparently do okay.
The difference is that “zypper dup” will remove older packages that otherwise cause conflicts, while “zypper up” wont.
If this seems to fit your problem, then try “zypper dup”.
If you are using other repos, such that “zypper dup” might cause problems, then at least try:
# zypper dup -D
That’s a dry run. It won’t change anything. But you will get a better idea of what it wants to remove and what other conflicts that it finds.
Thank you for this. Unfortunately, zypper dup did not solve the problem.
I have fixed it: I needed to stop the smb.service before doing the upgrade (Samba was set in YaST to start at boot, which I think is not the default option).
Okay now, this was way back in April -BUT- I am also experiencing the problem now. The scenario is a little different in that I am running on a Linux Host with Windows 10 inside VMware 12. The “nmb” services do NOT start at my boot up. I must go into the “Services Manager” and start them myself. It claims that it is “writing configuration” but the next time I need to ShutDown or ReBoot the nmb service does not get started. This has just happened since I upgraded to Leap 42.1 in July, 2016. I was previously on openSuSE 13.2 and did not have this problem. Didn’t have it with any of the previous SuSE’s either. 
Is there a fix for this or is it the “New Ways”??? I don’t believe that I should have to go into Services and restart nmb on every ReBoot.
Well darn!! I put code tages around these… I’ll have to ReBoot in order to get these again and then try QUOTE.
nmb.service - Samba NMB Daemon Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled) Active: failed (Result: exit-code) since Sat 2016-09-17 10:11:14 MST; 4h 52min ago Main PID: 1179 (code=exited, status=1/FAILURE) Status: "daemon failed to start: NMBD failed when creating subnet lists"
Sep 17 10:11:14 Dakotah-i7 nmbd[1179]: bind failed on port 137 socket_addr = 192.168.0.63. Sep 17 10:11:14 Dakotah-i7 nmbd[1179]: Error = Cannot assign requested address Sep 17 10:11:14 Dakotah-i7 nmbd[1179]: [2016/09/17 10:11:14.076463, 0] ../source3/nmbd/nmbd_subnetdb.c:113(make_subnet) Sep 17 10:11:14 Dakotah-i7 nmbd[1179]: nmbd_subnetdb:make_subnet() Sep 17 10:11:14 Dakotah-i7 nmbd[1179]: Failed to open nmb socket on interface 192.168.0.63 for port 137. Error was Cannot assign requested address Sep 17 10:11:14 Dakotah-i7 nmbd[1179]: [2016/09/17 10:11:14.076493, 0] ../lib/util/become_daemon.c:111(exit_daemon) Sep 17 10:11:14 Dakotah-i7 nmbd[1179]: STATUS=daemon failed to start: NMBD failed when creating subnet lists, error code 13 Sep 17 10:11:14 Dakotah-i7 systemd[1]: nmb.service: main process exited, code=exited, status=1/FAILURE Sep 17 10:11:14 Dakotah-i7 systemd[1]: Failed to start Samba NMB Daemon. Sep 17 10:11:14 Dakotah-i7 systemd[1]: Unit nmb.service entered failed state.
After I use Service Manager. start it, exit Yast and come back in:
nmb.service - Samba NMB Daemon Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled) Active: active (running) since Sat 2016-09-17 15:16:19 MST; 10min ago Main PID: 5342 (nmbd) Status: "nmbd: ready to serve connections..." CGroup: /system.slice/nmb.service |-5342 /usr/sbin/nmbd -D `-5343 /usr/sbin/nmbd -D
Sep 17 15:16:33 Dakotah-i7 nmbd[5342]: Sep 17 15:16:33 Dakotah-i7 nmbd[5342]: Samba server DAKOTAH-I7 is now a domain master browser for workgroup TRCOMPUTING on subnet 192.168.0.63 Sep 17 15:16:33 Dakotah-i7 nmbd[5342]: Sep 17 15:16:33 Dakotah-i7 nmbd[5342]: ***** Sep 17 15:16:41 Dakotah-i7 nmbd[5342]: [2016/09/17 15:16:41.173798, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Sep 17 15:16:41 Dakotah-i7 nmbd[5342]: ***** Sep 17 15:16:41 Dakotah-i7 nmbd[5342]: Sep 17 15:16:41 Dakotah-i7 nmbd[5342]: Samba name server DAKOTAH-I7 is now a local master browser for workgroup TRCOMPUTING on subnet 192.168.0.63 Sep 17 15:16:41 Dakotah-i7 nmbd[5342]: Sep 17 15:16:41 Dakotah-i7 nmbd[5342]: *****
Oh darn, I could not edit my previous message but here are the two section that were scrambled.:
nmb.service - Samba NMB Daemon
Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled)
Active: failed (Result: exit-code) since Sat 2016-09-17 15:48:53 MST; 2min 17s ago
Process: 1162 ExecStart=/usr/sbin/nmbd $NMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 1162 (code=exited, status=1/FAILURE)
Status: “daemon failed to start: NMBD failed when creating subnet lists”
Error: 13 (Permission denied)
Sep 17 15:48:53 Dakotah-i7 nmbd[1162]: bind failed on port 137 socket_addr = 192.168.0.63.
Sep 17 15:48:53 Dakotah-i7 nmbd[1162]: Error = Cannot assign requested address
Sep 17 15:48:53 Dakotah-i7 nmbd[1162]: [2016/09/17 15:48:53.543070, 0] …/source3/nmbd/nmbd_subnetdb.c:113(make_subnet)
Sep 17 15:48:53 Dakotah-i7 nmbd[1162]: nmbd_subnetdb:make_subnet()
Sep 17 15:48:53 Dakotah-i7 nmbd[1162]: Failed to open nmb socket on interface 192.168.0.63 for port 137. Error was Cannot assign requested address
Sep 17 15:48:53 Dakotah-i7 nmbd[1162]: [2016/09/17 15:48:53.543116, 0] …/lib/util/become_daemon.c:111(exit_daemon)
Sep 17 15:48:53 Dakotah-i7 nmbd[1162]: STATUS=daemon failed to start: NMBD failed when creating subnet lists, error code 13
Sep 17 15:48:53 Dakotah-i7 systemd[1]: nmb.service: main process exited, code=exited, status=1/FAILURE
Sep 17 15:48:53 Dakotah-i7 systemd[1]: Failed to start Samba NMB Daemon.
Sep 17 15:48:53 Dakotah-i7 systemd[1]: Unit nmb.service entered failed state.
=============
nmb.service - Samba NMB Daemon
Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled)
Active: active (running) since Sat 2016-09-17 15:51:59 MST; 21s ago
Main PID: 3122 (nmbd)
Status: “nmbd: ready to serve connections…”
CGroup: /system.slice/nmb.service
|-3122 /usr/sbin/nmbd -D
`-3123 /usr/sbin/nmbd -D
Sep 17 15:52:05 Dakotah-i7 nmbd[3122]: become_domain_master_browser_bcast:
Sep 17 15:52:05 Dakotah-i7 nmbd[3122]: Attempting to become domain master browser on workgroup TRCOMPUTING on subnet 192.168.0.63
Sep 17 15:52:05 Dakotah-i7 nmbd[3122]: [2016/09/17 15:52:05.402150, 0] …/source3/nmbd/nmbd_become_dmb.c:307(become_domain_master_browser_bcast)
Sep 17 15:52:05 Dakotah-i7 nmbd[3122]: become_domain_master_browser_bcast: querying subnet 192.168.0.63 for domain master browser on workgroup TRCOMPUTING
Sep 17 15:52:13 Dakotah-i7 nmbd[3122]: [2016/09/17 15:52:13.411954, 0] …/source3/nmbd/nmbd_become_dmb.c:112(become_domain_master_stage2)
Sep 17 15:52:13 Dakotah-i7 nmbd[3122]: *****
Sep 17 15:52:13 Dakotah-i7 nmbd[3122]:
Sep 17 15:52:13 Dakotah-i7 nmbd[3122]: Samba server DAKOTAH-I7 is now a domain master browser for workgroup TRCOMPUTING on subnet 192.168.0.63
Sep 17 15:52:13 Dakotah-i7 nmbd[3122]:
Sep 17 15:52:13 Dakotah-i7 nmbd[3122]: *****