Bug 33940

Summary:	(Re-)Join should remove s4internal.sqlite
Product:	UCS	Reporter:	Janis Meybohm <meybohm>
Component:	S4 Connector	Assignee:	Stefan Gohmann <gohmann>
Status:	CLOSED FIXED	QA Contact:	Arvid Requate <requate>
Severity:	normal
Priority:	P5	CC:	gohmann, jmm, markus.daehlmann, requate
Version:	UCS 3.2
Target Milestone:	UCS 3.2-0-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 Janis Meybohm

2014-01-16 18:08:39 CET

Ticket#2014011521001985

A customer reported that the s4-connector stopped synchronizing changes from S4 to LDAP (LDAP->S4 working fine) after rejoin of a (UCS@school) DC-Slave. It turned out that the lastUSN in s4internal.sqlite was a lot higher than the actual lastUSN in S4 so I guess the s4internal.sqlite is not removed during (re)-join.


Workaround:
invoke-rc.d univention-s4-connector stop
sqlite3 /etc/univention/connector/s4internal.sqlite 'update S4 set value=0;'
invoke-rc.d univention-s4-connector start

Comment 1 Stefan Gohmann

2014-01-24 09:40:53 CET

The database is now removed while re-joining: r47416

YAML: r47417

Comment 2 Arvid Requate

2014-01-28 16:00:15 CET

Verified (e.g. in UCS@school):

root@slave47:~# ls -l /etc/univention/connector/s4*
-rw-r--r-- 1 root root 79872 28. Jan 14:23 /etc/univention/connector/s4internal.sqlite
-rw-r--r-- 1 root root 93184 28. Jan 14:22 /etc/univention/connector/s4internal.sqlite_20140128142302

Advisory Ok.

Comment 3 Moritz Muehlenhoff

2014-02-06 13:37:39 CET

http://errata.univention.de/ucs/3.2/48.html