You are not logged in.
Pages: 1
Since updating linux (4.12.13-1 -> 4.13.3-1) and samba (4.6.7-1 -> 4.7.0-1) via Pacman -Syu Samba fails to start. I have made no configuration changes other than to change directory permissions to match package settings. Samba logs in /var/log/samba are empty. Journalctl -xe provides no information that is useful to me. Google and forum searches have failed me for the first time since I started using Arch.
Here is what systemd's log has to say about it:
Oct 01 05:40:11 Machine systemd[1]: Starting Samba AD Daemon...
-- Subject: Unit samba.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit samba.service has begun starting up.
Oct 01 05:40:11 Machine samba[1166]: handle_name_resolve_order: WARNING: Ignoring invalid list value 'hosts' for parameter 'name resolve
Oct 01 05:40:11 Machine systemd[1]: Started Samba AD Daemon.
-- Subject: Unit samba.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit samba.service has finished starting up.
--
-- The start-up result is done.
Oct 01 05:40:11 Machine sudo[1163]: pam_unix(sudo:session): session closed for user root
Oct 01 05:40:11 Machine systemd[1]: samba.service: Main process exited, code=exited, status=1/FAILURE
Oct 01 05:40:11 Machine systemd[1]: samba.service: Unit entered failed state.
Oct 01 05:40:11 Machine systemd[1]: samba.service: Failed with result 'exit-code'.
Oct 01 05:40:19 Machine sudo[1168]: robert : TTY=pts/1 ; PWD=/home/robert ; USER=root ; COMMAND=/usr/bin/systemctl start nmbd
Oct 01 05:40:19 Machine sudo[1168]: pam_unix(sudo:session): session opened for user root by robert(uid=0)
Oct 01 05:40:19 Machine systemd[1]: Starting Samba NetBIOS name server...
-- Subject: Unit nmbd.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nmbd.service has begun starting up.
Oct 01 05:40:19 Machine systemd[1]: nmbd.service: Control process exited, code=exited status=1
Oct 01 05:40:19 Machine systemd[1]: Failed to start Samba NetBIOS name server.
-- Subject: Unit nmbd.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nmbd.service has failed.
--
-- The result is failed.
Oct 01 05:40:19 Machine systemd[1]: nmbd.service: Unit entered failed state.
Oct 01 05:40:19 Machine systemd[1]: nmbd.service: Failed with result 'exit-code'.
Oct 01 05:40:19 Machine sudo[1168]: pam_unix(sudo:session): session closed for user root
Oct 01 05:40:25 Machine sudo[1172]: robert : TTY=pts/1 ; PWD=/home/robert ; USER=root ; COMMAND=/usr/bin/systemctl start smbd
Oct 01 05:40:25 Machine sudo[1172]: pam_unix(sudo:session): session opened for user root by robert(uid=0)
Oct 01 05:40:25 Machine systemd[1]: Starting Samba SMB/CIFS server...
-- Subject: Unit smbd.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit smbd.service has begun starting up.
Oct 01 05:40:25 Machine systemd[1]: smbd.service: Control process exited, code=exited status=1
Oct 01 05:40:25 Machine systemd[1]: Failed to start Samba SMB/CIFS server.
-- Subject: Unit smbd.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit smbd.service has failed.
--
-- The result is failed.
Oct 01 05:40:25 Machine systemd[1]: smbd.service: Unit entered failed state.
Oct 01 05:40:25 Machine systemd[1]: smbd.service: Failed with result 'exit-code'.
Oct 01 05:40:25 Machine sudo[1172]: pam_unix(sudo:session): session closed for user root
Oct 01 05:40:30 Machine sudo[1176]: robert : TTY=pts/1 ; PWD=/home/robert ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Oct 01 05:40:30 Machine sudo[1176]: pam_unix(sudo:session): session opened for user root by robert(uid=0)Here is my smb.conf minus shares:
#======================= Global Settings =====================================
[global]
workgroup = Workgroup
netbios name = Machine
server string = Machine
server string = %h
# server services = +smb
server services =
security = user
disable netbios = yes
name resolve order = hosts lmhosts bcast
load printers = no
disable spoolss = yes
log file = /var/log/samba/%m.log
log level = 3
max log size = 100
interfaces = 192.168.0.11/255.255.255.0 1 127.0.0.1/8
hosts allow = 192.168.0.0/255.255.255.0 127.0.0.1 localhost
hosts deny = all
bind interfaces only = yes
remote announce = 192.168.0.255
remote browse sync = 192.168.0.255
strict sync = no
sync always = no
deadtime = 60
dns proxy = no
wins support = no
wins proxy = no
create mask = 0755
directory mask = 0775
create mask = 0755
directory mask = 0775Can anyone point me in the right direction for a solution?
Last edited by fuankn (2017-10-01 13:48:53)
Offline
hello, in my case the error was in the smb.conf "name resolve order = hosts lmhosts bcast", the hosts with "s" is no valid, remove the "s" from "hosts" or comment the line.
Samba is working wrong for me too, it refuse to mount a folder that was working fine two days ago....
Offline
Thank you. Removing that 's' solved the problem. That warning has been showing up in the logs as far back as I can remember and I just ignored it because everything worked fine until now.
I can't mount folders either though. Adding vers=2.1 (or 3.0) and/or sec=ntlmssp to the mount command did not help here.
Thanks again.
Offline
Pages: 1