Bug 44466
| Summary: | BDB-Listener cache on DC Backup not converted to mdb | ||
|---|---|---|---|
| Product: | UCS | Reporter: | Arvid Requate <requate> |
| Component: | Listener (univention-directory-listener) | Assignee: | Arvid Requate <requate> |
| Status: | CLOSED FIXED | QA Contact: | Felix Botner <botner> |
| Severity: | critical | ||
| Priority: | P5 | CC: | gohmann, hahn |
| Version: | UCS 4.2 | ||
| Target Milestone: | UCS 4.2-0-errata | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| 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?: | 4: Will affect most installed domains | How will those affected feel about the bug?: | 5: Blocking further progress on the daily work |
| User Pain: | 0.343 | Enterprise Customer affected?: | |
| School Customer affected?: | ISV affected?: | ||
| Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
| Ticket number: | Bug group (optional): | Troubleshooting | |
| Max CVSS v3 score: | |||
| Bug Depends on: | 23367 | ||
| Bug Blocks: | |||
|
Description
Arvid Requate
I've added another conversion section to the postinst. Advisory: univention-directory-listener.yaml UCS 4.1-4 master + backup (with s4 con) + slave + member => update to 4.2-0 I could reproduce this on my backup, slave and member (master was ok). After the update /var/lib/univention-directory-listener/cache.db still existed and the listener cache was rather empty. -> univention-directory-listener-dump | grep dn:| wc -l 17 Replication (and s4 con) worked at this point, now objects where added to the listener cache. Then i updated the univention-directory-listener package (errata4.2-0) master: OK cache convert omitted backup: OK ... [....] Stopping univention-directory-listener (via systemctl): univention-directory-listener.service^[[?25l^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?12l^[[?25h.^M 25.04.17 17:34:42.654 DEBUG_INIT^M Converting listener cache to LMDB^M cached notifier_id: 1270^M cached schema_id: 11^M ... Cache has been converted successfully, listener id has been decreased to the id from before the update, but no sign of hickups (s4 connector got an extra add for objects created after the update, but also no problems here). Replication (s4 con) still works. slave: OK ... 26.04.17 00:36:38.768 DEBUG_INIT Converting listener cache to LMDB cached notifier_id: 1270 cached schema_id: 11 ... member: OK ... 26.04.17 00:42:44.222 DEBUG_INIT Converting listener cache to LMDB cached notifier_id: 1270 cached schema_id: 11 ... OK - On all system the cache has been converted, cache.db has been removed and the number of cache entries was bigger then before the update (which is OK, because i created objects after the upate) OK - YAML |