Description of problem: samba does not start Version-Release number of selected component (if applicable): samba-4.3.0-3.mga6 How reproducible: always Steps to Reproduce: # systemctl start smb Job for smb.service failed because the control process exited with error code. See "systemctl status smb.service" and "journalctl -xe" for details. # systemctl status smb.service â smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2015-10-03 22:50:21 CEST; 7s ago Process: 10867 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=1/FAILURE) Main PID: 10867 (code=exited, status=1/FAILURE) [...] Oct 03 22:50:20 localhost.localdomain systemd[1]: Starting Samba SMB Daemon... Oct 03 22:50:21 localhost.localdomain systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE Oct 03 22:50:21 localhost.localdomain systemd[1]: Failed to start Samba SMB Daemon. Oct 03 22:50:21 localhost.localdomain systemd[1]: smb.service: Unit entered failed state. Oct 03 22:50:21 localhost.localdomain systemd[1]: smb.service: Failed with result 'exit-code'. journalctl -xe gives this: [...] Oct 03 22:57:47 localhost.localdomain polkitd[411]: Registered Authentication Agent for unix-process:25625:129379349 (system bus name :1.240 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freed Oct 03 22:57:47 localhost.localdomain systemd[1]: Starting Samba SMB Daemon... -- Subject: Unit smb.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit smb.service has begun starting up. Oct 03 22:57:47 localhost.localdomain systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE Oct 03 22:57:47 localhost.localdomain kernel: audit: type=1130 audit(1443905867.785:2566): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=smb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? Oct 03 22:57:47 localhost.localdomain polkitd[411]: Unregistered Authentication Agent for unix-process:25625:129379349 (system bus name :1.240, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale Oct 03 22:57:47 localhost.localdomain systemd[1]: Failed to start Samba SMB Daemon. -- Subject: Unit smb.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit smb.service has failed. -- -- The result is failed. Oct 03 22:57:47 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=smb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Oct 03 22:57:47 localhost.localdomain systemd[1]: smb.service: Unit entered failed state. Oct 03 22:57:47 localhost.localdomain systemd[1]: smb.service: Failed with result 'exit-code'. Reproducible: Steps to Reproduce:
The culprit was an old smb.conf Using /etc/samba/smb.conf.rpmnew samba starts for me. It would be nice if some message would give a hint to consult /var/log/samba/log.smbd Anyway feel free to close the bug.
(In reply to Helge Hielscher from comment #1) > The culprit was an old smb.conf > > It would be nice if some message would give a hint to consult > /var/log/samba/log.smbd You would have to report that upstream, as we only package samba. As a hint, most people that use samba always first run "testparm" to check the validity of their current smb.conf ;) Closing.
Status: NEW => RESOLVEDCC: (none) => doktor5000Resolution: (none) => INVALID