On Wed, May 24, 2017 at 10:21 AM, John Winward <j...@mrpsystems.co.uk> wrote:
> Morning > > > > I have just installed a CentOS 7 system and I hace install many CentOS > platgforms over the years > > > > However, I cannot seem to get SAMBA running and have nenver had issues > with this before? > > > > [root@d3server ~]£ systemctl start smb > > > Job for smb.service failed because the control process exited with error > code. S > > ee "systemctl status smb.service" and "journalctl -xe" for > details. > > [root@d3server ~]£ > > > > > > > [root@d3server ~]£ systemctl status smb.service > > > ùÅ smb.service - Samba SMB Daemon > > > Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor > preset: > > disabled) > > > Active: failed (Result: exit-code) since Wed 2017-05-24 08:17:15 BST; > 29s ago > > > > > Process: 3731 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, > status=1/FAI > > LURE) > > > Main PID: 3731 (code=exited, status=1/FAILURE) > > > > > > May 24 08:17:15 d3server.scolaquip.co.uk systemd[1]: Starting Samba SMB > Daemo... > > > > > May 24 08:17:15 d3server.scolaquip.co.uk systemd[1]: smb.service: main > proces... > > > > > May 24 08:17:15 d3server.scolaquip.co.uk systemd[1]: Failed to start > Samba SM... > > > > > May 24 08:17:15 d3server.scolaquip.co.uk systemd[1]: Unit smb.service > entered... > > > > > May 24 08:17:15 d3server.scolaquip.co.uk systemd[1]: smb.service > failed. > > Hint: Some lines were ellipsized, use -l to show in > full. > > [root@d3server ~]£ > > It doesn't look like a systemd issue either way (although next time I'd suggest providing the full, non-ellipsized output). Please check /var/log/samba, verify your Samba configuration using `testparm`, and/or contact Samba technical support. -- Mantas Mikulėnas <graw...@gmail.com>
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel