Full_Name: Dany Bensighar
Version: 2.4.44
OS: Red Hat Enterprise Linux Server release 7.6 (Maipo)
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (212.138.78.4)
Hello,
Iam setting up a master slave openldap configuration in rhel 7, while adding the
syncprov module I am getting the below error. I have checked openspaces and
special characters but nothing found
Please find the syncprov.ldif file
dn: olcOverlay=syncprov,olcDatabase={2}hdb,cn=config
objectClass: olcOverlayConfig
objectClass: olcSyncProvConfig
olcOverlay: syncprov
olcSpSessionLog: 100
Please find the error
ldapadd -Y EXTERNAL -H ldapi:/// -f syncprov.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=1001+uidNumber=1001,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "olcOverlay=syncprov,olcDatabase={2}hdb,cn=config"
ldap_add: Invalid syntax (21)
additional info: objectClass: value #1 invalid per syntax
Your support will be highly appreciated
--000000000000856dab058992e756
Content-Type: text/plain; charset="UTF-8"
The short answer is yes. Our mappings are now bigger than 1TiB (out of 2TiB
total available). Also, it *seems* to be that it is just way faster for
Linux to map things in order all at once. Additionally, we have some boxes
that still have spinning disks, and sequential access is a couple orders of
magnitude faster on those.
I haven't looked at the logic in the Linux pager, but it seems to be fairly
aggressive about taking memory pages back from large memory maps, even
though it doesn't strictly need to. Locking the memory is a bit of a
sledgehammer, but in our experience it is an effective one.
On Thu, May 23, 2019 at 2:23 PM Howard Chu <hyc(a)symas.com> wrote:
> github(a)nicwatson.org wrote:
> > Full_Name: Nic Watson
> > Version:
> > OS: Linux
> > URL: ftp://ftp.openldap.org/incoming/
> > Submission from: (NULL) (73.132.68.128)
> >
> >
> > Goal:
> > I'd like a clean way to get at the address of the data memory map in
> LMDB.
> >
> > MDB_envinfo.me_mapaddr only returns the map address if MAP_FIXED is used.
> >
> > Current Workarounds:
> > * Use OS-specific mechanism to retrieve all memory maps (e.g.
> > /proc/<pid>/smaps).
> > * Defeat opaque handle and reach into the MDB_env struct directly and
> grab the
> > me_map field.
> >
> > Justification:
> > In my current application, I notice a significant performance increase
> if I
> > mlock the mapfile. In order to do that cleanly, I need the address of
> the map.
>
> That sounds odd. Is there a lot of memory pressure from other processes on
> the machine?
> Where is the performance loss or gain coming from?
>
> --
> -- Howard Chu
> CTO, Symas Corp. http://www.symas.com
> Director, Highland Sun http://highlandsun.com/hyc/
> Chief Architect, OpenLDAP http://www.openldap.org/project/
>
--000000000000856dab058992e756
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">The short answer is yes. Our mappings are now bigger than =
1TiB (out of 2TiB total available). Also, it *seems* to be that it is just =
way faster for Linux to map things in order all at once. Additionally, we h=
ave some boxes that still have spinning disks, and sequential access is a c=
ouple orders of magnitude faster on those.<div><br></div><div>I haven't=
looked at the logic in the Linux pager, but it seems to be fairly aggressi=
ve about taking memory pages back from large memory maps, even though it do=
esn't strictly need to. Locking the memory is a bit of a sledgehammer, =
but in our experience it is an effective one.</div></div><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, May 23, 2019 at =
2:23 PM Howard Chu <<a href=3D"mailto:hyc@symas.com">hyc(a)symas.com</a>&g=
t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><a hre=
f=3D"mailto:github@nicwatson.org" target=3D"_blank">github(a)nicwatson.org</a=
> wrote:<br>
> Full_Name: Nic Watson<br>
> Version: <br>
> OS: Linux<br>
> URL: <a href=3D"ftp://ftp.openldap.org/incoming/" rel=3D"noreferrer" t=
arget=3D"_blank">ftp://ftp.openldap.org/incoming/</a><br>
> Submission from: (NULL) (73.132.68.128)<br>
> <br>
> <br>
> Goal:<br>
> I'd like a clean way to get at the address of the data memory map =
in LMDB.<br>
> <br>
> MDB_envinfo.me_mapaddr only returns the map address if MAP_FIXED is us=
ed.<br>
> <br>
> Current Workarounds:<br>
> * Use OS-specific mechanism to retrieve all memory maps (e.g.<br>
> /proc/<pid>/smaps). <br>
> * Defeat opaque handle and reach into the MDB_env struct directly and =
grab the<br>
> me_map field.<br>
> <br>
> Justification:<br>
> In my current application, I notice a significant performance increase=
if I<br>
> mlock the mapfile.=C2=A0 In order to do that cleanly, I need the addre=
ss of the map.<br>
<br>
That sounds odd. Is there a lot of memory pressure from other processes on =
the machine?<br>
Where is the performance loss or gain coming from?<br>
<br>
-- <br>
=C2=A0 -- Howard Chu<br>
=C2=A0 CTO, Symas Corp.=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"=
http://www.symas.com" rel=3D"noreferrer" target=3D"_blank">http://www.symas=
.com</a><br>
=C2=A0 Director, Highland Sun=C2=A0 =C2=A0 =C2=A0<a href=3D"http://highland=sun.com/hyc/" rel=3D"noreferrer" target=3D"_blank">http://highlandsun.com/h=
yc/</a><br>
=C2=A0 Chief Architect, OpenLDAP=C2=A0 <a href=3D"http://www.openldap.org/p=
roject/" rel=3D"noreferrer" target=3D"_blank">http://www.openldap.org/proje=
ct/</a><br>
</blockquote></div>
--000000000000856dab058992e756--
github(a)nicwatson.org wrote:
> Full_Name: Nic Watson
> Version:
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (73.132.68.128)
>
>
> Goal:
> I'd like a clean way to get at the address of the data memory map in LMDB.
>
> MDB_envinfo.me_mapaddr only returns the map address if MAP_FIXED is used.
>
> Current Workarounds:
> * Use OS-specific mechanism to retrieve all memory maps (e.g.
> /proc/<pid>/smaps).
> * Defeat opaque handle and reach into the MDB_env struct directly and grab the
> me_map field.
>
> Justification:
> In my current application, I notice a significant performance increase if I
> mlock the mapfile. In order to do that cleanly, I need the address of the map.
That sounds odd. Is there a lot of memory pressure from other processes on the machine?
Where is the performance loss or gain coming from?
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
Full_Name: Nic Watson
Version:
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (73.132.68.128)
Goal:
I'd like a clean way to get at the address of the data memory map in LMDB.
MDB_envinfo.me_mapaddr only returns the map address if MAP_FIXED is used.
Current Workarounds:
* Use OS-specific mechanism to retrieve all memory maps (e.g.
/proc/<pid>/smaps).
* Defeat opaque handle and reach into the MDB_env struct directly and grab the
me_map field.
Justification:
In my current application, I notice a significant performance increase if I
mlock the mapfile. In order to do that cleanly, I need the address of the map.
On Mon, May 20, 2019 at 10:29:02AM +0000, AYANIDES, JEAN-PHILIPPE wrote:
> Yes, it serves traffic. It doesn't crash until I run a bind with a
> wrong password.
>
>> (gdb) cont
>> Continuing.
>
> [LDAP search with wrong password]
>
>> [New Thread -1237541968 (LWP 29380)]
>
>> Program exited with code 0177.
>> (gdb) thread apply all bt full
>
> Yes sorry, It runs on an old version of debian: 4:0 32 bits that I am
> not authorised to upgrade.
>
> It the first time we record that sort of issue on that platform…
Hi Jean-Philippe,
are you able to reproduce this on a different system, if not, can you
get a more recent gdb on that system?
I have tried to reproduce with a config similar to the one you describe
didn't manage to provoke a segfault with re24 nor master.
On a side note, I don't think running the chain overlay with mode=self
will work to propagate the ppolicy information the way you want. The
same failing credentials will be used to contact the upstream server and
so the initial bind will be rejected again, not allowing the
modification to be performed.
Regards,
--
OndÅ™ej KuznÃk
Senior Software Engineer
Symas Corporation http://www.symas.com
Packaged, certified, and supported LDAP solutions powered by OpenLDAP
On Mon, May 20, 2019 at 09:44:45AM +0000, AYANIDES, JEAN-PHILIPPE wrote:
> Hello Ondřej
>
> I have proceeded like this because I had nothing more to show!
Hi Jean-Philippe,
is slapd actually willing to serve any traffic while you let gdb
continue or does it say slapd stopped immediately?
Also, while this might be a red herring, what version and architecture
of Debian do you use? There are some things about your gdb output and
library locations that I can't reconcile with any recent Debian release.
> If I run the commands as you said:
> (…)
>
> Loaded symbols for /appli/openldap-2.4.47/libexec/openldap/ppolicy-2.4.so.2
> Reading symbols from /appli/openldap-2.4.47/libexec/openldap/back_ldap-2.4.so.2...done.
> Loaded symbols for /appli/openldap-2.4.47/libexec/openldap/back_ldap-2.4.so.2
> Reading symbols from /appli/openldap-2.4.47/libexec/openldap/pw-sha2.so.0...done.
> Loaded symbols for /appli/openldap-2.4.47/libexec/openldap/pw-sha2.so.0
> Reading symbols from /appli/openldap-2.4.47/lib/libldap_r-2.4.so.2...done.
> Loaded symbols for /appli/openldap-2.4.47/lib/libldap_r-2.4.so.2
> Reading symbols from /appli/openldap-2.4.47/lib/liblber-2.4.so.2...done.
> Loaded symbols for /appli/openldap-2.4.47/lib/liblber-2.4.so.2
> Failed to read a valid object file image from memory.
> 0xb7c93183 in pthread_join () from /lib/tls/libpthread.so.0
> (gdb) set logging on
> Copying output to gdb.txt.
> (gdb) cont
> Continuing.
> [New Thread -1237541968 (LWP 29380)]
>
> Program exited with code 0177.
> (gdb) thread apply all bt full
> (gdb)
> (gdb) quit
--
OndÅ™ej KuznÃk
Senior Software Engineer
Symas Corporation http://www.symas.com
Packaged, certified, and supported LDAP solutions powered by OpenLDAP
On Mon, May 20, 2019 at 09:11:21AM +0000, jpayanides(a)prosodie.com wrote:
> Hello Quanah,
>
> what I have done:
>
>
> /var/install/openldap-2.4.47/servers/slapd/slapd -h "ldap://*:390 ldaps://*=
> :637" -l LOCAL5 -f /appli/openldap-preprod/etc/slapd.conf -u root -g root ;=
> ps aux | grep ldap
>
> gdb /var/install/openldap-2.4.47/servers/slapd/slapd 15684
>
> (gdb) set logging on
> (gdb) thread apply all bt full
> (gdb) cont
> <crashing operation>
>
> Here is the dump.
>
> Seems to crash when returning from libpthread
Hi Jean-Philippe,
the backtrace you recorded was during normal operation, you need to do
the opposite, continue to let the program crash, with gdb intercepting
that. Then you can use 'thread apply all bt full' to inspect the state
of slapd at the point it crashed, so what should you do:
> (gdb) cont
> <crashing operation>
> (gdb) thread apply all bt full
Regards,
--
OndÅ™ej KuznÃk
Senior Software Engineer
Symas Corporation http://www.symas.com
Packaged, certified, and supported LDAP solutions powered by OpenLDAP
--_004_AM0PR0202MB355397966458DFBCF87CDE19BA060AM0PR0202MB3553_
Content-Type: multipart/alternative;
boundary="_000_AM0PR0202MB355397966458DFBCF87CDE19BA060AM0PR0202MB3553_"
--_000_AM0PR0202MB355397966458DFBCF87CDE19BA060AM0PR0202MB3553_
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Hello Quanah,
what I have done:
/var/install/openldap-2.4.47/servers/slapd/slapd -h "ldap://*:390 ldaps://*=
:637" -l LOCAL5 -f /appli/openldap-preprod/etc/slapd.conf -u root -g root ;=
ps aux | grep ldap
gdb /var/install/openldap-2.4.47/servers/slapd/slapd 15684
(gdb) set logging on
(gdb) thread apply all bt full
(gdb) cont
<crashing operation>
Here is the dump.
Seems to crash when returning from libpthread
--
Jean-Philippe
________________________________
De : Quanah Gibson-Mount <quanah(a)symas.com>
Envoy=E9 : vendredi 17 mai 2019 17:30:42
=C0 : AYANIDES, JEAN-PHILIPPE; openldap-its(a)OpenLDAP.org
Objet : RE: (ITS#9023) crash using ppolicy chaining from slave to master
--On Friday, May 17, 2019 4:09 PM +0000 "AYANIDES, JEAN-PHILIPPE"
<jpayanides(a)prosodie.com> wrote:
>
>
> Hello Quanah,
>
> I am not very familiar with gdb. Can you help me doing that?
Start slapd on the server that's crashing
Get the process ID of slapd
gdb /path/to/slapd PID
For example, if slapd is located in /usr/sbin, and the process ID is 1234:
gdb /usr/sbin/slapd 1234
At the (gdb) prompt, enter the command "cont" to continue execution
Run your operation that causes slapd to crash. This should drop you back
to the (gdb) prompt.
Then run the command:
thr apply all bt full
This will provide the full backtrace.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
This message contains information that may be privileged or confidential an=
d is the property of the Capgemini Group. It is intended only for the perso=
n to whom it is addressed. If you are not the intended recipient, you are n=
ot authorized to read, print, retain, copy, disseminate, distribute, or use=
this message or any part thereof. If you receive this message in error, pl=
ease notify the sender immediately and delete all copies of this message.
--_000_AM0PR0202MB355397966458DFBCF87CDE19BA060AM0PR0202MB3553_
Content-Type: text/html; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<p style=3D"margin-top:0;margin-bottom:0">Hello Quanah,</p>
<p style=3D"margin-top:0;margin-bottom:0">what I have done:</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0"></p>
<div>/var/install/openldap-2.4.47/servers/slapd/slapd -h "ldap://*:390=
ldaps://*:637" -l LOCAL5 -f /appli/openldap-preprod/etc/slapd.conf -u=
root -g root ; ps aux | grep ldap<br>
</div>
<div>
<div><br>
</div>
<div>gdb /var/install/openldap-2.4.47/servers/slapd/slapd 15684<br>
<br>
</div>
(gdb) set logging on</div>
<div>(gdb) thread apply all bt full</div>
<div>(gdb) cont</div>
<div><crashing operation><br>
</div>
<br>
<p></p>
<p style=3D"margin-top:0;margin-bottom:0">Here is the dump.</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">Seems to crash when returning fro=
m libpthread<br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">--</p>
<p style=3D"margin-top:0;margin-bottom:0">Jean-Philippe<br>
</p>
<div id=3D"Signature">
<meta content=3D"text/html; charset=3DUTF-8">
</div>
</div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>De :</b> Quanah Gibson-Mount &l=
t;quanah(a)symas.com><br>
<b>Envoy=E9 :</b> vendredi 17 mai 2019 17:30:42<br>
<b>=C0 :</b> AYANIDES, JEAN-PHILIPPE; openldap-its(a)OpenLDAP.org<br>
<b>Objet :</b> RE: (ITS#9023) crash using ppolicy chaining from slave to ma=
ster</font>
<div> </div>
</div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;=
">
<div class=3D"PlainText">--On Friday, May 17, 2019 4:09 PM +0000 "=
AYANIDES, JEAN-PHILIPPE"
<br>
<jpayanides(a)prosodie.com> wrote:<br>
<br>
><br>
><br>
> Hello Quanah,<br>
><br>
> I am not very familiar with gdb. Can you help me doing that?<br>
<br>
<br>
Start slapd on the server that's crashing<br>
Get the process ID of slapd<br>
<br>
gdb /path/to/slapd PID<br>
<br>
For example, if slapd is located in /usr/sbin, and the process ID is 1234:<=
br>
<br>
gdb /usr/sbin/slapd 1234<br>
<br>
At the (gdb) prompt, enter the command "cont" to continue executi=
on<br>
<br>
Run your operation that causes slapd to crash. This should drop you b=
ack <br>
to the (gdb) prompt.<br>
<br>
Then run the command:<br>
<br>
thr apply all bt full<br>
<br>
This will provide the full backtrace.<br>
<br>
--Quanah<br>
<br>
<br>
--<br>
<br>
Quanah Gibson-Mount<br>
Product Architect<br>
Symas Corporation<br>
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:<br>
<<a href=3D"http://www.symas.com">http://www.symas.com</a>><br>
<br>
</div>
</span></font></div>
<span style=3D"font-size: 9px; line-height: 10px;">This message contains in=
formation that may be privileged or confidential and is the property of the=
Capgemini Group. It is intended only for the person to whom it is addresse=
d. If you are not the intended recipient, you are not authorized to read, p=
rint, retain, copy, disseminate, distribute, or use this message or any par=
t thereof. If you receive this message in error, please notify the sender i=
mmediately and delete all copies of this message.</span></body>
</html>
--_000_AM0PR0202MB355397966458DFBCF87CDE19BA060AM0PR0202MB3553_--
--_004_AM0PR0202MB355397966458DFBCF87CDE19BA060AM0PR0202MB3553_
Content-Type: text/plain; name="gdb.txt"
Content-Description: gdb.txt
Content-Disposition: attachment; filename="gdb.txt"; size=2695;
creation-date="Mon, 20 May 2019 09:10:06 GMT";
modification-date="Mon, 20 May 2019 09:10:06 GMT"
Content-Transfer-Encoding: base64
ClRocmVhZCAzIChUaHJlYWQgLTEyMjc2OTkyODAgKExXUCAxNTY4NykpOgojMCAgMHhiN2M4ODY3
OSBpbiBlcG9sbF93YWl0ICgpIGZyb20gL2xpYi90bHMvbGliYy5zby42Ck5vIHN5bWJvbCB0YWJs
ZSBpbmZvIGF2YWlsYWJsZS4KIzEgIDB4MDgwNzljYmQgaW4gc2xhcGRfZGFlbW9uX3Rhc2sgKHB0
cj0weDApIGF0IGRhZW1vbi5jOjI1MzkKICAgICAgICBhY3RpdmUgPSAwCiAgICAgICAgbCA9IDx2
YWx1ZSBvcHRpbWl6ZWQgb3V0PgogICAgICAgIGxhc3RfaWRsZV9jaGVjayA9IDE1NTgzNDMwMzgK
ICAgICAgICBlYmFkZiA9IDAKIzIgIDB4YjdjZjQwYmQgaW4gc3RhcnRfdGhyZWFkICgpIGZyb20g
L2xpYi90bHMvbGlicHRocmVhZC5zby4wCk5vIHN5bWJvbCB0YWJsZSBpbmZvIGF2YWlsYWJsZS4K
IzMgIDB4YjdjODgwMWUgaW4gY2xvbmUgKCkgZnJvbSAvbGliL3Rscy9saWJjLnNvLjYKTm8gc3lt
Ym9sIHRhYmxlIGluZm8gYXZhaWxhYmxlLgoKVGhyZWFkIDIgKFRocmVhZCAtMTIzMTg5MzU4NCAo
TFdQIDE1Njg4KSk6CiMwICAweGI3Y2Y2YzAxIGluIHB0aHJlYWRfY29uZF93YWl0QEBHTElCQ18y
LjMuMiAoKSBmcm9tIC9saWIvdGxzL2xpYnB0aHJlYWQuc28uMApObyBzeW1ib2wgdGFibGUgaW5m
byBhdmFpbGFibGUuCiMxICAweDA4MTc4ZGNmIGluIGxkYXBfaW50X3RocmVhZF9wb29sX3dyYXBw
ZXIgKHhwb29sPTB4ODJhOWMzMCkgYXQgdHBvb2wuYzo2ODMKICAgICAgICB0YXNrID0gKGxkYXBf
aW50X3RocmVhZF90YXNrX3QgKikgMHgwCiAgICAgICAgd29ya19saXN0ID0gKGxkYXBfaW50X3Rw
b29sX3BsaXN0X3QgKikgMHgxCiAgICAgICAgY3R4ID0ge2x0dV9pZCA9IDMwNjMwNzM3MTIsIGx0
dV9rZXkgPSB7e2x0a19rZXkgPSAweDgwZDM3ZjAsIGx0a19kYXRhID0gMHg4MzViNGQwLAogICAg
ICBsdGtfZnJlZSA9IDB4ODBkMzgyMCA8c2xhcF9zbF9tZW1fZGVzdHJveT59LCB7bHRrX2tleSA9
IDB4ODMzZmE4OCwgbHRrX2RhdGEgPSAweDgzNjZkNTAsCiAgICAgIGx0a19mcmVlID0gMHg4MTMz
OGQwIDxiZGJfcmVhZGVyX2ZyZWU+fSwge2x0a19rZXkgPSAweDAsIGx0a19kYXRhID0gMHgwLAog
ICAgICBsdGtfZnJlZSA9IDB9IDxyZXBlYXRzIDMwIHRpbWVzPn19CiAgICAgICAga2N0eCA9IDx2
YWx1ZSBvcHRpbWl6ZWQgb3V0PgogICAgICAgIGtleXNsb3QgPSAxMzEKICAgICAgICBoYXNoID0g
PHZhbHVlIG9wdGltaXplZCBvdXQ+CiAgICAgICAgX19QUkVUVFlfRlVOQ1RJT05fXyA9ICJsZGFw
X2ludF90aHJlYWRfcG9vbF93cmFwcGVyIgojMiAgMHhiN2NmNDBiZCBpbiBzdGFydF90aHJlYWQg
KCkgZnJvbSAvbGliL3Rscy9saWJwdGhyZWFkLnNvLjAKTm8gc3ltYm9sIHRhYmxlIGluZm8gYXZh
aWxhYmxlLgojMyAgMHhiN2M4ODAxZSBpbiBjbG9uZSAoKSBmcm9tIC9saWIvdGxzL2xpYmMuc28u
NgpObyBzeW1ib2wgdGFibGUgaW5mbyBhdmFpbGFibGUuCgpUaHJlYWQgMSAoVGhyZWFkIC0xMjEy
NTE2MTI4IChMV1AgMTU2ODQpKToKIzAgIDB4YjdjZjUxODMgaW4gcHRocmVhZF9qb2luICgpIGZy
b20gL2xpYi90bHMvbGlicHRocmVhZC5zby4wCk5vIHN5bWJvbCB0YWJsZSBpbmZvIGF2YWlsYWJs
ZS4KIzEgIDB4MDgwNzZmMWEgaW4gc2xhcGRfZGFlbW9uICgpIGF0IGRhZW1vbi5jOjI5MzIKICAg
ICAgICBpID0gPHZhbHVlIG9wdGltaXplZCBvdXQ+CiAgICAgICAgcmMgPSA8dmFsdWUgb3B0aW1p
emVkIG91dD4KIzIgIDB4MDgwNjI5NTcgaW4gbWFpbiAoYXJnYz0xMSwgYXJndj0weGJmODA3NDI0
KSBhdCBtYWluLmM6MTAxNwogICAgICAgIGkgPSAxMQogICAgICAgIG5vX2RldGFjaCA9IDAKICAg
ICAgICByYyA9IDAKICAgICAgICB1cmxzID0gMHg4MjgwMDA4ICJsZGFwOi8vKjozOTAgbGRhcHM6
Ly8qOjYzNyIKICAgICAgICB1c2VybmFtZSA9IDB4ODI4MDA1OCAicm9vdCIKICAgICAgICBncm91
cG5hbWUgPSAweDgyODAwNjggImxkYXAiCiAgICAgICAgc2FuZGJveCA9IDB4MAogICAgICAgIHN5
c2xvZ1VzZXIgPSAxNjgKICAgICAgICBwaWQgPSA8dmFsdWUgb3B0aW1pemVkIG91dD4KICAgICAg
ICB3YWl0ZmRzID0gezExLCAxMn0KICAgICAgICBjb25maWdmaWxlID0gMHg4MjgwMDI4ICIvYXBw
bGkvb3BlbmxkYXAtcHJlcHJvZC9ldGMvc2xhcGQuY29uZiIKICAgICAgICBjb25maWdkaXIgPSAw
eDAKICAgICAgICBzZXJ2ZXJOYW1lID0gPHZhbHVlIG9wdGltaXplZCBvdXQ+CiAgICAgICAgc2Nw
ID0gPHZhbHVlIG9wdGltaXplZCBvdXQ+CiAgICAgICAgc2NwX2VudHJ5ID0gPHZhbHVlIG9wdGlt
aXplZCBvdXQ+CiAgICAgICAgZGVidWdfdW5rbm93bnMgPSAoY2hhciAqKikgMHgwCiAgICAgICAg
c3lzbG9nX3Vua25vd25zID0gKGNoYXIgKiopIDB4MAogICAgICAgIGwgPSA8dmFsdWUgb3B0aW1p
emVkIG91dD4KICAgICAgICBzbGFwZF9waWRfZmlsZV91bmxpbmsgPSAxCiAgICAgICAgc2xhcGRf
YXJnc19maWxlX3VubGluayA9IDEKICAgICAgICBmaXJzdG9wdCA9IDx2YWx1ZSBvcHRpbWl6ZWQg
b3V0PgogICAgICAgIF9fUFJFVFRZX0ZVTkNUSU9OX18gPSAibWFpbiIKIzAgIDB4YjdjZjUxODMg
aW4gcHRocmVhZF9qb2luICgpIGZyb20gL2xpYi90bHMvbGlicHRocmVhZC5zby4wCkNvbnRpbnVp
bmcuCltOZXcgVGhyZWFkIC0xMjM3MTQwNTYwIChMV1AgMTY4NzYpXQoKUHJvZ3JhbSBleGl0ZWQg
d2l0aCBjb2RlIDAxNzcuCg==
--_004_AM0PR0202MB355397966458DFBCF87CDE19BA060AM0PR0202MB3553_--