I'm chasing down an issue with multi-master replication on OpenLDAP 2.4.10 and I issue the following search to compare the contextCSN. Is there any reason to have 3 contextCSN attributes, and one of them looks like a base64 encoded string, that doesn't look right. Is this expected behavior?
-4- user@f8-workstation ~ >
ldapsearch -xZZH ldap://server01.example.com -D
"cn=manager,dc=openldap,dc=example,dc=com" -W -z 1 contextCSN dn: dc=openldap,dc=example,dc=com -LLL Enter LDAP Password: dn: dc=openldap,dc=example,dc=com contextCSN: 20080527205300.158966Z#000000#000#000000 contextCSN: 20080619202050.412763Z#000000#004#000000 contextCSN: 20080623172814.327835Z#000000#003#000000
Size limit exceeded (4)
-4- user@f8-workstation ~ >
ldapsearch -xZZH ldap://server03.example.com -D
"cn=manager,dc=openldap,dc=example,dc=com" -W -z 1 contextCSN dn: dc=openldap,dc=example,dc=com -LLL Enter LDAP Password: dn: dc=openldap,dc=example,dc=com contextCSN:: qBiaszA2MTIxNzMyMzMuMTA1MTA2WiMwMDAwMDAjMDAzIzAwMDAwMA== contextCSN: 20080620213035.498183Z#000000#004#000000 contextCSN: 20080527205300.158966Z#000000#000#000000
Size limit exceeded (4)
TIA,
On Wednesday 25 June 2008 19:07:14 Josh Miller wrote:
I'm chasing down an issue with multi-master replication on OpenLDAP 2.4.10 and I issue the following search to compare the contextCSN. Is there any reason to have 3 contextCSN attributes,
Yes, one per master.
and one of them looks like a base64 encoded string, that doesn't look right. Is this expected behavior?
-4- user@f8-workstation ~ >
ldapsearch -xZZH ldap://server01.example.com -D
ldapsearch -xZZH ldap://server01.example.com -D -s base contextCSN
would just pull what you need ...
"cn=manager,dc=openldap,dc=example,dc=com" -W -z 1 contextCSN dn: dc=openldap,dc=example,dc=com -LLL Enter LDAP Password: dn: dc=openldap,dc=example,dc=com contextCSN: 20080527205300.158966Z#000000#000#000000 contextCSN: 20080619202050.412763Z#000000#004#000000 contextCSN: 20080623172814.327835Z#000000#003#000000
Size limit exceeded (4)
-4- user@f8-workstation ~ >
ldapsearch -xZZH ldap://server03.example.com -D
"cn=manager,dc=openldap,dc=example,dc=com" -W -z 1 contextCSN dn: dc=openldap,dc=example,dc=com -LLL Enter LDAP Password: dn: dc=openldap,dc=example,dc=com contextCSN:: qBiaszA2MTIxNzMyMzMuMTA1MTA2WiMwMDAwMDAjMDAzIzAwMDAwMA== contextCSN: 20080620213035.498183Z#000000#004#000000 contextCSN: 20080527205300.158966Z#000000#000#000000
Size limit exceeded (4)
Yes, seems that contextCSN is corrupt: $ echo "qBiaszA2MTIxNzMyMzMuMTA1MTA2WiMwMDAwMDAjMDAzIzAwMDAwMA=="|openssl base64 -d �▒��0612173233.105106Z#000000#003#000000
BTW, here are some of mine from my "personal" setup:
$ ldapsearch -LLL -x -s base contextCSN dn: dc=ranger,dc=dnsalias,dc=com contextCSN: 20080604145433.000000Z#000000#000#000000 contextCSN: 20080619112342.214243Z#000000#001#000000 contextCSN: 20080610060640.243411Z#000000#002#000000
$ ldapsearch -LLL -x -H ldap://seaknight:390/ -s base contextCSN dn: dc=ranger,dc=dnsalias,dc=com contextCSN: 20080604145433.000000Z#000000#000#000000 contextCSN: 20080619112342.214243Z#000000#001#000000
(this server can't reach the other master .... I still wonder if this can cause problems)
Regards, Buchan
openldap-technical@openldap.org
-
Buchan Milne -
Josh Miller