[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: (ITS#7996) Tighten race in ldap_int_initialize
On Tue, Jun 18, 2019 at 07:33:48AM +0000, Armin.Tueting@tueting-online.com wrote:
> Am Montag, den 17.06.2019, 15:40 -0700 schrieb Quanah Gibson-Mount:
>> --On Monday, June 17, 2019 7:16 PM +0200 Armin T=C3=BCting=20
>> <Armin.Tueting@tueting-online.com> wrote:
>>>> I.e., it started and then got as far as reading your ldap.conf file.
>>>> What is the contents of ldap.conf?
>>> Attached 'ldap.conf'. Nothing unusual...
>>>
>>>> Have you run the test suite (make test)? Does it pass? fail?
>>> Attached 'make_test.txt'. As far as I can see - it has been passed.
>>
>> Ok, so make test passes without issue, so it would appear there's something
>> specific with your configuration that is triggering the problem. Would you
>> be able to provide your slapd configuration (minus any passwords and the
>> like)?
> I'll privately send it to you in a seperate email.
>
>>
>> Additionally, if you could get a full gdb backtrace of the hung slapd=20
>> process that would be useful as well. I.e.:
>>
>> start up slapd
>> gdb /path/to/slapd <pid #>
> (gdb) thr apply all bt full
> #3 0x00007ffa4a92a135 in ldap_pvt_thread_mutex_lock
> #4 0x00007ffa4a944e6e in ldap_set_option
> #5 0x00007ffa4a943ed3 in openldap_ldap_init_w_conf
> #6 0x00007ffa4a944318 in openldap_ldap_init_w_sysconf
> #8 0x00007ffa4a944e38 in ldap_set_option
> #9 0x0000000000413cd6 in main ()
Hi Armin,
thank you very much for your report, this should now be fixed in master
with commit b2f4cacd4783cfe49370accc712863f9537f9924.
Regards,
--
OndÅ?ej KuznÃk
Senior Software Engineer
Symas Corporation http://www.symas.com
Packaged, certified, and supported LDAP solutions powered by OpenLDAP