Mageia forum

After my update of mga6 today samba does not start any more:

Code: Select all

# 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 Mo 2019-01-14 11:58:23 CET; 8min ago
  Process: 17227 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)
 Main PID: 17227 (code=exited, status=1/FAILURE)

Jan 14 11:58:23 ***.***.de systemd[1]: Starting Samba SMB Daemon...
Jan 14 11:58:23 ***.***.de systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
Jan 14 11:58:23 ***.***.de systemd[1]: Failed to start Samba SMB Daemon.
Jan 14 11:58:23 ***.***.de systemd[1]: smb.service: Unit entered failed state.
Jan 14 11:58:23 ***.***.de systemd[1]: smb.service: Failed with result 'exit-code'.
#

The output of journalctl -xe does not help me:

Code: Select all

Jan 14 12:08:15 ***.***.de 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.
Jan 14 12:08:15 ***.***.de systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
Jan 14 12:08:15 ***.***.de 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.
Jan 14 12:08:15 ***.***.de systemd[1]: smb.service: Unit entered failed state.
Jan 14 12:08:15 ***.***.de systemd[1]: smb.service: Failed with result 'exit-code'.
lines 965-1013/1013 (END)

I already re-installed samba server but this did not solve the problem. Any idea what I could try?

Did you check whether there were any smbd / nmbd processes actually still running at that time?
Did you check whether any of the ports used by samba are maybe already in use? Did you recheck your samba configuration via testparm -s ?
Also, what happens if you directly start smbd in debug mode, logging to stdout ?

Thank you for your hint. It turned out that one line in smb.cnf which was accepted previously (samba 4.6.5) is not accepted by samba 4.7.12 any more:

Code: Select all

name resolve order = hosts bcast

The solution was to comment out that line.