Knot DNS issueshttps://gitlab.nic.cz/knot/knot-dns/-/issues2021-04-06T21:09:02+02:00https://gitlab.nic.cz/knot/knot-dns/-/issues/722[Patch] Build fails with undefined references with slibtool.2021-04-06T21:09:02+02:00orbea[Patch] Build fails with undefined references with slibtool.Note: I intended to make a MR, but the system would not let me.
Patch: [knot-dns-undefined.patch](/uploads/7bf63fea8871b4845212290609a874ab/knot-dns-undefined.patch)
When building knot-dns with slibtool (https://dev.midipix.org/cross/s...Note: I intended to make a MR, but the system would not let me.
Patch: [knot-dns-undefined.patch](/uploads/7bf63fea8871b4845212290609a874ab/knot-dns-undefined.patch)
When building knot-dns with slibtool (https://dev.midipix.org/cross/slibtool) the build fails with many undefined references.
These are basically the same 3 issues repeated.
```
ld: warning: libdnssec.so.8, needed by .libs/libknot.so, not found (try using -rpath or -rpath-link)
```
```
ld: .libs/libknotus.a(la-rrset-dump.o): undefined reference to symbol 'pow@@GLIBC_2.29'
```
```
ld: .libs/libknotus.a(la-error.o): undefined reference to symbol 'mdb_strerror'
```
These can be fixed by adding `libdnssec.la` to `LDADD`, adding `$(math_LIBS)` and `$(lmdb_LIBS)` to `LDFLAGS`. I attached a patch that does this.
I am not sure what GNU libtool is doing to hide them, but it is a common occurrence that slibtool exposes undefined references that libtool hides by silently adding linker flags or ignoring `-no-undefined`.
Also see this downstream issue: https://bugs.gentoo.org/778335https://gitlab.nic.cz/knot/knot-dns/-/issues/706keymgr uses zone: section storage: when importing keys when it should use glo...2020-12-15T12:18:54+01:00Tuomo Soinikeymgr uses zone: section storage: when importing keys when it should use global storage:When keymgr imports keys it creates new keys directory and uses the zone: section storage setting which should only apply to zone files. This happens at least when storage is specified in template.When keymgr imports keys it creates new keys directory and uses the zone: section storage setting which should only apply to zone files. This happens at least when storage is specified in template.https://gitlab.nic.cz/knot/knot-dns/-/issues/659failed to apply journal changes after upgrade to 2.9.02019-10-22T10:00:45+02:00Pavel Stanofailed to apply journal changes after upgrade to 2.9.0hi, after upgrading knot from 2.8.1 to 2.9.0 there are errors when loading some dnssec enabled zones:
```
Oct 17 14:44:02 testns1 knotd[15159]: info: [dnssectest.eu.] zone file parsed, serial 1566477270
Oct 17 14:44:02 testns1 knotd[151...hi, after upgrading knot from 2.8.1 to 2.9.0 there are errors when loading some dnssec enabled zones:
```
Oct 17 14:44:02 testns1 knotd[15159]: info: [dnssectest.eu.] zone file parsed, serial 1566477270
Oct 17 14:44:02 testns1 knotd[15159]: error: [dnssectest.eu.] failed to apply journal changes 1566477270 -> 0 (invalid parameter)
Oct 17 14:44:02 testns1 knotd[15159]: warning: [dnssectest.eu.] failed to load journal (invalid parameter)
Oct 17 14:44:02 testns1 knotd[15159]: info: [dnssectest.eu.] zone not found
Oct 17 14:44:02 testns1 knotd[15159]: error: [dnssectest.eu.] zone event 'load' failed (not exists)
```
we are using automatic dnssec signing, with changes stored in journal
config:
```
template:
- id: default
storage: "/var/lib/knot"
semantic-checks: on
serial-policy: increment
global-module: mod-stats
zonefile-sync: -1
zonefile-load: difference
journal-content: changes
notify: [ testns2 ]
acl: [ acl_testns2 ]
dnssec-policy: default
policy:
- id: default
nsec3: on
single-type-signing: off
ksk-submission: submission
zsk-lifetime: 30d
ksk-lifetime: 365d
propagation-delay: 1m
single-type-signing: off
```
[kjournalprint.log](/uploads/e937c2695cadae6b16b825a45e2321a5/kjournalprint.log)2.9https://gitlab.nic.cz/knot/knot-dns/-/issues/532Consistent names for related options2019-09-20T19:57:45+02:00Anand BuddhdevConsistent names for related optionsNewer versions of Knot have a journal, and there are some options to adjust journal parameters. Some of them start with "journal" (eg. journal-db and journal-db-mode), whereas others start with "max" (eg, max-journal-usage). IMHO, such o...Newer versions of Knot have a journal, and there are some options to adjust journal parameters. Some of them start with "journal" (eg. journal-db and journal-db-mode), whereas others start with "max" (eg, max-journal-usage). IMHO, such options should all be prefixed with the same name, ie. "journal", so that you have "journal-db", "journal-db-mode", "journal-max-usage", "journal-max-depth". Similar treatment for "kasp-db" and "timer-db" and their related options would be nice.