Re: [knot-resolver-users] cache size / full / kresd crash

Hi, thanks for the detailed report. On 05/06/2020 13.46, Vladimír Čunát wrote: I think there might be some issue with the usage calculation in GC. Perhaps you could try to lower the limit to trigger GC to something like 60% (down from the default 80%), and see if the issue persists? It can be done by passing "-u 60" when launching kres-cache-gc. On 05/06/2020 09.29, Petr Kyselák wrote: This shouldn't be related to the issue, but 1.4 secs is a long time to analyze the cache, considering there's just 1 second delay before it is triggered again. It's understandable given you're running it on Raspberry Pi, but I'd consider changing the delay to something like 1 minute to prevent GC from consuming too much CPU. This can be done with "-d 60000" argument to kres-cache-gc. You can check how kres-cache-gc is executed from systemd by running: $ systemctl cat kres-cache-gc.service | grep ExecStart Then, you can override the arguments for the kres-cache-gc by creating a systemd override for the kres-cache-gc.service unit: $ systemctl edit kres-cache-gc.service [Service] ExecStart=<original_command> -u 60 -d 60000 And restart the kres-cache-gc.service. I'd be interested to know if the issue persists with the lower GC limit. -- Tomas Krizek PGP: 4A8B A48C 2AED 933B D495 C509 A1FB A5F7 EF8C 4869