nmb (samba naming) not working

Hi

I noticed a couple of days ago that my Tumbleweed machine was not reachable on a mapped drive in a windows 8 machine.

So I checked in Yast → services, and nmb is enabled + inactive

So systemctl says this:

Tumbleweed132:/home/john # systemctl status nmb.service
nmb.service - Samba NMB Daemon
   Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled)
   Active: failed (Result: exit-code) since Tue 2015-03-24 09:00:45 AEST; 16s ago
  Process: 3610 ExecStart=/usr/sbin/nmbd $NMBDOPTIONS (code=exited, status=1/FAILURE)
 Main PID: 3610 (code=exited, status=1/FAILURE)

and journalctl says this (and I don’t understand it but it seems to say nothing about nmbd).

Tumbleweed132:/home/john # journalctl -xn
-- Logs begin at Thu 2014-11-13 21:34:50 AEST, end at Tue 2015-03-24 09:03:37 AEST. --
Mar 24 09:03:04 Tumbleweed132 kernel: SFW2-INext-ACC-TCP IN=enp0s25 OUT= MAC=00:24:e8:fc:dd:b5:00:24:01:e2:8a:33:08:00 SRC=84
Mar 24 09:03:11 Tumbleweed132 kernel: SFW2-INext-DROP-DEFLT IN=enp0s25 OUT= MAC=33:33:00:00:00:fb:00:24:e8:43:09:a3:86:dd SRC
Mar 24 09:03:12 Tumbleweed132 kernel: SFW2-INext-DROP-DEFLT IN=enp0s25 OUT= MAC=33:33:00:00:00:fb:00:24:e8:43:09:a3:86:dd SRC
Mar 24 09:03:12 Tumbleweed132 kernel: SFW2-INext-ACC-TCP IN=enp0s25 OUT= MAC=00:24:e8:fc:dd:b5:00:24:01:e2:8a:33:08:00 SRC=91
Mar 24 09:03:13 Tumbleweed132 kernel: SFW2-INext-ACC-TCP IN=enp0s25 OUT= MAC=00:24:e8:fc:dd:b5:00:24:01:e2:8a:33:08:00 SRC=91
Mar 24 09:03:13 Tumbleweed132 kernel: SFW2-INext-ACC-TCP IN=enp0s25 OUT= MAC=00:24:e8:fc:dd:b5:00:24:01:e2:8a:33:08:00 SRC=91
Mar 24 09:03:14 Tumbleweed132 kernel: SFW2-INext-DROP-DEFLT IN=enp0s25 OUT= MAC=33:33:00:00:00:fb:00:24:e8:43:09:a3:86:dd SRC
Mar 24 09:03:14 Tumbleweed132 kernel: SFW2-INext-ACC-TCP IN=enp0s25 OUT= MAC=00:24:e8:fc:dd:b5:00:24:01:e2:8a:33:08:00 SRC=91
Mar 24 09:03:15 Tumbleweed132 kernel: SFW2-INext-ACC-TCP IN=enp0s25 OUT= MAC=00:24:e8:fc:dd:b5:00:24:01:e2:8a:33:08:00 SRC=91
Mar 24 09:03:37 Tumbleweed132 kernel: SFW2-INext-DROP-DEFLT IN=enp0s25 OUT= MAC=00:24:e8:fc:dd:b5:00:24:01:e2:8a:33:08:00 SRC
lines 1-11/11 (END)

Any Thoughts?

Those are log entries from SuSEfirewall2.

Any Thoughts?

Try to disable AppArmor, or put it into “complain” mode:
https://bugzilla.opensuse.org/show_bug.cgi?id=923201

Thanks, that fixed it

For others, if you use AppArmor: enter su and run this: aa-complain /etc/apparmor.d/usr.sbin.nmbd

Tumbleweed132:/home/john # aa-complain /etc/apparmor.d/usr.sbin.nmbd
Setting /etc/apparmor.d/usr.sbin.nmbd to complain mode.

Then you can start the service

Tumbleweed132:/home/john # systemctl start nmb.service

and if you like to check it

Tumbleweed132:/home/john # systemctl status nmb.service
nmb.service - Samba NMB Daemon
   Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled)
   Active: active (running) since Tue 2015-03-24 09:44:45 AEST; 11s ago
 Main PID: 4058 (nmbd)
   Status: "nmbd: ready to serve connections..."
   CGroup: /system.slice/nmb.service
           └─4058 /usr/sbin/nmbd -D

Mar 24 09:44:45 Tumbleweed132 nmbd[4058]: [2015/03/24 09:44:45.521432,  0] ../lib/util/become_daemon.c:124(daemon_ready)
Mar 24 09:44:45 Tumbleweed132 nmbd[4058]: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
Tumbleweed132:/home/john #