By default bind rpm is adding in an entry to /etc/logrotate.d/named to rotate data/named.run and reload named service afterwards. The reload can take several seconds to complete on a larger dns set and it's causing downtime.
IPA is overriding the whole named configuration and logging is done as:
ipa-logging-ext.conf:
channel named { file "data/named.log" versions 10 size 20M; severity info; print-time yes; print-category yes; print-severity yes; };
This is causing logrotate to daily rotate an unused 0 byte file and reload the service.
N/A
named service goes down unnecessarily after midnight for several seconds.
ipa-server-install to disable /etc/logrotate.d/named after the steps: created new /etc/named.conf created named user config '/etc/named/ipa-ext.conf' created named user config '/etc/named/ipa-options-ext.conf' created named user config '/etc/named/ipa-logging-ext.conf'
freeipa-server-4.9.11-1.fc36.x86_64 freeipa-client-4.9.11-1.fc36.x86_64 package ipa-server is not installed package ipa-client is not installed 389-ds-base-2.1.6-1.fc36.x86_64 package pki-ca is not installed krb5-server-1.19.2-12.fc36.x86_64
From triage meeting notes: - remove named config for logroate - Fix our config to not use logrotation using bind itself… - Clever logrotate to detect if bind default logrotate is not there ?
Adding notifempty to the entry for /var/named/data/named.run in /etc/logrotate.d/named could help?
notifempty
/var/named/data/named.run
/etc/logrotate.d/named