key.cache.count always 0?

Unbound
1

Hi,

unlike the other counters 'key.cache.count' (stats output) is
always 0. Does that mean there is something wrong with it?

Does this value increase on your resolvers?

key-cache-size is not set in the config file and therefore should
be 4MB (default).

thanks,
nusenu

2

# unbound-control stats|grep key.cache.count
key.cache.count=1274

25.08.2018 05:16, nusenu via Unbound-users пишет:

Hi,

unlike the other counters 'key.cache.count' (stats output) is
always 0. Does that mean there is something wrong with it?

Yes. Most probably your unbound daemon has no permissions to write key
or directory contains it.

3

Yuri via Unbound-users:

# unbound-control stats|grep key.cache.count
key.cache.count=1274

25.08.2018 05:16, nusenu via Unbound-users пишет:

Hi,

unlike the other counters 'key.cache.count' (stats output) is
always 0. Does that mean there is something wrong with it?

Yes. Most probably your unbound daemon has no permissions to write key
or directory contains it.

it isn't supposed to write the key cache to disk, is it? (caches are in memory, no?)

4

Mmmmmmmm. Ah. Too late night here :slight_smile: Brains, my brains…

5

Wwwwwww. Opens man:

*key.cache.count*
	      The  number  of  items in	the key	cache.	These are DNSSEC keys,
	      one item per delegation point, and their validation status.

It should increases when validator properly configured and running.
6

this is solved now.
the counter did not increase because DNSSEC validation was not enabled.

7

:wink:
25.08.2018 06:56, nusenu via Unbound-users пишет: