Job for smbd service failed because the control process exited with error code - Исправление ошибок и поиск оптимальных решений проблем

Печать

Страницы: [1] 2 Все Вниз

Тема: Проблема с запуском Samba (Прочитано 12325 раз)

0 Пользователей и 1 Гость просматривают эту тему.

xpforest

Всем привет!
Ситуация следующая. Стоит Ubuntu Server 16.04 x64 LTS.
Настраивал доступ к шаре через Webmin, попытался перезапустить самбу, как вдруг мне выдало сообщение:

Failed to start Samba servers : service smbd start ; service nmbd start failedПри попытке перезапустить самбу через терминал выдало следующее:

Job for smbd.service failed because the control process exited with error code. See "systemctl status smbd.service" and "journalctl -xe" for details.Кто-нибудь сталкивался с подобным?

« Последнее редактирование: 31 Мая 2016, 20:28:46 от xpforest »

Че, родимый, еще рассказать тебе?

victor00000

xpforest

victor00000, эммм? версии? Подскажи, пожалуйста

Че, родимый, еще рассказать тебе?

victor00000

честно эту apt-get install samba?

wolfser2701

xpforest,

эммм? версии? Подскажи, пожалуйста

Где нибудь рядом видел проблемы с версиями самбы 4.3.8 и 4.3.9 , сообщество в ауте.

xpforest

victor00000, ну да, ставил именно так.
wolfser2701, у меня 4.3.9

Че, родимый, еще рассказать тебе?

victor00000

xpforest,

wolfser2701, у меня 4.3.9

зачем показывай версии?

xpforest

victor00000, в смысле «Показывай версии»?)) Мужчина, я Вас не понимаю)))))я еще слишком зеленый в линуксе)))

Че, родимый, еще рассказать тебе?

wolfser2701

victor00000, Вот что? Ты не видел проблем с обновлениями самбы до 3.8 и 3.9 ?

victor00000

wolfser2701, просто install samba, никаких версии.

xpforest

wolfser2701, victor00000, после выполнения команды sudo apt-get install samba выдало следующее:

samba is already the newest version (2:4.3.9+dfsg-0ubuntu0.16.04.2). обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 3 пакетов не обновлено.

Че, родимый, еще рассказать тебе?

wolfser2701

victor00000, Ты же видел, сколько этих самб упало, может подождём твою маму, Подождём Твою Мать.

xpforest

wolfser2701, у всех чтоль такая хреновина с морковиной? (как бы выразилась моя бабуля)

Че, родимый, еще рассказать тебе?

victor00000

xpforest,
а как дела

smbclient -L 127.0.0.1 -N?

xpforest

victor00000,

WARNING: The "syslog" option is deprecated WARNING: Ignoring invalid value 'share' for parameter 'security' smbclient: Can't load /etc/samba/smb.conf - run testparm to debug it Connection to 127.0.0.1 failed (Error NT_STATUS_CONNECTION_REFUSED)

« Последнее редактирование: 31 Мая 2016, 21:40:22 от xpforest »

Че, родимый, еще рассказать тебе?

Печать

Страницы: [1] 2 Все Вверх

Источник

Forum
The Ubuntu Forum Community
Ubuntu Specialised Support
Ubuntu Servers, Cloud and Juju
Server Platforms
[SOLVED] Unable to restart SAMBA — ubuntu server 18.04

Unable to restart SAMBA — ubuntu server 18.04

Hi

Have edited /etc/samba/smb.conf using code carried forward from previous working server installations and modified paths as required.
Code:
sudo service smbd restart
results in
Code:
Job for smbd.service failed because the control process exited with error code.
See "systemctl status smbd.service" and "journalctl -xe" for details.
Code:
systemctl status smbd.service
produces
Code:
● smbd.service - Samba SMB Daemon
   Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2018-08-11 16:18:17 UTC; 12min ago
     Docs: man:smbd(8)
           man:samba(7)
           man:smb.conf(5)
  Process: 4463 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
 Main PID: 4463 (code=exited, status=1/FAILURE)

Aug 11 16:18:16 econel-200 systemd[1]: Starting Samba SMB Daemon...
Aug 11 16:18:17 econel-200 systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Aug 11 16:18:17 econel-200 systemd[1]: smbd.service: Failed with result 'exit-code'.
Aug 11 16:18:17 econel-200 systemd[1]: Failed to start Samba SMB Daemon.
Ideas please?

TIA

Re: Unable to restart SAMBA — ubuntu server 18.04

Did you modify just parts of the smb.conf or you replaced the whole content from a previous version? I had similar problems when replacing the whole file. It seems they are not 100% compatible between versions.

I suggest you try keeping the default smb.conf that comes with 18.04 and in it you add only the parts that you need. Try modifying bit by bit, restarting samba along the way to confirm it didn’t break.

Darko.
————————————————————————
Ubuntu 18.04 LTS 64bit
Re: Unable to restart SAMBA — ubuntu server 18.04

If you didn’t make a copy of your default smb.conf there is another one at: /usr/share/samba/smb.conf

I can easily reproduce that error by adding a line in the [global] section: security = share. Many users had that in their smb.conf files from way back but it’s not a real option anymore and stops smbd from running.

That may not be your exact issue but if you run the following command it may provide an error massage:
Re: Unable to restart SAMBA — ubuntu server 18.04
Darkod, Morbius1

Thanks for your replies.

Replaced modified smb.conf with the default smb.conf, tested, fine.

Appended a share to smb.conf, tested, fine, excepting that the server is not visible to any Windows device on the WORKGROUP network.

Access via other linux boxes is ok.

In the smb.conf used for previous O/Ss, there was under Global settings
Code:

netbios name = ServerName
a reference to presumably identify the server on the WORKGROUP network.

Unable to locate any such or similar reference in the current smb.conf — so what’s missing please?
Re: Unable to restart SAMBA — ubuntu server 18.04
In the smb.conf used for previous O/Ss, there was under Global settings Code:
netbios name = ServerName
a reference to presumably identify the server on the WORKGROUP network.

Unable to locate any such or similar reference in the current smb.conf

It is usually not necessary to add that line because it is in the defaults ( smb.conf does not hold the defaults for samba only overrides ).

If you run this command you should see the default sets the netbios name to the host name:
Code:

testparm -sv /dev/null | grep "netbios name"
There is one problem with using netbios and that is the length of the host name. If it’s more than 15 characters long it is unresolvable to a Windows client — A Linux client can use another method. That is when you would use smb.conf to override the netbios name.
Re: Unable to restart SAMBA — ubuntu server 18.04
Code:

testparm -sv /dev/null | grep "netbios name"
returns the server’s name correctly — thanks.

Powered down the complete network and started again.

Voila! Some of the Windows 10 pcs work as expected and log onto the share correctly — others do not but will accept mapping of the share, another demands credentials but won’t accept them.

Windows, eh!

Many thanks to those who contributed to the thread, now marked as solved.

Bookmarks

Posting Permissions

Источник

root@BackUp:~# apt-get purge samba
Чтение списков пакетов… Готово
Построение дерева зависимостей
Чтение информации о состоянии… Готово
Пакет «samba» не установлен, поэтому не может быть удалён
обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 4 пакетов не обновлено.
root@BackUp:~# apt-get install samba
Чтение списков пакетов… Готово
Построение дерева зависимостей
Чтение информации о состоянии… Готово
Будут установлены следующие дополнительные пакеты:
attr python-dnspython samba-dsdb-modules samba-vfs-modules tdb-tools
Предлагаемые пакеты:
bind9 bind9utils ctdb ldb-tools ntp | chrony smbldap-tools winbind ufw
НОВЫЕ пакеты, которые будут установлены:
attr python-dnspython samba samba-dsdb-modules samba-vfs-modules tdb-tools
обновлено 0, установлено 6 новых пакетов, для удаления отмечено 0 пакетов, и 4 пакетов не обновлено.
Необходимо скачать 0 B/1 881 kB архивов.
После данной операции, объём занятого дискового пространства возрастёт на 14,6 MB.
Хотите продолжить? [Д/н] y
Выбор ранее не выбранного пакета python-dnspython.
(Чтение базы данных … на данный момент установлено 140943 файла и каталога.)
Подготовка к распаковке …/0-python-dnspython_1.15.0-1+deb9u1_all.deb …
Распаковывается python-dnspython (1.15.0-1+deb9u1) …
Выбор ранее не выбранного пакета tdb-tools.
Подготовка к распаковке …/1-tdb-tools_1.3.11-2_i386.deb …
Распаковывается tdb-tools (1.3.11-2) …
Выбор ранее не выбранного пакета samba.
Подготовка к распаковке …/2-samba_2%3a4.5.16+dfsg-1+deb9u1_i386.deb …
Распаковывается samba (2:4.5.16+dfsg-1+deb9u1) …
Выбор ранее не выбранного пакета attr.
Подготовка к распаковке …/3-attr_1%3a2.4.47-2+b2_i386.deb …
Распаковывается attr (1:2.4.47-2+b2) …
Выбор ранее не выбранного пакета samba-dsdb-modules.
Подготовка к распаковке …/4-samba-dsdb-modules_2%3a4.5.16+dfsg-1+deb9u1_i386.deb …
Распаковывается samba-dsdb-modules (2:4.5.16+dfsg-1+deb9u1) …
Выбор ранее не выбранного пакета samba-vfs-modules.
Подготовка к распаковке …/5-samba-vfs-modules_2%3a4.5.16+dfsg-1+deb9u1_i386.deb …
Распаковывается samba-vfs-modules (2:4.5.16+dfsg-1+deb9u1) …
Настраивается пакет python-dnspython (1.15.0-1+deb9u1) …
Настраивается пакет samba-vfs-modules (2:4.5.16+dfsg-1+deb9u1) …
Обрабатываются триггеры для libc-bin (2.24-11+deb9u4) …
Обрабатываются триггеры для systemd (232-25+deb9u11) …
Настраивается пакет tdb-tools (1.3.11-2) …
update-alternatives: используется /usr/bin/tdbbackup.tdbtools для предоставления /usr/bin/tdbbackup (tdbbackup) в автоматическом режиме
Обрабатываются триггеры для man-db (2.7.6.1-2) …
Настраивается пакет samba (2:4.5.16+dfsg-1+deb9u1) …
Samba is not being run as an AD Domain Controller, masking samba-ad-dc-service.
Please ignore the following error about deb-systemd-helper not finding samba-ad-dc-service.
Created symlink /etc/systemd/system/multi-user.target.wants/nmbd.service → /lib/systemd/system/nmbd.service.
Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory
Created symlink /etc/systemd/system/multi-user.target.wants/smbd.service → /lib/systemd/system/smbd.service.
Job for smbd.service failed because the control process exited with error code.
See «systemctl status smbd.service» and «journalctl -xe» for details.
invoke-rc.d: initscript smbd, action «start» failed.
● smbd.service — Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-04-11 13:36:19 MSK; 16ms ago
Docs: man:smbd(
man:samba(7)
man:smb.conf(5)
Process: 14407 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 14407 (code=exited, status=1/FAILURE)

апр 11 13:36:19 BackUp systemd[1]: Starting Samba SMB Daemon…
апр 11 13:36:19 BackUp systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
апр 11 13:36:19 BackUp systemd[1]: Failed to start Samba SMB Daemon.
апр 11 13:36:19 BackUp systemd[1]: smbd.service: Unit entered failed state.
апр 11 13:36:19 BackUp systemd[1]: smbd.service: Failed with result ‘exit-code’.
dpkg: ошибка при обработке пакета samba (—configure):
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Настраивается пакет samba-dsdb-modules (2:4.5.16+dfsg-1+deb9u1) …
Настраивается пакет attr (1:2.4.47-2+b2) …
Обрабатываются триггеры для libc-bin (2.24-11+deb9u4) …
Обрабатываются триггеры для systemd (232-25+deb9u11) …
При обработке следующих пакетов произошли ошибки:
samba
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@BackUp:~#

[свернуть]

Источник

Index
» Newbie Corner
» [SOLVED] smbd.service & nmbd.service fail to start

#1 2015-03-05 14:22:12

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)

#2 2015-03-05 14:26:18

cris9288: Member; Registered: 2013-01-07; Posts: 348

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

well…what does journalctl say?

#3 2015-03-05 14:33:21

mshan: Member; Registered: 2013-05-05; Posts: 105

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

well

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

#4 2015-03-05 14:43:13

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.

#5 2015-03-05 14:51:51

mshan: Member; Registered: 2013-05-05; Posts: 105

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

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.

#6 2015-03-05 15:08:36

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)

#7 2015-03-06 19:38:32

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)

#8 2015-04-13 15:01:10

Olegach21: Member; Registered: 2015-04-13; Posts: 1

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

ashbreeze wrote:

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.

#9 2015-09-12 23:49:01

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)

#10 2017-11-02 09:52:53

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.

#11 2017-11-02 09:57:49

V1del: Forum Moderator; Registered: 2012-10-16; Posts: 18,300

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.

Источник

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> xpforest

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> victor00000

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> xpforest

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> victor00000

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> wolfser2701

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> xpforest

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> victor00000

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> xpforest

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> wolfser2701

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> victor00000

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> xpforest

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> wolfser2701

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> xpforest

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> victor00000

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> xpforest

Unable to restart SAMBA — ubuntu server 18.04

Re: Unable to restart SAMBA — ubuntu server 18.04

Re: Unable to restart SAMBA — ubuntu server 18.04

Re: Unable to restart SAMBA — ubuntu server 18.04

Re: Unable to restart SAMBA — ubuntu server 18.04

Re: Unable to restart SAMBA — ubuntu server 18.04

Bookmarks

Bookmarks

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://ubuntuforums.org/images/ubuntu-VB4/buttons/collapse_40b.png" alt /> Posting Permissions

#1 2015-03-05 14:22:12

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

#2 2015-03-05 14:26:18

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

#3 2015-03-05 14:33:21

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

#4 2015-03-05 14:43:13

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

#5 2015-03-05 14:51:51

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

#6 2015-03-05 15:08:36

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

#7 2015-03-06 19:38:32

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

#8 2015-04-13 15:01:10

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

#9 2015-09-12 23:49:01

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

#10 2017-11-02 09:52:53

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

#11 2017-11-02 09:57:49

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

xpforest

victor00000

xpforest

victor00000

wolfser2701

xpforest

victor00000

xpforest

wolfser2701

victor00000

xpforest

wolfser2701

xpforest

victor00000

xpforest

Posting Permissions