Univention Bugzilla – Full Text Bug Listing |
Summary: | Samba AD DC provision failed due to winbind(3) installed and running. | ||
---|---|---|---|
Product: | UCS | Reporter: | Arvid Requate <requate> |
Component: | Samba4 | Assignee: | Erik Damrose <damrose> |
Status: | CLOSED FIXED | QA Contact: | Arvid Requate <requate> |
Severity: | normal | ||
Priority: | P5 | CC: | damrose, gohmann, schwardt, walkenhorst |
Version: | UCS 3.2 | ||
Target Milestone: | UCS 3.2-3-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
What kind of report is it?: | --- | What type of bug is this?: | --- |
Who will be affected by this bug?: | --- | How will those affected feel about the bug?: | --- |
User Pain: | Enterprise Customer affected?: | ||
School Customer affected?: | ISV affected?: | ||
Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
Ticket number: | Bug group (optional): | ||
Max CVSS v3 score: |
Description
Arvid Requate
2014-08-12 12:25:23 CEST
This is how it sould be: root@ucsmaster:~# samba-tool processes | grep winbind winbind_server 15706 It just happened again. After executing $ killall winbindd the provisioning continued and the join finished successfully. Everything seemed to work fine in a quick test (kinit, univention-s4sesarch, smbclient -k \\fqdn\sysvol) This now occured 3 times today, always with appliance mode, so we might want to fix this before releasing the new appliance images. Just saying. User experience. The winbind initscript does not stop winbind. The fix adjusts the joinscript to really stop all winbind processes. The fix for UCS 4 will adjust the winbind initscript. r52686 univention-samba4 3.0.39-33.586.201408131223 r52687 staging/2014-08-12-univention-samba4.yaml I think it would be better to use start-stop-daemon like it's done in the winbind init script. pkill doesn't ensure that the process is really gone. start-stop-daemon --stop --quiet --retry 2 --exec /usr/sbin/winbindd Use start-stop-daemon instead of pkill r52700 univention-samba4 3.0.39-34.587.201408131600 r52701 yaml Verified and advisory is Ok. |