Bug 40389 - Running Samba 4 and S4 Connector during rejoin on a school slave
Running Samba 4 and S4 Connector during rejoin on a school slave
Product: UCS
Classification: Unclassified
Component: Join (univention-join)
UCS 4.0
Other Linux
: P5 normal (vote)
: UCS 4.0-4-errata
Assigned To: Arvid Requate
Felix Botner
Depends on:
Blocks: 40391
  Show dependency treegraph
Reported: 2016-01-08 07:01 CET by Stefan Gohmann
Modified: 2016-01-20 13:44 CET (History)
1 user (show)

See Also:
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:


Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2016-01-08 07:01:23 CET
During the rejoin of a school slave, I've seen that the S4 connector still synchronized while the listener has been initialized. I guess that could led to problems but at least it costs a lot of performance. The Samba 4 server was running as well.

univention-join should stop theses services.

I've seen that at least Samba4 is stopped at the beginning of the join but it has been started in 62ucs-school-slave.inst. I'll create a new bug for it.

Ticket #2015121821000547
Comment 1 Arvid Requate univentionstaff 2016-01-12 14:02:08 CET
Fixed in errata4.0-4.

Advisory: univention-join.yaml
Comment 2 Felix Botner univentionstaff 2016-01-13 11:17:44 CET
OK - univention-join, s4-connector and samba are stopped in univention-join and not restarted until 96univention-samba4.inst resp. 97univention-s4-connector.inst

OK - yaml
Comment 3 Janek Walkenhorst univentionstaff 2016-01-20 13:44:14 CET