[Freeipa-users] named seg faulting

[Petr Spacek]

On 1.7.2013 09:56, James Hogarth wrote:
> Jun 30 03:10:01 ipa01 named[4228]: reloading configuration succeeded
> Jun 30 03:10:01 ipa01 named[4228]: reloading zones succeeded
> Jun 30 03:10:01 ipa01 named[4228]: task.c:1448: REQUIRE(task->state ==
> task_state_running) failed, back trace
> Jun 30 03:10:01 ipa01 named[4228]: #0 0x7f1996e74eff in ??
> Jun 30 03:10:01 ipa01 named[4228]: #1 0x7f199582589a in ??
> Jun 30 03:10:01 ipa01 named[4228]: #2 0x7f1995843a8f in ??
> Jun 30 03:10:01 ipa01 named[4228]: #3 0x7f19904df97f in ??
> Jun 30 03:10:01 ipa01 named[4228]: #4 0x7f19904e0df3 in ??
> Jun 30 03:10:01 ipa01 named[4228]: #5 0x7f19904e3e8c in ??
> Jun 30 03:10:01 ipa01 named[4228]: #6 0x7f19951f9851 in ??
> Jun 30 03:10:01 ipa01 named[4228]: #7 0x7f199475b90d in ??
> Jun 30 03:10:01 ipa01 named[4228]: exiting (due to assertion failure)
>
> Has anyone else seen similar behaviour or have any idea what could be
> causing this?
>
> The systems are CentOS 6.4 with:
> bind-9.8.2-0.17.rc1.el6_4.4.x86_64
> bind-dyndb-ldap-2.3-2.el6.x86_64

You are using old version of bind-dyndb-ldap.

Please see:
http://rhn.redhat.com/errata/RHBA-2013-0739.html
https://bugzilla.redhat.com/show_bug.cgi?id=928429

Upgrade to bind-dyndb-ldap-2.3-2.el6_4.1 should fix the problem.

As usual, we recommend to use latest released bits.

-- 
Petr^2 Spacek