25 Srp
2024
25 Srp
'24
14:02
Hi,
I am running knot-resolver-5.7.4 in a FreeBSD service jail (14.1-STABLE).
Note: Because I am still pretty new to using knot resolver, I may miss something important
besides [1].
MWN> sum /usr/home/jails/test/var/run/kresd/data.mdb
268 10240 /usr/home/jails/test/var/run/kresd/data.mdb
MWN> ./_STATS [2]
cache('['count_entries']'): 4953
cache('['usage_percent']'): 16.953125
### stopping jail simulates shutdown server [3]:
MWN> service jail stop test
Stopping jails: test.
MWN> sum /usr/home/jails/test/var/run/kresd/data.mdb
268 10240 /usr/home/jails/test/var/run/kresd/data.mdb
### Thus, data.mdb is preserved after shutdown!
### starting jail simulates booting server:
MWN> service jail start test
Starting jails: test.
MWN> sum /usr/home/jails/test/var/run/kresd/data.mdb
15059 10240 /usr/home/jails/test/var/run/kresd/data.mdb
MWN> ./_STATS
cache('['count_entries']'): 87
cache('['usage_percent']'): 0.15625
1) After having stopped that jail, data.mdb is still available and hasn't been
modified as shown by checksum.
2) After start of the jail including start of kresd data.mdb has been modified
(checksum).
3) cache.stats() shows significantly lower numbers.
Questions:
#) become cache.stats() reset after a reboot?
#) what am I missing?
Thanks in advance and regards,
Michael
[1] https://knot-resolver.readthedocs.io/en/stable/daemon-bindings-cache.html#p…
[2] _STATS (based on
https://knot-resolver.readthedocs.io/en/stable/daemon-bindings-cache.html#c…)
echo -n "cache('['count_entries']'): " ; echo
"cache.stats()" | nc -NU /var/run/kresd/control/kresd.sock | grep count_entries
echo -n "cache('['usage_percent']'): " ; echo
"cache.stats()" | nc -NU /var/run/kresd/control/kresd.sock | grep usage_percent
[3] a real server reboot shows the same issue with the cache
26 Srp
26 Srp
12:48
Hello, thanks for your interest in Knot Resolver :-)
On 25/08/2024 14.02, Michael Grimm via knot-resolver-users wrote:
cache('['count_entries']'): 4953
cache('['usage_percent']'): 16.953125
These values do persist for me, but I don't really know FreeBSD in
particular and don't have it at hand.
Have you checked that noone clears the files and you don't have
cache.clear() in some config, etc? Say, /var/run is usually considered
ephemeral and not persisted across reboots.
#) become cache.stats() reset after a reboot?
Beware that most of those stats are tied the single current process
(PID), counting the number of an operation was performed. But those two
above are indeed shared and persisted, as they're properties of the
data.mdb file contents.
--Vladimir
14:54
Vladimír Čunát via knot-resolver-users <knot-resolver-users(a)lists.nic.cz> wrote:
Hello, thanks for your interest in Knot Resolver :-)
I am so interested that I am in the process of getting knot-resolver-6.0.8 run on FreeBSD
;-)
On 25/08/2024 14.02, Michael Grimm via
knot-resolver-users wrote:
> cache('['count_entries']'): 4953
> cache('['usage_percent']'): 16.953125
Have you checked that noone clears the files and you
don't have cache.clear() in some config, etc?
No, I haven't a cache.clear() in my config.
Say, /var/run is usually considered ephemeral and not
persisted across reboots.
I read that in the docs an made the wrong tests, me bad.
Now, I moved the cache to '/var/db' and 'count_entries' and
'usage_percent' are persistent after restarting the jail
> #) become cache.stats() reset after a reboot?
Beware that most of those stats are tied the single
current process (PID), counting the number of an operation was performed.
I do run a very small site, one kresd process is more than needed
Thanks and sorry for the noise,
Michael
15:06
On 26/08/2024 14.54, Michael Grimm wrote:
I am so interested that I am in the process of getting
knot-resolver-6.0.8 run on FreeBSD 😉
There are still quite serious hurdles related to the "manager" part
that's new in 6.x and written mostly in python.
On our public [chat] there was Aisha attacking a part of the hurdles
(focusing on openbsd but the issues would be mostly the same), but it
doesn't look like the work's been made public (so far), I'm afraid.
[chat]: https://gitter.im/CZ-NIC/knot-resolver
(or you could use any matrix client)
15:35
Vladimír Čunát via knot-resolver-users <knot-resolver-users(a)lists.nic.cz> wrote:
On 26/08/2024 14.54, Michael Grimm wrote:
> I am so interested that I am in the process of
getting knot-resolver-6.0.8 run on FreeBSD 😉
There are still quite serious hurdles related to the
"manager" part that's new in 6.x and written mostly in python.
The regular kresd stuff compiles and runs like 5.7.4, and yes the manager took me some
time to understand.
On our public [chat] there was Aisha attacking a part
of the hurdles (focusing on openbsd but the issues would be mostly the same), but it
doesn't look like the work's been made public (so far), I'm afraid.
[chat]: https://gitter.im/CZ-NIC/knot-resolver
(or you could use any matrix client)
Thanks for that. I just had a quick scan of that communication, and it looks familiar ;-)
In [1] I reported that I needed to patch
manager/knot_resolver_manager/kresd_controller/supervisord/plugin/notifymodule.c as well.
I do assume that Aisha did the same. But I first need to get the manager running in order
to test that patch ;-)
But if you are interested I can provide you with that patch, now.
Thanks and regards,
Michael
[1]
https://lists.nic.cz/hyperkitty/list/knot-resolver-users@lists.nic.cz/messa…
90
days inactive
91
days old
knot-resolver-users@lists.nic.cz
4 comments
2 participants
participants (2)
-
Michael Grimm -
Vladimír Čunát