On 5.10.2016 08:59, Martin Basti wrote:
> 
> 
> On 05.10.2016 03:10, Richard Harmonson wrote:
>>
>>     On 10/04/2016 06:25 AM, Richard Harmonson wrote:
>>     > After successful installation and use of DNS with forwarding
>>     first on a
>>     > Master and Replica, several days pass then it stops. Using 'ipactl
>>     > status' shows named service stopped. Using 'ipactl restart'
>>     services,
>>     > DNS is running but stops again several days later. Rinse and repeat.
>>     >
>>     > All other services show running with using 'ipactl status.'
>>     Interesting,
>>     > both the Master and Replica fail. It is never just one.
>>     >
>>     > Suggestions on where to begin looking? and how?
>>     >
>>     >
>>
>>     There should be some information in the journal log. Try to issue
>>     `journalctl -u named-pkcs11.service` and look into the output for
>>     errors.
>>
>>     --
>>     Martin^3 Babinsky
>>
>>
>> Very helpful, Martin. Thank you.
>>
>> I found several the following in journal. I, believe, they fall within a
>> time period that is consistent with my observations.
>>
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: configuring command channel from '/etc/rndc.key'
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: configuring command channel from '/etc/rndc.key'
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: reloading configuration succeeded
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: reloading zones succeeded
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: zt.c:186: REQUIRE(ztp != ((void *)0) && *ztp == ((void
>> *)0)) failed, back trace
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: #0 0x5576112a8110 in ??
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: #1 0x7fde02d93c4a in ??
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: #2 0x7fde0316ff22 in ??
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: #3 0x7fddfb1462ba in ??
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: #4 0x7fddfb1464b0 in ??
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: #5 0x7fddfb146604 in ??
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: #6 0x7fde02db690c in ??
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: #7 0x7fde00ee25ca in ??
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: #8 0x7fddfff5cf6d in ??
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: exiting (due to assertion failure)
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net> systemd[1]:
>> Reloaded Berkeley Internet Name Domai
>> Oct 02 03:21:02 ds1.mydomain.net <http://ds1.mydomain.net>
>> named-pkcs11[3300]: exiting (due to assertion failure)
>>
>>
>>
>>
> 
> Hello,
> 
> what is your IPA version?
> 
> Do you have coredump? We need backtrace
> https://fedorahosted.org/bind-dyndb-ldap/wiki/BIND9/Debugging/Coredump

In short, this is likely fixed in bind-dyndb-ldap 10.1. Please upgrade.
https://bugzilla.redhat.com/show_bug.cgi?id=1362162#c6

-- 
Petr^2 Spacek

-- 
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go to http://freeipa.org for more info on the project

Reply via email to