Arch Linux

mshan

Member

Registered: 2013-05-05

Posts: 105

[SOLVED] smbd.service & nmbd.service fail to start

I can't start smbd.service and nmbd.service any more today.

[msh@localhost ~]$ sudo systemctl start smbd.service nmbd.service
Job for nmbd.service failed. See "systemctl status nmbd.service" and "journalctl -xe" for details.
Job for smbd.service failed. See "systemctl status smbd.service" and "journalctl -xe" for details.
[msh@localhost ~]$ systemctl status smbd.service nmbd.service
● smbd.service - Samba SMB/CIFS server
   Loaded: loaded (/usr/lib/systemd/system/smbd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2015-03-05 20:40:26 MMT; 22s ago
  Process: 685 ExecStart=/usr/bin/smbd -D (code=exited, status=1/FAILURE)

Mar 05 20:40:26 localhost systemd[1]: smbd.service: control process exited, code=exited status=1
Mar 05 20:40:26 localhost systemd[1]: Failed to start Samba SMB/CIFS server.
Mar 05 20:40:26 localhost systemd[1]: Unit smbd.service entered failed state.
Mar 05 20:40:26 localhost systemd[1]: smbd.service failed.

● nmbd.service - Samba NetBIOS name server
   Loaded: loaded (/usr/lib/systemd/system/nmbd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2015-03-05 20:40:26 MMT; 22s ago
  Process: 686 ExecStart=/usr/bin/nmbd -D (code=exited, status=1/FAILURE)

Mar 05 20:40:26 localhost systemd[1]: Starting Samba NetBIOS name server...
Mar 05 20:40:26 localhost systemd[1]: nmbd.service: control process exited, code=exited status=1
Mar 05 20:40:26 localhost systemd[1]: Failed to start Samba NetBIOS name server.
Mar 05 20:40:26 localhost systemd[1]: Unit nmbd.service entered failed state.
Mar 05 20:40:26 localhost systemd[1]: nmbd.service failed.

I have googled for a few hour. No helpful post found.
I also enabled the services but in vain.

[msh@localhost ~]$ sudo systemctl enable smbd.service nmbd.service
[sudo] password for msh: 
[msh@localhost ~]$ sudo systemctl start smbd.service nmbd.service
Job for smbd.service failed. See "systemctl status smbd.service" and "journalctl -xe" for details.
Job for nmbd.service failed. See "systemctl status nmbd.service" and "journalctl -xe" for details.

Last edited by mshan (2015-03-05 15:50:44)

---

Amazing !

cris9288

Member

Registered: 2013-01-07

Posts: 348

Re: [SOLVED] smbd.service & nmbd.service fail to start

well...what does journalctl say?

mshan

Member

Registered: 2013-05-05

Posts: 105

Re: [SOLVED] smbd.service & nmbd.service fail to start

well

journalctl -xe

says

journalctl -xe
Mar 05 20:51:03 localhost systemd[1]: Reloading.
Mar 05 20:51:03 localhost sudo[820]: pam_unix(sudo:session): session closed for user root
Mar 05 20:51:29 localhost sudo[832]: msh : TTY=pts/0 ; PWD=/home/msh ; USER=root ; COMMAND=/usr/bin/systemctl start smbd.service nmbd.se
Mar 05 20:51:29 localhost sudo[832]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 05 20:51:29 localhost systemd[1]: Starting Samba SMB/CIFS server...
-- Subject: Unit smbd.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit smbd.service has begun starting up.
Mar 05 20:51:29 localhost systemd[1]: Starting Samba NetBIOS name server...
-- Subject: Unit nmbd.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit nmbd.service has begun starting up.
Mar 05 20:51:29 localhost systemd[1]: smbd.service: control process exited, code=exited status=1
Mar 05 20:51:29 localhost systemd[1]: Failed to start Samba SMB/CIFS server.
-- Subject: Unit smbd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit smbd.service has failed.
-- 
-- The result is failed.
Mar 05 20:51:29 localhost systemd[1]: Unit smbd.service entered failed state.
Mar 05 20:51:29 localhost systemd[1]: smbd.service failed.
Mar 05 20:51:29 localhost systemd[1]: nmbd.service: control process exited, code=exited status=1
Mar 05 20:51:29 localhost systemd[1]: Failed to start Samba NetBIOS name server.
-- Subject: Unit nmbd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit nmbd.service has failed.
-- 
-- The result is failed.
Mar 05 20:51:29 localhost systemd[1]: Unit nmbd.service entered failed state.
Mar 05 20:51:29 localhost systemd[1]: nmbd.service failed.
Mar 05 20:51:29 localhost sudo[832]: pam_unix(sudo:session): session closed for user root
[msh@localhost ~]$ sudo systemctl start smbd.service nmbd.service
[sudo] password for msh: 
Job for nmbd.service failed. See "systemctl status nmbd.service" and "journalctl -xe" for details.
Job for smbd.service failed. See "systemctl status smbd.service" and "journalctl -xe" for details.
[msh@localhost ~]$ journalctl -xe
Mar 05 20:51:29 localhost systemd[1]: nmbd.service failed.
Mar 05 20:51:29 localhost sudo[832]: pam_unix(sudo:session): session closed for user root
Mar 05 21:00:11 localhost sudo[867]: msh : TTY=pts/0 ; PWD=/home/msh ; USER=root ; COMMAND=/usr/bin/systemctl start smbd.service nmbd.se
Mar 05 21:00:11 localhost sudo[867]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 05 21:00:11 localhost systemd[1]: Starting Samba SMB/CIFS server...
-- Subject: Unit smbd.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit smbd.service has begun starting up.
Mar 05 21:00:11 localhost systemd[1]: Starting Samba NetBIOS name server...
-- Subject: Unit nmbd.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit nmbd.service has begun starting up.
Mar 05 21:00:11 localhost systemd[1]: nmbd.service: control process exited, code=exited status=1
Mar 05 21:00:11 localhost systemd[1]: Failed to start Samba NetBIOS name server.
-- Subject: Unit nmbd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit nmbd.service has failed.
-- 
-- The result is failed.
Mar 05 21:00:11 localhost systemd[1]: Unit nmbd.service entered failed state.
Mar 05 21:00:11 localhost systemd[1]: nmbd.service failed.
Mar 05 21:00:11 localhost systemd[1]: smbd.service: control process exited, code=exited status=1
Mar 05 21:00:11 localhost systemd[1]: Failed to start Samba SMB/CIFS server.
-- Subject: Unit smbd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit smbd.service has failed.
-- 
-- The result is failed.
Mar 05 21:00:11 localhost systemd[1]: Unit smbd.service entered failed state.
Mar 05 21:00:11 localhost systemd[1]: smbd.service failed.
Mar 05 21:00:11 localhost sudo[867]: pam_unix(sudo:session): session closed for user root

---

Amazing !

cris9288

Member

Registered: 2013-01-07

Posts: 348

Re: [SOLVED] smbd.service & nmbd.service fail to start

I find that for some reason, journalctl -xe doesn't always include the actual errors. I end up just reading journalctl -r. Sometimes adding the -u flag helps to trim the output, but if you still don't see the error I would just read journalctl's full output. It's a lot more to parse through. The next step would be to post your smb.conf and to try to run those daemons from the cli. Also, have permissions on the shares changed? I would also just try rebooting as that has solved weird smbd/nmbd behavior for me before.

mshan

Member

Registered: 2013-05-05

Posts: 105

Re: [SOLVED] smbd.service & nmbd.service fail to start

journalctl -r

says

-- Logs begin at Wed 2014-12-31 23:19:43 MMT, end at Thu 2015-03-05 21:16:15 MMT. --
Mar 05 21:16:15 localhost sudo[952]: pam_unix(sudo:session): session closed for user root
Mar 05 21:16:15 localhost systemd[1]: smbd.service failed.
Mar 05 21:16:15 localhost systemd[1]: Unit smbd.service entered failed state.
Mar 05 21:16:15 localhost systemd[1]: Failed to start Samba SMB/CIFS server.
Mar 05 21:16:15 localhost systemd[1]: smbd.service: control process exited, code=exited status=1
Mar 05 21:16:15 localhost systemd[1]: nmbd.service failed.
Mar 05 21:16:15 localhost systemd[1]: Unit nmbd.service entered failed state.
Mar 05 21:16:15 localhost systemd[1]: Failed to start Samba NetBIOS name server.
Mar 05 21:16:15 localhost systemd[1]: nmbd.service: control process exited, code=exited status=1
Mar 05 21:16:15 localhost systemd[1]: Starting Samba NetBIOS name server...
Mar 05 21:16:15 localhost systemd[1]: Starting Samba SMB/CIFS server...
Mar 05 21:16:15 localhost sudo[952]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 05 21:16:15 localhost sudo[952]: msh : TTY=pts/0 ; PWD=/home/msh ; USER=root ; COMMAND=/usr/bin/systemctl start smbd.service nmbd.se
Mar 05 21:00:11 localhost sudo[867]: pam_unix(sudo:session): session closed for user root
Mar 05 21:00:11 localhost systemd[1]: smbd.service failed.
Mar 05 21:00:11 localhost systemd[1]: Unit smbd.service entered failed state.
Mar 05 21:00:11 localhost systemd[1]: Failed to start Samba SMB/CIFS server.
Mar 05 21:00:11 localhost systemd[1]: smbd.service: control process exited, code=exited status=1
Mar 05 21:00:11 localhost systemd[1]: nmbd.service failed.
Mar 05 21:00:11 localhost systemd[1]: Unit nmbd.service entered failed state.
Mar 05 21:00:11 localhost systemd[1]: Failed to start Samba NetBIOS name server.
Mar 05 21:00:11 localhost systemd[1]: nmbd.service: control process exited, code=exited status=1
Mar 05 21:00:11 localhost systemd[1]: Starting Samba NetBIOS name server...
Mar 05 21:00:11 localhost systemd[1]: Starting Samba SMB/CIFS server...
Mar 05 21:00:11 localhost sudo[867]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 05 21:00:11 localhost sudo[867]: msh : TTY=pts/0 ; PWD=/home/msh ; USER=root ; COMMAND=/usr/bin/systemctl start smbd.service nmbd.se
Mar 05 20:51:29 localhost sudo[832]: pam_unix(sudo:session): session closed for user root
Mar 05 20:51:29 localhost systemd[1]: nmbd.service failed.
Mar 05 20:51:29 localhost systemd[1]: Unit nmbd.service entered failed state.
Mar 05 20:51:29 localhost systemd[1]: Failed to start Samba NetBIOS name server.
Mar 05 20:51:29 localhost systemd[1]: nmbd.service: control process exited, code=exited status=1
Mar 05 20:51:29 localhost systemd[1]: smbd.service failed.
Mar 05 20:51:29 localhost systemd[1]: Unit smbd.service entered failed state.
Mar 05 20:51:29 localhost systemd[1]: Failed to start Samba SMB/CIFS server.
Mar 05 20:51:29 localhost systemd[1]: smbd.service: control process exited, code=exited status=1
Mar 05 20:51:29 localhost systemd[1]: Starting Samba NetBIOS name server...
Mar 05 20:51:29 localhost systemd[1]: Starting Samba SMB/CIFS server...
Mar 05 20:51:29 localhost sudo[832]: pam_unix(sudo:session): session opened for user root by (uid=0)

I read those messages but I don't know about them to solve the problem.
Ok, I will reboot the system and see it works or not.

---

Amazing !

mshan

Member

Registered: 2013-05-05

Posts: 105

Re: [SOLVED] smbd.service & nmbd.service fail to start

OK..... I check my /etc/samba directory. The problem is because of missing smb.conf file.
I don't know why it is missing because I configured samba properly and used it about one week ago.
I have created another one by

sudo cp /etc/samba/smb.conf.default /etc/samba/smb.conf

Thanks for this line in your post. It remined me to check the configuration file.

The next step would be to post your smb.conf and to try to run those daemons from the cli.

sorry for my post before things which should be checked.

Last edited by mshan (2015-03-06 03:27:21)

---

Amazing !

ashbreeze

Member

Registered: 2014-03-02

Posts: 9

Re: [SOLVED] smbd.service & nmbd.service fail to start

Yeah, well, I upgraded from 4.1.17 to 4.2.0 today, and samba won't start (/etc/samba/smb.conf exists). Yet, here is the samba error log (/var/log/samba/log.smbd)::

[2015/03/06 12:27:53,  0] ../source3/smbd/server.c:1241(main)
  smbd version 4.2.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2014
[2015/03/06 12:27:53,  0] ../source3/smbd/server.c:1256(main)
  error opening config file '/etc/samba/smb.conf'

I could not see any ownership or security issues with /etc/samba/smb.conf file...

I downgraded with the following:

sudo pacman -U \
 /var/cache/pacman/pkg/samba-4.1.17-1-x86_64.pkg.tar.xz \
 /var/cache/pacman/pkg/smbclient-4.1.17-1-x86_64.pkg.tar.xz \
 /var/cache/pacman/pkg/libwbclient-4.1.17-1-x86_64.pkg.tar.xz
 sudo systemctl stop smbd.service
 sudo systemctl stop nmbd.service
 sudo systemctl start smbd.service
 sudo systemctl start smbd.service

and I'm working again... What gives with Samba 4.2.0

Last edited by ashbreeze (2015-03-06 20:43:53)

Olegach21

Member

Registered: 2015-04-13

Posts: 1

Re: [SOLVED] smbd.service & nmbd.service fail to start

Yeah, well, I upgraded from 4.1.17 to 4.2.0 today, and samba won't start (/etc/samba/smb.conf exists). Yet, here is the samba error log (/var/log/samba/log.smbd)::

[2015/03/06 12:27:53,  0] ../source3/smbd/server.c:1241(main)
  smbd version 4.2.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2014
[2015/03/06 12:27:53,  0] ../source3/smbd/server.c:1256(main)
  error opening config file '/etc/samba/smb.conf'

I could not see any ownership or security issues with /etc/samba/smb.conf file...

I downgraded with the following:

sudo pacman -U \
 /var/cache/pacman/pkg/samba-4.1.17-1-x86_64.pkg.tar.xz \
 /var/cache/pacman/pkg/smbclient-4.1.17-1-x86_64.pkg.tar.xz \
 /var/cache/pacman/pkg/libwbclient-4.1.17-1-x86_64.pkg.tar.xz
 sudo systemctl stop smbd.service
 sudo systemctl stop nmbd.service
 sudo systemctl start smbd.service
 sudo systemctl start smbd.service

and I'm working again... What gives with Samba 4.2.0

I solve this problem by removing line "security = share" from [global] section of my smb.conf file.

mauriciootta

Member

Registered: 2012-04-05

Posts: 9

Re: [SOLVED] smbd.service & nmbd.service fail to start

Just run into this issue and could get this on my journal:
-- Unit smbd.service has begun starting up.
Sep 12 16:45:06 brain smbd[9187]: /usr/bin/smbd: error while loading shared libraries: libgnutls.so.28: cannot open shared object file: No such file or directory
Sep 12 16:45:06 brain systemd[1]: smbd.service: Control process exited, code=exited status=127
Sep 12 16:45:06 brain systemd[1]: Failed to start Samba SMB/CIFS server.
-

Which led me here:
https://bbs.archlinux.org/viewtopic.php?id=196311

then
pacman -Syy
pacman -Syu

fixed it and samba is happy again

hope this helps someone (or myself when it happens again)

parthanon

Member

Registered: 2017-11-02

Posts: 1

Re: [SOLVED] smbd.service & nmbd.service fail to start

To anybody running Samba 2:4.3.11 I had this same issue.

I discovered this in /var/log/samba/log.

[2017/08/22 19:37:30.574385,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/09/01 13:08:30.854508,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/09/01 13:42:45.205868,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/09/04 17:29:09.870033,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/09/05 23:24:41.535263,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/10/02 21:54:00.188617,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/10/23 20:39:55.735468,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/10/23 20:59:17.856120,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/10/23 21:12:15.848701,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/10/25 15:14:33.505406,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/10/25 16:25:26.263832,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/10/25 18:48:07.542979,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/10/27 16:32:55.428651,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/11/01 18:42:58.801855,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/11/02 11:09:12.474714,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700
[2017/11/02 11:28:35.232256,  0] ../lib/util/util.c:285(directory_create_or_exist_strict)
  invalid permissions on directory '/var/lib/samba/private/msg.sock': has 0777 should be 0700

Naturally setting permissions on /var/lib/samba/private/msg.sock to 0700 fixed it for me.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,001

Re: [SOLVED] smbd.service & nmbd.service fail to start

Not only do you necrobump a solved thread, you also are talking about Ubuntu which doesn't have anything to do with Arch, as such your information is completely irrelevant to this thread (and doesn't use [ code ] tags).

Please read our code of conduct should you want to further contribute to the boards.

Closing.