4 Úno
2021
4 Úno
'21
12:05
Hi Marek,
I tried to reproduce your issue, but after following the steps you
described, nothing wrong happened in my environment.
Could you please share some more log snippets produced by Knot after the
changes you performed? It would be best, whenever the "dead loop"
occurs, to share the log from the first (and second) run of this loop.
I guess there is nothing wrong with copying the KASP database. The
signing process itself seems to be working fine, based on the log
snippet you shared earlier.
This issue is really suspicious. I can see no code path that might lead
to repeated zone 'load' event.
Thanks,
Libor
Dne 04. 02. 21 v 11:41 Marek Szuba napsal(a):
On 03/02/2021 16:55, libor.peltan wrote:
In order to attempt to mitigate the issue, you
may try purging zone
timers. Please back up the timers database first (by simply copying
the directory <storage>/timers somewhere), and then either `knotc
zone-purge example.com. +timers` or delete the directory (I assume
that you have just one zone configured at your server?).
There are other zones on that server but they are all from the same
set so I can manipulate the server with no major disruption.
Anyway, here is what I have tried (in this order) since my previous
e-mail:
- purging the timers
- downgrading knot to 2.9
- following the downgrade, deleting both the timers and the journal
- commenting out "journal-content: all" (the old master didn't use this)
Unfortunately none of these actions have helped.
Hmm. Could it be that something has gone wrong with the import of the
KASP database from the old master?