28 Bře
2017
28 Bře
'17
8:32
Hello,
For the second time after an upgrade, one of my knot instance did not
restart. (actually, it restarts but does not respond to queries)
I got theses messages in log :
2017-03-27T17:11:16 warning: [durel.eu.] discontinuity in chages history
(2017032310 -> 2017032309), dropping older changesets
2017-03-27T17:11:16 error: [durel.org.] zone event 'load' failed
(invalid parameter)
2017-03-27T17:11:16 error: [durel.eu.] failed to store changes into
journal (invalid parameter)
2017-03-27T17:11:16 error: [durel.eu.] zone event 'load' failed (invalid
parameter)
2017-03-27T17:11:27 warning: [durel.eu.] discontinuity in chages history
(2017032310 -> 2017032309), dropping older changesets
2017-03-27T17:11:27 error: [durel.eu.] failed to store changes into
journal (invalid parameter)
2017-03-27T17:11:27 error: [durel.eu.] zone event 'load' failed (invalid
parameter)
2017-03-27T17:11:27 warning: [durel.org.] discontinuity in chages
history (2017032310 -> 2017032309), dropping older changesets
2017-03-27T17:11:27 error: [durel.org.] failed to store changes into
journal (invalid parameter)
2017-03-27T17:11:27 error: [durel.org.] zone event 'load' failed
(invalid parameter)
removing all files in journal/ directory and restarting it leads to
normal behaviour.
Do you have hints about these error ?
Thanks,
--
Bastien Durel
28 Bře
28 Bře
13:45
Hello Bastien,
thanks very much for your report.
Starting with Knot DNS 2.4.x, the journal is completely reworked, so
even with our best testing effort, such problems are unfortunately
expectable to occur.
Do you have any predictable way how to reproduce the issue ?
How about the zone's configuration, especially zonefile-sync option ?
Do you have any specific log warning level - is it possible that
"notice" messages have been suppressed ?
I'm sorry for your inconveniences and hope you haven't lost data for the
rest of zones.
Thanks,
Libor
Dne 28.3.2017 v 08:32 Bastien Durel napsal(a):
Hello,
For the second time after an upgrade, one of my knot instance did not
restart. (actually, it restarts but does not respond to queries)
I got theses messages in log :
2017-03-27T17:11:16 warning: [durel.eu.] discontinuity in chages
history (2017032310 -> 2017032309), dropping older changesets
2017-03-27T17:11:16 error: [durel.org.] zone event 'load' failed
(invalid parameter)
2017-03-27T17:11:16 error: [durel.eu.] failed to store changes into
journal (invalid parameter)
2017-03-27T17:11:16 error: [durel.eu.] zone event 'load' failed
(invalid parameter)
2017-03-27T17:11:27 warning: [durel.eu.] discontinuity in chages
history (2017032310 -> 2017032309), dropping older changesets
2017-03-27T17:11:27 error: [durel.eu.] failed to store changes into
journal (invalid parameter)
2017-03-27T17:11:27 error: [durel.eu.] zone event 'load' failed
(invalid parameter)
2017-03-27T17:11:27 warning: [durel.org.] discontinuity in chages
history (2017032310 -> 2017032309), dropping older changesets
2017-03-27T17:11:27 error: [durel.org.] failed to store changes into
journal (invalid parameter)
2017-03-27T17:11:27 error: [durel.org.] zone event 'load' failed
(invalid parameter)
removing all files in journal/ directory and restarting it leads to
normal behaviour.
Do you have hints about these error ?
Thanks,
14:19
Le mardi 28 mars 2017 à 13:45 +0200, Libor Peltan a écrit :
Hello Bastien,
Hello,
thanks very much for your report.
Starting with Knot DNS 2.4.x, the journal is completely reworked, so
even with our best testing effort, such problems are unfortunately
expectable to occur.
Do you have any predictable way how to reproduce the issue ?
No, I don't. It appended last time I upgraded, and this time too. Do
you want I keep journal files to send them if it appens again ?
How about the zone's configuration, especially
zonefile-sync option ?
No sync option here ; zones are simple ones, with dnssec :
- domain: "durel.eu."
file: "durel.eu"
notify: "corrin"
acl: "acl_corrin"
dnssec-policy: ecdsa
- domain: "durel.org."
file: "durel.org"
notify: "corrin"
acl: "acl_corrin"
dnssec-policy: default_rsa
with this template :
template:
- id: "default"
storage: "/var/lib/knot/internal"
ixfr-from-differences: "on"
dnssec-signing: "on"
kasp-db: "/var/lib/knot/external/keys"
serial-policy: "increment"
Do you have any specific log warning level - is it
possible that
"notice" messages have been suppressed ?
I don't :
log:
- target: "stderr"
any: "warning"
- target: "syslog"
server: "info"
zone: "notice"
any: "error"
Log I sent is from stderr (I run knot under daemontool's supervise)
Here is syslog's :
Mar 27 11:06:41 arrakeen knotd[2348]: notice: TCP, terminated inactive client, address
'2002:d41a:889a::d41a:889a@51409'
Mar 27 17:11:16 arrakeen knotd[2348]: info: stopping server
Mar 27 17:11:16 arrakeen knotd[2348]: info: updating persistent timers DB
Mar 27 17:11:16 arrakeen knotd[2348]: info: shutting down
Mar 27 17:11:16 arrakeen knotd[23402]: info: Knot DNS 2.4.2 starting
Mar 27 17:11:16 arrakeen knotd[23402]: info: binding to interface
'10.42.42.21@53'
Mar 27 17:11:16 arrakeen knotd[23402]: info: binding to interface
'2001:41d0:fe4b:ec42::e@53'
Mar 27 17:11:16 arrakeen knotd[23402]: info: binding to interface
'2a01:e35:8aea:ac42::e@53'
Mar 27 17:11:16 arrakeen knotd[23402]: info: changing GID to '152'
Mar 27 17:11:16 arrakeen knotd[23402]: info: changing UID to '134'
Mar 27 17:11:16 arrakeen knotd[23402]: info: loading 8 zones
Mar 27 17:11:16 arrakeen knotd[23402]: info: starting server
Mar 27 17:11:16 arrakeen knotd[23402]: warning: [durel.org.] discontinuity in chages
history (2017032310 -> 2017032309), dropping older changesets
Mar 27 17:11:16 arrakeen knotd[23402]: notice: [durel.org.] journal is full, flushing
Mar 27 17:11:16 arrakeen knotd[23402]: error: [durel.org.] failed to store changes into
journal (invalid parameter)
Mar 27 17:11:16 arrakeen knotd[23402]: warning: [durel.eu.] discontinuity in chages
history (2017032310 -> 2017032309), dropping older changesets
Mar 27 17:11:16 arrakeen knotd[23402]: error: [durel.org.] zone event 'load'
failed (invalid parameter)
Mar 27 17:11:16 arrakeen knotd[23402]: notice: [durel.eu.] journal is full, flushing
Mar 27 17:11:16 arrakeen knotd[23402]: error: [durel.eu.] failed to store changes into
journal (invalid parameter)
Mar 27 17:11:16 arrakeen knotd[23402]: error: [durel.eu.] zone event 'load' failed
(invalid parameter)
Mar 27 17:11:16 arrakeen knotd[23402]: info: server started in the foreground, PID 23402
Mar 27 17:11:16 arrakeen knotd[23402]: info: control, binding to
'/run/knot/knot.sock'
Mar 27 17:11:26 arrakeen knotd[23402]: info: stopping server
Mar 27 17:11:26 arrakeen knotd[23402]: info: updating persistent timers DB
Mar 27 17:11:26 arrakeen knotd[23402]: info: shutting down
Mar 27 17:11:26 arrakeen knotd[23609]: info: Knot DNS 2.4.2 starting
Mar 27 17:11:26 arrakeen knotd[23609]: info: binding to interface
'10.42.42.21@53'
Mar 27 17:11:26 arrakeen knotd[23609]: info: binding to interface
'2001:41d0:fe4b:ec42::e@53'
Mar 27 17:11:26 arrakeen knotd[23609]: info: binding to interface
'2a01:e35:8aea:ac42::e@53'
Mar 27 17:11:26 arrakeen knotd[23609]: info: changing GID to '152'
Mar 27 17:11:26 arrakeen knotd[23609]: info: changing UID to '134'
Mar 27 17:11:26 arrakeen knotd[23609]: info: loading 8 zones
Mar 27 17:11:26 arrakeen knotd[23609]: info: starting server
Mar 27 17:11:27 arrakeen knotd[23609]: warning: [durel.eu.] discontinuity in chages
history (2017032310 -> 2017032309), dropping older changesets
Mar 27 17:11:27 arrakeen knotd[23609]: notice: [durel.eu.] journal is full, flushing
Mar 27 17:11:27 arrakeen knotd[23609]: error: [durel.eu.] failed to store changes into
journal (invalid parameter)
Mar 27 17:11:27 arrakeen knotd[23609]: error: [durel.eu.] zone event 'load' failed
(invalid parameter)
Mar 27 17:11:27 arrakeen knotd[23609]: warning: [durel.org.] discontinuity in chages
history (2017032310 -> 2017032309), dropping older changesets
Mar 27 17:11:27 arrakeen knotd[23609]: notice: [durel.org.] journal is full, flushing
Mar 27 17:11:27 arrakeen knotd[23609]: error: [durel.org.] failed to store changes into
journal (invalid parameter)
Mar 27 17:11:27 arrakeen knotd[23609]: error: [durel.org.] zone event 'load'
failed (invalid parameter)
Mar 27 17:11:27 arrakeen knotd[23609]: info: server started in the foreground, PID 23609
Mar 27 17:11:27 arrakeen knotd[23609]: info: control, binding to
'/run/knot/knot.sock'
(I kept only the "internal" instance)
I'm sorry for your inconveniences and hope you
haven't lost data for
the rest of zones.
As this is the master server, no harm done. (Beside LAN clients that
cannot resolve names ;) )
Regards,
--
Bastien Durel
29 Bře
29 Bře
17:16
Hello Bastien,
Thanks much for your answers, and your effort helping us make Knot better.
Sure, if you are ready to send us more report including the journal
files the next time something similar happens, we would really
appreciate it.
Currently I made some bugfix in journal possibly related to your issue,
will be released in next (2.4.3) version. Anyway, I'm not really sure it
would fix your problems completely.
BR,
Libor
12 Dub
12 Dub
9:59
Le mercredi 29 mars 2017 à 17:16 +0200, Libor Peltan a écrit :
Hello Bastien,
Thanks much for your answers, and your effort helping us make Knot
better.
Sure, if you are ready to send us more report including the journal
files the next time something similar happens, we would really
appreciate it.
Currently I made some bugfix in journal possibly related to your
issue,
will be released in next (2.4.3) version. Anyway, I'm not really sure
it
would fix your problems completely.
Hello,
I upgraded to 2.4.3, and didn't got any broken journal.
Thanks for your work,
--
Bastien
2594
days inactive
2609
days old
4 comments
2 participants
participants (2)
-
Bastien Durel -
Libor Peltan