journal file is out of date: removing journal file

[Klaus Darilion]

Hi Tony!

Am 31.07.2019 um 12:44 schrieb Tony Finch:
> Klaus Darilion <klaus.mailinglists at pernau.at> wrote:
>>
>> What does the log message "journal file is out of date: removing journal
>> file" exactly mean? Is it somehow problematic?
> 
> After loading a zone, named discovers the serial number of the zone
> doesn't match the serial number of the journal.
> 
> Something weird is happening, because I would expect that the zone either
> had an incremental change, which goes via the journal, so the journal will
> be up to date; or it's a full reload (e.g. thaw or axfr), in which case
> the journal should be quietly removed in the reload process; or there is
> ixfr-from-differences, in which case the journal is updated instead of
> removed when a reload happens.

In my case, ixfr-from-differences is off, and incoming and outgoing is
always AXFR. Zone config is:
  type slave;
  auto-dnssec maintain;
  dnssec-dnskey-kskonly no;
  inline-signing yes;

> If I'm skim-reading the code right, the problem might be that it checks
> the journal for staleness (in zone_postload) before checking that the
> journal needs to be removed (in zone_replacedb which is called towards the
> end of zone_postload) which is the wrong order and will cause this log
> message more frequently than it should.

So, is this then a bug or just some suboptimal processing which should
not cause any operational issues?

Thanks
Klaus