--On Monday, August 31, 2020 4:51 PM +0200 Frédéric Goudal <[email protected]> wrote:
Hello, I have an ldap master that from some reason has multiple CSN : contextCSN: 20130927152219.157851Z#000000#001#000000 contextCSN: 20131127140429.597497Z#000000#002#000000 contextCSN: 20141208130549.278599Z#000000#004#000000 contextCSN: 20200831094837.531411Z#000000#00a#000000 Some are quite old. I don't know why they are here. Is there a way to clean the old Context CSN ?
This would indicate that at some point in time, you had providers with serverIDs of 1, 2, and 4 and those were the last time they received an update. Do you currently only have a single provider?
If so, you have to manually clean up the old contextCSNs by exporting the database, using sed or similar to replace all #001#, #002#, and #004# in the database entryCSN fields with #00a#, delete the existing contextCSN values for other than #00a#, and then reload the DB on all servers.
It's been on my to-do to file an ITS that allows one to forcefully reset all serverIDs with slapadd to a single serverID, so I should probably go file that. ;)
Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>
