16 Úno
2015
16 Úno
'15
20:35
Hello Jan,
Please, can you verify the file permissions on KASP
database? I guess knot
can't write into the zone_k20.aa.json file in the KASP database.
I checked that, and it looks OK to me (all belong to user `knot'):
(here: restarted after clearing out keys/ directory)
49685941 4 drwxrwxr-x 3 knot knot 4096 Feb 13 16:43 /etc/kasp/
49685943 4 -rw-r--r-- 1 knot knot 278 Feb 13 16:38
/etc/kasp/policy_jp.json
49685944 4 -rw-r--r-- 1 knot knot 35 Feb 13 16:43
/etc/kasp/zone_k20.aa.json
49685942 4 drwxrwxr-x 2 knot knot 4096 Feb 16 19:32 /etc/kasp/keys
49685946 4 -rw-r----- 1 knot root 916 Feb 16 19:32
/etc/kasp/keys/1c4c994fde0b73169a79682038d689d8a045c8a5.pem
49685945 4 -rw-r----- 1 knot root 1704 Feb 16 19:32
/etc/kasp/keys/fc88d86e1b150e36d6baec75b9ed3fe9405722a5.pem
If I change knot.conf to have it run as `root', there no change other
than files being created as root of course:
2015-02-16T19:34:36 error: [k20.aa] DNSSEC, failed to execute event (not enough memory)
2015-02-16T19:34:36 error: [k20.aa] DNSSEC, failed to process events (unknown error -12)
2015-02-16T19:34:36 error: [k20.aa] failed to store changes into journal (unknown error
-12)
2015-02-16T19:34:36 error: [k20.aa] zone reload failed (unknown error -12)
Regards,
-JP