Hi, I've removed the command for now.
About a year ago we had to disable the shared cache in unwind. With that we can no longer report the memory usage. rev 1.167 of resolver.c: | Disable the shared cache between resolvers for now. | | Since the latest libunbound update the frontend process would segfault | about once a day on one of my MX servers with what looks like a | use-after-free deep inside of libunbound. | | Maybe we are poking too much at internals and the shared cache is too | much of a hack. #ifdef for now to ease investigation, but it is | possible that this code just has to go. Thanks, Florian On 2025-07-30 13:21 -07, Jordan Geoghegan <[email protected]> wrote: > Hello, > > I recently upgraded a few older machines to the latest 7.7 release > that had previously been running various OpenBSD versions ranging > between 6.8 and 7.3. > I've been happily running unwind on these machines for many years > now. It seems that sometime between 7.3 and 7.7 'unwindctl status > memory' command has broken: > > mail$ unwindctl status memory > msg-cache: 0 / 0 (-nan%) > rrset-cache: 0 / 0 (-nan%) > key-cache: 0 / 0 (-nan%) > neg-cache: 0 / 0 (-nan%) > > ^ output on 7.7 > > obsd73$ unwindctl status memory > msg-cache: 1179620 / 1048576 (112.50%) > rrset-cache: 1113916 / 1048576 (106.23%) > key-cache: 290834 / 1048576 (27.74%) > neg-cache: 24897 / 102400 (24.31%) > > ^ output on 7.3 > > Unwind is is definitely being used so those zero stats are bogus - I > use it fairly heavily on mail servers to perform recursive lookups to > avoid DNSBL ratelimiting etc. > I also tried running it on a fresh 7.7 install with no config and > experienced the same issue with unwindctl. > > Is 'unwindctl status memory' working for anybody else? > > I've included some info below just in case it helps. > > mail$ unwindctl status > 1. autoconf validating, 50ms 3. DoT validating, 300ms > 2. recursor validating, 150ms 4. stub resolving, 300ms > > histograms: lifetime[ms], decaying[ms] > <10 <20 <40 <60 <80 <100 <200 <400 <600 <800 > <1000 > > auto 1055 61 163 53 50 53 156 147 48 25 15 110 > 0 0 0 1 0 0 0 0 0 0 0 0 > rec 4308 128 465 580 632 845 2599 2215 241 70 16 178 > 2 0 0 0 0 1 3 2 0 0 0 0 > DoT 60 1 1 5 1 4 19 43 32 11 18 131 > 0 0 0 0 0 0 0 0 0 0 0 0 > stub 45 0 0 0 0 0 7 11 3 2 0 91 > 0 0 0 0 0 0 0 0 0 0 0 0 > > > > # cat /etc/unwind.conf > Q9=dns.quad9.net > > preference { > autoconf DoT forwarder recursor stub > } > > forwarder { 2620:fe::11 authentication name $Q9 DoT \ > 2620:fe::fe:11 authentication name $Q9 DoT \ > 9.9.9.11 authentication name $Q9 DoT \ > 149.112.112.11 authentication name $Q9 DoT > } > > force recursor { > blocklist.de > dnswl.org > mailspike.net > manitu.net > msbl.org > rspamd.com > senderscore.com > spameatingmonkey.net > spamhaus.org > surbl.org > uribl.com > virusfree.cz > } > -- In my defence, I have been left unsupervised.
