Hello Venkatesh,
There's been no follow up since 2012, so I will be closing this ITS. I
assume the issue was resolved by downgrading BDB. If you still encounter
this issue with the current OpenLDAP release, feel free to follow up and I
will reopen the ITS.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Full_Name: Alan Griffiths
Version: 2.4.44
OS: Centos 7.3
URL: https://pastebin.com/CaVGpfKj
Submission from: (NULL) (86.22.17.96)
Adding multiple entries to olcDbURI causes slapd to crash when the ref is first
followed with: -
8ef6698 conn=1002 op=1 ldap_chain_op:
ref="ldap://aws-mldap-01.aws/uid=test1,ou=people,dc=abu,dc=inmarsat,dc=com" ->
"ldap://aws-mldap-01.aws"
slapd: chain.c:227: ldap_chain_uri_cmp: Assertion `((&li2->li_bvuri[ 1
])->bv_val == ((void *)0))' failed.
Aborted
This appears to be the same issue as reported here
http://www.openldap.org/lists/openldap-technical/201409/msg00056.html
but in a more recent version. I can re-create in 2.4.40 and 2.4.44.
Link to full debug output is provided.
Full_Name: James Turner
Version: 2.4.42
OS: Ubuntu 16.04 LTS
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (81.86.27.193)
The schema definition for 'deltaCRL' includes:
DESC 'RFC2587: PKI user'
This class does not represent a user - the text may have been copied/pasted from
pkiUser (which appears a few definitions above it in the same files).
A more appropriate definition would be something like:
DESC 'RFC2587: delta CRL'
Affected files:
servers/slapd/schema/core.ldif
servers/slapd/schema/core.schema
Hi Michael,
I'm going to assume this issue was fixed in 2.4.29 with the fix for
ITS#7113. If that's not the case, please follow up. I will close this ITS
in the meantime.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Hi Jarl,
Apologies for the delay in response. Do you still experience this issue in
curent OpenLDAP releases? Numerous fixes have been made to MMR since your
report was originally filed. I will close the ITS for now, but if you
still are encountering this issue, feel free to follow up so it can be
correcty triaged this time.
Thanks,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--On Monday, April 10, 2017 9:36 AM +0000 daniel(a)pluta.biz wrote:
> Although I know that I'm highly probable not directly addressed by the
> question "For 2.5?" (see this its's notes), my answer/comment would be
> "Yes", even "Yes, of course.":
Hi Daniel,
It's just a note to myself to discuss with Howard for possible inclusion in
2.5. ;) I'm going through all the incoming ITSes and sorting them out and
setting priority, etc, as that's been neglected for a while.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Hello,
Sorry for the delay in response. I believe this issue has been resolved
since the 2.4.25 release. If you can reproduce this issue with the current
OpenLDAP release, please follow up.
Thanks,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Full_Name: Quanah Gibson-Mount
Version: 2.4.44
OS: N/A
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (47.208.148.239)
The man page for serverID says:
serverID <integer> [<URL>]
Specify an integer ID from 0 to 4095 for this server (limited to 3
hexadecimal digits). The ID may also be
specified as a hexadecimal ID by prefixing the value with
"0x". These IDs are required when using multimaster
replication and each master must have a unique ID. Note that this
requirement also applies to separate masters
contributing to a glued set of databases. If the URL is provided,
this directive may be specified multiple times,
providing a complete list of participating servers and their IDs.
The fully qualified hostname of each server
should be used in the supplied URLs. The IDs are used in the
"replica id" field of all CSNs generated by the
specified server. The default value is zero. Example:
serverID 1
However, it does not specifically note that serverID 0 is reserved for single
master only, and that in MMR & Mirror mode configurations, serverIDs must be 1
and higher.
The admin guide likely needs similar updating.