Bug 13184 - systemd should start samba and nmbd only when network is fully set up
Summary: systemd should start samba and nmbd only when network is fully set up
Status: RESOLVED FIXED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Other (show other bugs)
Version: 4.7.0
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Andreas Schneider
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-12 07:30 UTC by Andreas Schneider
Modified: 2020-04-10 16:23 UTC (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Schneider 2017-12-12 07:30:34 UTC 
sytsemd starts the samba service to early so the MIT KDC can't find any interfaces and fails to start.

We need to wait till the network is up.
Comment 1 Andreas Schneider 2017-12-12 12:30:52 UTC 
--- a/packaging/systemd/samba.service
+++ b/packaging/systemd/samba.service
@@ -1,6 +1,7 @@
 [Unit]
 Description=Samba AD Daemon
-After=syslog.target network.target
+Wants=network-online.target
+After=syslog.target network.target network-online.target
 
 [Service]
 Type=notify
Comment 2 Alexander Bokovoy 2018-10-05 13:02:12 UTC 
The issue is fixed in both 4.8 and 4.9 branches which are the current ones supported by Samba Team. 4.7 is for security fixes only.

Thus, I'm closing this bug.
Comment 3 Mikhail Novosyolov 2020-04-10 16:23:38 UTC 
There is another problem related to start up: bug#13111