[Freeipa-users] named crash: RUNTIME_CHECK pthread_mutex_destroy failed

[Petr Spacek]

On 18.2.2013 17:27, Michael Mercier wrote:
> Hello,
>
> Named stopped on one of my IPA servers over the weekend, this was the last message in the log file:
>
> ldap_helper.c:627: fatal error:
> RUNTIME_CHECK(((pthread_mutex_destroy(((&ldap_conn->lock))) == 0) ? 0 : 34) == 0) failed
> exiting (due to fatal error in library)
>
> Any ideas?
>
> All other IPA services (ipactl status) were shown as running when I checked this morning, the only service stopped was named.
>
> IPA on CentOS 6.3:
> libipa_hbac-1.8.0-32.el6.x86_64
> ipa-admintools-2.2.0-17.el6_3.1.x86_64
> ipa-pki-ca-theme-9.0.3-7.el6.noarch
> ipa-python-2.2.0-17.el6_3.1.x86_64
> ipa-client-2.2.0-17.el6_3.1.x86_64
> ipa-server-2.2.0-17.el6_3.1.x86_64
> libipa_hbac-python-1.8.0-32.el6.x86_64
> ipa-pki-common-theme-9.0.3-7.el6.noarch
> python-iniparse-0.3.1-2.1.el6.noarch
> ipa-server-selinux-2.2.0-17.el6_3.1.x86_64
>
> bind-libs-9.8.2-0.10.rc1.el6_3.6.x86_64
> bind-utils-9.8.2-0.10.rc1.el6_3.6.x86_64
> bind-dyndb-ldap-1.1.0-0.9.b1.el6_3.1.x86_64

It is known problem: https://fedorahosted.org/bind-dyndb-ldap/ticket/101

You should get fixed bind-dyndb-ldap version with CentOS 6.4. Package version 
should look like "bind-dyndb-ldap-2.3-2".

Simple "service named restart" is usable as a workaround, your data should be 
in safe.

Thank you for reporting the bug!

-- 
Petr^2 Spacek