David C. Rankin
2014-Jan-11 00:40 UTC
[Samba] systemd - error on start: You should start smbd/nmbd/winbindd for domain member & standalone
All, Looking at logs for 4.1.3 on my standalone server (Archlinux w/systemd), I get an error launching samba with 'systemctl start samba.service' telling me I should start all individual daemons instead (nmbd/smbd/winbindd) of using samba.service: Jan 07 22:25:07 phoinix systemd[1]: Starting Samba AD Daemon... Jan 07 22:25:07 phoinix samba[29948]: [2014/01/07 22:25:07.734014, 0] ../source4/smbd/server.c:370(binary_smbd_main) Jan 07 22:25:07 phoinix samba[29948]: samba version 4.1.3 started. Jan 07 22:25:07 phoinix samba[29948]: Copyright Andrew Tridgell and the Samba Team 1992-2013 Jan 07 22:25:07 phoinix systemd[1]: Started Samba AD Daemon. Jan 07 22:25:07 phoinix samba[29950]: [2014/01/07 22:25:07.784527, 0] ../source4/smbd/server.c:478(binary_smbd_main) Jan 07 22:25:07 phoinix samba[29950]: At this time the 'samba' binary should only be used for either: Jan 07 22:25:07 phoinix samba[29950]: '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' Jan 07 22:25:07 phoinix samba[29950]: You should start smbd/nmbd/winbindd instead for domain member and standalone file server tasks Jan 07 22:25:07 phoinix systemd[1]: samba.service: main process exited, code=exited, status=1/FAILURE Jan 07 22:25:07 phoinix systemd[1]: Unit samba.service entered failed state. Why should this make any difference? If it does, what difference does it make? I have a small office with less that 12 client machines and don't care about single-sign-on. So I have always run samba by starting 'samba' if the distro provided a 'samba' init, or by just starting the daemons individually. I don't mind doing it either way, but I do mind not understanding why systemd should care. So what is the correct way to start samba here and why isn't systemd smart enough to know how to properly start samba with samba.service in a standalone/workgroup setting? -- David C. Rankin, J.D.,P.E.
Possibly Parallel Threads
- Standalone Update 4.8.5 -> 4.9.2 smb fails to start ERROR: failed to setup guest info.
- What in samba 4.1 prevents a '/' share?
- upgrade 4.4 -> 4.5 broke standalone server smbmount of drives?
- kernel update to 3.12.5-1, now: upsd[617]: getaddrinfo: Servname not supported for ai_socktype
- Nut (git) upsdrvctl fails without "-u root start <upsname>", upsd fails on state file GID