[SOLVED] samba does not start after mga6 update

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

[SOLVED] samba does not start after mga6 update

Postby magfan » Jan 14th, '19, 13:19

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?
Last edited by magfan on Jan 16th, '19, 10:28, edited 1 time in total.
magfan
 
Posts: 274
Joined: Apr 3rd, '12, 12:33

Re: samba does not start after mga6 update

Postby doktor5000 » Jan 15th, '19, 19:03

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 ?
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 14573
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: samba does not start after mga6 update

Postby magfan » Jan 16th, '19, 10:27

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.
magfan
 
Posts: 274
Joined: Apr 3rd, '12, 12:33


Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest