You are not logged in.
EDIT: Fixed it. Had to chmod 755 /var/cache/samba/msg, enable and start nmbd (this was not necessary before?), then samba started without errors.
Hi,
after upgrading samba to 4.3.0-1 and doing a systemctl daemon-reload, samba fails starting. My server is running as a standalone file server, I'm not using any active directory features (config at the end of post). Here's the output:
[2015/09/09 12:17:19.870069, 0] ../source4/smbd/server.c:372(binary_smbd_main)
samba version 4.3.0 started.
Copyright Andrew Tridgell and the Samba Team 1992-2015
[2015/09/09 12:17:20.012219, 0] ../source4/smbd/server.c:477(binary_smbd_main)
At this time the 'samba' binary should only be used for either:
'server role = active directory domain controller' or to access the ntvfs file server with 'server services = +smb' or the rpc proxy with 'dcerpc endpoint servers = remote'
You should start smbd/nmbd/winbindd instead for domain member and standalone file server tasks
[2015/09/09 12:17:20.012383, 0] ../lib/util/become_daemon.c:111(exit_daemon)
STATUS=daemon failed to start: Samba detected misconfigured 'server role' and exited. Check logs for details, error code 22
I tried to do so, enabled and started winbindd, which also failed:
Sep 09 12:31:30 green-lagune systemd[1]: winbindd.service: Control process exited, code=dumped status=6
Sep 09 12:31:30 green-lagune systemd[1]: Failed to start Samba Winbind daemon.
-- Subject: Unit winbindd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit winbindd.service has failed.
--
-- The result is failed.
Sep 09 12:31:30 green-lagune systemd[1]: winbindd.service: Unit entered failed state.
Sep 09 12:31:30 green-lagune polkitd[788]: Unregistered Authentication Agent for unix-process:25110:14055636 (system bus name :1.90, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Sep 09 12:31:30 green-lagune systemd[1]: winbindd.service: Failed with result 'core-dump'.
Sep 09 12:31:30 green-lagune systemd-coredump[25116]: Process 25115 (winbindd) of user 0 dumped core.
-- Subject: Process 25115 (winbindd) dumped core
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
--
-- Process 25115 (winbindd) crashed and dumped core.
--
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
And finally, here's my smb.conf:
[global]
workgroup = WORKGROUP
server string = My SMB Server
hosts allow = 192.168.77. 127.
log file = /var/log/samba/%m.log
max log size = 50
security = user
invalid users = root
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
dns proxy = no
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes
[myfiles]
path = /srv/myfiles
comment = myfiles
browseable = yes
writable = yes
valid users = user1,user2,user3
nt acl support = yes
Last edited by vibee (2015-09-09 12:12:01)
Offline
Good one Vibee. No head scratching for me now.
Offline
Thank you, Vibee !
I could solve same problem. In my case, I did chmod 755 /var/cache/samba/msg, and start smbd.service instead of samba.service.
That works fine for me.
Offline
In my case it was even simplier: already tryed it on Arch Linux x64 setup and Arch Linux ARM setup.
1) To your "smb.conf" add
server services = +smb
2) Check that this path has 0755 permissions
/var/cache/samba/msg
Once done, reload your nmbd and/or smbd service as always using systemctl
The purposed edit was tested starting from "smb.conf.default" file template.
Last edited by julianxhokaxhiu (2015-09-09 19:37:00)
Offline
Thank you all. Once I'd stopped reading 755 as 775, it fixed my issue, too.
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
Really good. thanks
Offline
Had the same issue. Fixing the permissions for /var/cache/samba/msg fixed smbd start.
Offline
Thank you, Vibee !
I could solve same problem. In my case, I did chmod 755 /var/cache/samba/msg, and start smbd.service instead of samba.service.
That works fine for me.
Thanks!
That solve my problem too
Offline
Thanks, helped me to.
Offline
Have you tried to reboot?
After changing permissions of '/var/cache/samba/msg' if I reboot 'nmbd.service' starts, but 'smbd.service' still fails...
Manually starting 'smbd.service' after boot works again!
This is the only working solution for me:
1) To your "smb.conf" add
server services = +smb
Waiting for a real fix.
"Greetings from the Banana Republic"
Offline
I've tried to edits here but I am still not getting samba working. When I look in /var/cache/samba I don't have msg there but it lets me set the permissions
I've also added:
server services = +smb
But it doesn't seemed to have worked unless it needs to go in a particular spot. If so where should it go?
Offline
Put it in the 'global settings' section, not in the 'share definitions'.
"Greetings from the Banana Republic"
Offline
I experienced the same problem, none of the above fixed anything, what actually solved it was:
sudo rm -rf /var/cache/samba/*
than I restarted the smbd service and everything went fine.
Offline
Out of interest, what are the permissions on the "msg" directory *before* applying the fix?
Offline
Offline