Hi all, We're seeing an odd issue where when rndc reload is called named segfaults but not 100% of the time ... so the exact circumstances are hard to reproduce although it happens on all four instances (sometime at the same time which is problematic).
When it happens we see the following in the logs: Jun 30 03:07:02 ipa01 named[4228]: client 10.137.17.1#52842: received notify for zone 'example.com' Jun 30 03:07:03 ipa01 named[4228]: client 10.137.17.1#1131: received notify for zone '9.139.10.in-addr.arpa' Jun 30 03:07:03 ipa01 named[4228]: client 10.137.17.1#1131: received notify for zone 'dev.example.com' Jun 30 03:07:03 ipa01 named[4228]: client 10.137.17.1#1131: received notify for zone '8.139.10.in-addr.arpa' Jun 30 03:07:03 ipa01 named[4228]: client 10.137.17.1#1131: received notify for zone 'prod.example.com' Jun 30 03:07:03 ipa01 named[4228]: client 10.137.17.1#64362: received notify for zone '16.137.10.in-addr.arpa' Jun 30 03:07:03 ipa01 named[4228]: client 10.137.17.1#64362: received notify for zone '17.137.10.in-addr.arpa' Jun 30 03:07:03 ipa01 named[4228]: client 10.137.17.1#64362: received notify for zone '18.137.10.in-addr.arpa' Jun 30 03:07:03 ipa01 named[4228]: client 10.137.17.1#64362: received notify for zone '19.137.10.in-addr.arpa' Jun 30 03:07:07 ipa01 named[4228]: client 10.137.17.1#56263: received notify for zone '17.137.10.in-addr.arpa' Jun 30 03:07:08 ipa01 named[4228]: client 10.137.17.1#30345: received notify for zone '18.137.10.in-addr.arpa' Jun 30 03:07:08 ipa01 named[4228]: client 10.137.17.1#30345: received notify for zone '19.137.10.in-addr.arpa' Jun 30 03:10:01 ipa01 named[4228]: received control channel command 'reload' Jun 30 03:10:01 ipa01 named[4228]: loading configuration from '/etc/named.conf' Jun 30 03:10:01 ipa01 named[4228]: using default UDP/IPv4 port range: [1024, 65535] Jun 30 03:10:01 ipa01 named[4228]: using default UDP/IPv6 port range: [1024, 65535] Jun 30 03:10:01 ipa01 named[4228]: sizing zone task pool based on 6 zones Jun 30 03:10:01 ipa01 named[4228]: /etc/named.conf:12: no forwarders seen; disabling forwarding Jun 30 03:10:01 ipa01 named[4228]: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones Jun 30 03:10:01 ipa01 named[4228]: /etc/named.conf:12: no forwarders seen; disabling forwarding 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 ipa-admintools-3.0.0-26.el6_4.2.x86_64 ipa-pki-ca-theme-9.0.3-7.el6.noarch libipa_hbac-1.9.2-82.7.el6_4.x86_64 libipa_hbac-python-1.9.2-82.7.el6_4.x86_64 ipa-pki-common-theme-9.0.3-7.el6.noarch python-iniparse-0.3.1-2.1.el6.noarch ipa-python-3.0.0-26.el6_4.2.x86_64 ipa-client-3.0.0-26.el6_4.2.x86_64 ipa-server-3.0.0-26.el6_4.2.x86_64 ipa-server-selinux-3.0.0-26.el6_4.2.x86_64 389-ds-base-libs-1.2.11.15-14.el6_4.x86_64 389-ds-base-1.2.11.15-14.el6_4.x86_64 Cheers, James
_______________________________________________ Freeipa-users mailing list Freeipa-users@redhat.com https://www.redhat.com/mailman/listinfo/freeipa-users
