e" configured to anything?
>>>> - Are you perhaps getting short on disc storage in the place where BIND
>>>> keeps its files?
>>>> - How much RAM does the server have and how much of that is BIND using?
>>>>
>>>> I would recommend re
ep5.example.com <http://iparep5.example.com>
named[541]: zone example.com/IN <http://example.com/IN>:
zone_journal_compact: could not get zone size: not found
Jul 03 07:50:51 iparep5.example.com <http://iparep5.example.com>
named[541]: zone
16.16.172.in-addr
vals.
Jul 03 07:50:44
iparep5.example.com named[541]: zone
example.com/IN:
zone_journal_compact: could not get zone size: not found
Jul 03 07:50:51
iparep5.example.com named[541]: zone
hese show this message at irregular intervals.
Jul 03 07:50:44 iparep5.example.com <http://iparep5.example.com>
named[541]: zone example.com/IN <http://example.com/IN>:
zone_journal_compact: could not get zone size: not found
Jul 03 07:50:51 iparep5.example.com <http://ipa
CentOS 9-Stream.
All three of these show this message at irregular intervals.
Jul 03 07:50:44 iparep5.example.com <http://iparep5.example.com>
named[541]: zone example.com/IN <http://example.com/IN>:
zone_journal_compact: could not get zone size: not found
; wrote:
> Hi,
>
> At the moment I have three FreeIPA systems (replicas), recently
> installed with CentOS 9-Stream.
> All three of these show this message at irregular intervals.
>
> Jul 03 07:50:44 iparep5.example.com named[541]: zone example.com/IN:
> zone_journal_compact:
Hi,
At the moment I have three FreeIPA systems (replicas), recently
installed with CentOS 9-Stream.
All three of these show this message at irregular intervals.
Jul 03 07:50:44 iparep5.example.com named[541]: zone example.com/IN:
zone_journal_compact: could not get zone size: not found
Jul
7 matches
Mail list logo