--Apple-Mail=_F8BCAB64-A19B-4B00-B41B-03BE06C12A1F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
> On 6. Aug 2019, at 13:43, Victor Porof <vporof(a)mozilla.com> wrote:
>=20
> Here's everything we know about: =
https://crash-stats.mozilla.org/report/index/5d77bd19-41ce-459f-9c1c-7f9fb=
0190324 See the "details" and "telemetry environment" sections for a =
breakdown.
Since that link is now expired, here=E2=80=99s an up to date place to =
see all recent crash reports involving `mdb_cursor_put`: =
https://crash-stats.mozilla.org/signature/?signature=3Dmdb_cursor_put#repo=
rts =
<https://crash-stats.mozilla.org/signature/?signature=3Dmdb_cursor_put#rep=
orts>=20
Victor=
--Apple-Mail=_F8BCAB64-A19B-4B00-B41B-03BE06C12A1F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
6. Aug 2019, at 13:43, Victor Porof <<a =
href=3D"mailto:vporof@mozilla.com" class=3D"">vporof(a)mozilla.com</a>> =
wrote:</div><div class=3D""><div class=3D""><br class=3D"">Here's =
everything we know about: <a =
href=3D"https://crash-stats.mozilla.org/report/index/5d77bd19-41ce-459f-9c=
1c-7f9fb0190324" =
class=3D"">https://crash-stats.mozilla.org/report/index/5d77bd19-41ce-459f=
-9c1c-7f9fb0190324</a> See the "details" and "telemetry environment" =
sections for a breakdown.<br class=3D""></div></div></blockquote><div><br =
class=3D""></div>Since that link is now expired, here=E2=80=99s an up to =
date place to see all recent crash reports involving =
`mdb_cursor_put`: <a =
href=3D"https://crash-stats.mozilla.org/signature/?signature=3Dmdb_cursor_=
put#reports" =
class=3D"">https://crash-stats.mozilla.org/signature/?signature=3Dmdb_curs=
or_put#reports</a> <div class=3D""><br class=3D""></div><div =
class=3D"">Victor</div></div></body></html>=
--Apple-Mail=_F8BCAB64-A19B-4B00-B41B-03BE06C12A1F--
--On Sunday, August 11, 2019 7:34 PM +0000 zagarc(a)oclc.org wrote:
> Would you please consider changing this to:
>
> TMP=${TMPDIR-/tmp}/mkdep$$
Thanks for the report, this is fixed in OpenLDAP master.
Regards,
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.48
OS: N/A
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (47.208.128.44)
When looking at the man pages, the tls_reqcert description in the section of the
man page about syncrepl is missing a BOLD tag, unlike the other keywords.
Trivial fix.
Full_Name: Chris Zagar
Version: 2.4.48
OS: Linux
URL:
Submission from: (NULL) (68.98.212.84)
/build/mkdep contains this line:
TMP=/tmp/mkdep$$
that forces the use of the /tmp directory. The /tmp directory is vulnerable to
race conditions. The rest of OpenLDAP obeys the TMPDIR environment variable if
it exists as a mitigation to this risk. Would you please consider changing this
to:
TMP=${TMPDIR-/tmp}/mkdep$$
so this will obey TMPDIR as well?
Thank you.
Chris Zagar
zagarc(a)oclc.org
--On Wednesday, August 07, 2019 10:35 AM +0000 alex.s(a)wildix.com wrote:
> Full_Name: Alex
> Version: 2.4.44+dfsg-5+deb9u2
Hello,
The ITS system is for bug reports, not usage questions. Additionally, if
you're doing replication of any type, please upgrade to the latest release
(2.4.48). Ensure you are using delta-syncrepl. For any other questions,
please use the correct forum which is the openldap-technical(a)openldap.org
mailing list:
<https://www.openldap.org/lists/mm/listinfo/openldap-technical>.
I believe there is a backport of 2.4.48 for Debian9 from the backports repo.
This ITS will be closed.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Full_Name: Alex
Version: 2.4.44+dfsg-5+deb9u2
OS: Debian 9
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (154.41.3.130)
Hello
I have some issues with replication between Master and Slave LDAP servers.
Preconditions data:
I have a Master server with a huge LDAP data
And also I have about 200 Slave servers around the world which have a data
replica in their databases.
What happened:
I have applied a bckup on Master server. (Actually data have not changed except
entryCSN)
entryCSN has been deleted from backup previously, before apply, for actualise
data in LDAP database.
As a result I had a situation when all Slave servers starts replication.
The first question is: how I can avoid full replication after apply backup on
Master? I understand that entryCSN changed and LDAP should sync some objects.
But can I use another way to actualize the data in LDAP database instead of
entryCSN?
The second question is: after apply backup and restarts the Master server I had
a problem with local LDAP because all Slave servers start connecting and start
their replication. In this case LDAP on Master server not responding even on
localhost via ldapsearch. May I change some parameters to increase concurrent
connections? Because LDAP starts not responding if the quantity of simultaneous
connected of Slave servers exceeds 10-15
Thank you in advance
Best regards, Alex
> On 1. Aug 2019, at 19:47, Howard Chu <hyc(a)symas.com> wrote:
>=20
> vporof(a)mozilla.com wrote:
>> Hey folks.
>>=20
>> =3D46rom Myk=3DE2=3D80=3D99s investigations in the previous followup, =
it seems =3D
>> that the suggested changes to `mdb_cursor_init` to avoid using an =3D
>> invalid DBI might not be solving the actual issue, given the =
behaviour =3D
>> of `mdb_page_search`.
>=20
> Agreed, that assert that I suggested isn't catching what we want.
FWIW, here's my findings when attempting to look into what was happening =
with regards to that test case: =
https://gist.github.com/victorporof/d1f98b8a52f79c7ff99f361d3a2adc3e
It's unclear how much overlap there is with the previous findings, and =
whether or not calling `mdb_put` should assert with the DBI previously =
opened via `mdb_dbi_open` with MDB_CREATE. Let me know if what I'm =
observing here is expected.
>=20
>> It=3DE2=3D80=3D99s also causing the seemingly correct test program to =
assert =3D
>> when it wasn=3DE2=3D80=3D99t before. It=3DE2=3D80=3D99s unclear =
whether this should =3D
>> be the case or not, perhaps Howard can confirm the expected =
behaviour.
>>=20
>> In any case, we=3DE2=3D80=3D99re wondering if there=3DE2=3D80=3D99s =
been any other =3D
>> progress, or if someone managed to reproduce this issue? Shipping new =
=3D
>> features built on top of LMDB in Firefox is currently blocked due to =
=3D
>> these failures, so any additional info would be helpful.
>=20
> Sorry, still not seeing this over here. What else do you know about =
the
> systems where this is occurring? RAM size, storage on HDD / SSD / USB =
?
Here's everything we know about: =
https://crash-stats.mozilla.org/report/index/5d77bd19-41ce-459f-9c1c-7f9fb=
0190324 See the "details" and "telemetry environment" sections for a =
breakdown.
Victor
>=20
> --=20
> -- Howard Chu
> CTO, Symas Corp. http://www.symas.com
> Director, Highland Sun http://highlandsun.com/hyc/
> Chief Architect, OpenLDAP http://www.openldap.org/project/