[samba] can not see shares on one host (laptop) in the workgroup

English Network/Internet
1

Greetings !!

I recently had problems using smb4k which can not access the shares on the domain master host (ANTARES).
I used dolphin and saw a strange behaviour that I never had before:

the workgroup has three computers: two in 13.2 (one laptop wifi and one desktop eth) and one 12.2 (the samba server).

All computers are servers, ANTARES is PDC, CYRIUS is not a DC and RASALGETHI is not a DC (but is a master browser for the network in the lab at school)

The whole of them are set to be in the same workgroup.

The issue is the following: when I browse using dolphin (because smb4k seems to have a big problem) I can see ANTARES and CYRIUS, BUT NOT RASALGETHI.

I checked my router settings but it seems there is no filtering between wifi and ethernet.

I restarted the servers on all computers waited 15 minutes before getting back to dolphin: same results.

On rasalgethi there is no way to start nmb.service.

It has worked (looking at the logs untill 18 april 2016… but could not be launched since.

2

Probably you have run systemctl to get status, but if in case not then run this command and see what it says, might be some clues:

systemctl -l status nmb.service   ; systemctl -l status smb.service
3

All I got is

[2016/04/28 12:33:08.116375,  1]** ../source3/lib/messages_dgm.c:233(messaging_dgm_init)
  messaging_dgm_init: messaging_dgm_create_lockfile failed: Permission denied**

But nothing more that would drive to a clue to solve this issue…
These lines are coming from the /var/log/samba/log.nmbd

I used journalctl -u nmb.service but it didn’t gave me any usefull informations but nmb.service failed ^^

The version of samba is:

**

**Samba version 4.2.4-34.1-3638-SUSE-oS13.2-x86_64**

**

on both 13.2 computers (laptop – rasalgethi and desktop – cyrius)

I did not yet tried with a leap client to see if it is able to connect to the opensuse 12.2 samba server (antares)

I compared the 13.2 folders in **/var/lib/samba/**concerning the **access rights **but it seems they are similar…

4

Samba versions:
ANTARES (pdc) Samba version 3.6.7-48.28.1-3108-SUSE-SL12.2-x86_64 [192.168.0.3]

CYRIUS (not pdc) Samba version 4.2.4-34.1-3638-SUSE-oS13.2-x86_64 [192.168.0.4]
LEAP (not pdc) Samba version 4.2.4-12.1-3616-SUSE-SLE_12-x86_64 [192.168.0.6]

All shares are accessible without any problems (even if using smb4k) using dolphin.

That is the initial situation… now I boot the problematic 13.2 opensuse laptop which could not launch nmb.service.

Note that smb4k can not work anymore on CYRIUS, but it is not very important.

http://paste.opensuse.org/77321702 this is the rasalgethi view
http://paste.opensuse.org/68145308 this is the leap view
http://paste.opensuse.org/67285419 this is the antares view
http://paste.opensuse.org/85160825 this is the cyrius view

I can access samba shares by using mount.cifs as shown here:

http://paste.opensuse.org/7237339 shows a share has been mounted without any problem using konsole

The problem is: smbtree never shows the shares as nmb.service could not be launched…

How can I fix this ?

5

Extracts from journactl -u nmb: http://paste.opensuse.org/24900006

6

Although the full log is nice for completeness, you might run the “systemctl status” commands as follows, included will be relevant log snippets to whether the service succeeded or failed starting up.

systemctl status nmb.service

and

systemctl status smb.service

TSU

7

thank you tsu2…

as said in the previous posts, systemctl status nmb.service gives

nmb.service - Samba NMB Daemon
   Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled)
   Active: failed (Result: exit-code) since Fri 2016-04-29 17:26:28 CEST; 4min 38s ago
  Process: 1086 ExecStart=/usr/sbin/nmbd $NMBDOPTIONS (code=exited, status=1/FAILURE)
 Main PID: 1086 (code=exited, status=1/FAILURE)

Apr 29 17:26:28 rasalgethi.dezordi.world systemd[1]: Starting Samba NMB Daemon...
Apr 29 17:26:28 rasalgethi.dezordi.world systemd[1]: nmb.service: main process exited, code=exited, status=1/FAILURE
Apr 29 17:26:28 rasalgethi.dezordi.world systemd[1]: Failed to start Samba NMB Daemon.
Apr 29 17:26:28 rasalgethi.dezordi.world systemd[1]: Unit nmb.service entered failed state.

That is not enough to know what to do to fix the fact nmb.service won’t launch…

I’m trying stuffs like: uninstall samba (as I imagine that nmb.service is linked with and hope nmbd will be uninstalled with smbd)…
delete all stuffs related to samba after have saved the config files…

install samba and try again…

8

That didn’t worked :{

9

Thanks for showing this:

nmb.service - Samba NMB Daemon
   Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled)
   Active: failed (Result: exit-code) since Fri 2016-04-29 17:26:28 CEST; 4min 38s ago
  Process: 1086 ExecStart=/usr/sbin/nmbd $NMBDOPTIONS (code=exited, status=1/FAILURE)
 Main PID: 1086 (code=exited, status=1/FAILURE)

Apr 29 17:26:28 rasalgethi.dezordi.world systemd[1]: Starting Samba NMB Daemon...
Apr 29 17:26:28 rasalgethi.dezordi.world systemd[1]: nmb.service: main process exited, code=exited, status=1/FAILURE
Apr 29 17:26:28 rasalgethi.dezordi.world systemd[1]: Failed to start Samba NMB Daemon.
Apr 29 17:26:28 rasalgethi.dezordi.world systemd[1]: Unit nmb.service entered failed state.

Nmb is failing as we thought. So now perhaps do one of two quick options:

  1. make a bug report with focus on the data you have from running systemctl but do use the version I suggested i.e.
systemctl -l status nmb.service   ; systemctl -l status smb.service

because that tells them more than the abbreviated version you are using

  1. take out/uninstall the Samba version you are using, all of it, completely. And install the available earlier version. See how that goes.
10

If you do make a bug report, then pro tem do not overwhelm them with raselgethi, antares, leap, smb4k and so on. Let them lead you from the info of systemctl. That nmb failure is a strong thing to look at already.

11

I assume that you have done this, but just in case: have you checked in Yast ==> System ==> Services ==> nmb (Samba NMB daemon) ==> set to “enabled” and “active”.

12

As you already know, you still haven’t gathered enough info to start actually troubleshooting.
From the error, the next thing I’d look at is your actual configuration, in particular what is in $NMBDOPTIONS.
I don’t know if you can echo the contents or you might need to look at some documentation or the SAMBA Unit file to see how that variable is created.
If you have a default or can find a likely working configuration for that, you can try replacing to test.

TSU

13

Thank you tsu2

## Type:           string
## Default:        "-D"
## ServiceRestart:·nmb
NMBDOPTIONS="-D"
## Type:           string
## Default:        "-D"
## ServiceRestart:·smb
SMBDOPTIONS="-D"
## Type:           string
## Default:        "-D"
## ServiceRestart:·winbind
WINBINDOPTIONS="-D"

The nmboptionsjust contains the flags/options to be set up when nmb is launched at boot.
Up there you have the extract of the /etc/sysconfig/samba file.

Yes I don’t know what is happening… what happened that caused nmb to stop working (yes, the version of samba changed but it works on leap and the other 13.2 computer).
You are right I’m just gathering informations to have an explanation…

Nothing shown indicates why it doesn’t work any more and how to fix it.

14

Shame on me :{

To fix this: disable apparmor, relaunch nmb → it worked !!