Bug 40773 - Remove lockingdb.sqlite while-rejoining
Remove lockingdb.sqlite while-rejoining
Product: UCS
Classification: Unclassified
Component: S4 Connector
UCS 4.2
Other Linux
: P5 normal (vote)
: UCS 4.4-0-errata
Assigned To: Samba maintainers
Felix Botner
Depends on:
  Show dependency treegraph
Reported: 2016-02-25 10:40 CET by Stefan Gohmann
Modified: 2019-06-19 15:52 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.069
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number: 2016022221000271
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-02-25 10:40:41 CET
The lockingdb.sqlite should be removed while re-joining.

It is already implemented for the s4internal.sqlite file:

if [ $JS_LAST_EXECUTED_VERSION -le 0 ]; then
    # Remove existing sqlite DB while re-joining
    test -e "$internal_db" && mv "$internal_db" "${internal_db}_$(date +%Y%m%d%H%M%S)"
Comment 1 Stefan Gohmann univentionstaff 2016-02-25 10:41:30 CET
Happened here: Ticket #2016022221000271
Comment 2 Arvid Requate univentionstaff 2019-06-13 12:02:39 CEST
a0c6ab518f | Remove lockingdb and s4cache during re-join
84dd749a79 | Advisory
Comment 3 Felix Botner univentionstaff 2019-06-13 13:39:56 CEST
Comment 4 Arvid Requate univentionstaff 2019-06-19 15:52:40 CEST