Core 6.0.5: DNS Times Out || Multi clients || Excessive DNS queries || High CPU ||

bombz88 · March 10, 2025, 2:45am

Currently attempting to resolve a concern with one client on the network causing many DNS queries to pihole.

Pihole V6
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian

Setup: Gateway > VLANs > Pihole (as primary DNS)
Devices: 20-30 clients
Unbound: enabled

When the client is online, pihole CPU goes to approx. from 1% usage to 25% usage and query logs show all the traffic.

I cannot be certain if this is causing the concern, it was not an issue on v5.
To mitigate the concern, if i set the client .100 to a static public DNS domain or a VPN DNS server, the pihole CPU drops , and all other 20-ish devices using pihole as DNS are operational and the query logs settle down.

I am not sure why client .100 is causing the CPU to ramp up with this one client as soon as it is using pihole.
Once the client is using pihole any nslookup works for maybe 10-20 min, before all DNS traffic slows or times out completely.

Reaching out for any suggestions or if I can provide more information to resolve this concern.

Thank you.

bombz88 · March 10, 2025, 3:08pm

Not quite sure what has changed, seems that the pihole struggles to keep up with queries

>  -----head of FTL.log------
>    2025-03-10 00:47:22.835 EDT [573/T577] INFO: Received 8/8 valid NTP replies from pool.ntp.org
>    2025-03-10 00:47:22.835 EDT [573/T577] INFO: Time offset: -2.377871e+01 ms (excluded 0 outliers)
>    2025-03-10 00:47:22.836 EDT [573/T577] INFO: Round-trip delay: 7.869619e+01 ms (excluded 0 outliers)
>    2025-03-10 01:47:23.091 EDT [573/T577] INFO: Received 8/8 valid NTP replies from pool.ntp.org
>    2025-03-10 01:47:23.091 EDT [573/T577] INFO: Time offset: -7.130419e+00 ms (excluded 1 outliers)
>    2025-03-10 01:47:23.091 EDT [573/T577] INFO: Round-trip delay: 2.137811e+01 ms (excluded 1 outliers)
>    2025-03-10 02:47:23.291 EDT [573/T577] INFO: Received 8/8 valid NTP replies from pool.ntp.org
>    2025-03-10 02:47:23.291 EDT [573/T577] INFO: Time offset: -3.454140e+00 ms (excluded 1 outliers)
>    2025-03-10 02:47:23.291 EDT [573/T577] INFO: Round-trip delay: 1.586246e+01 ms (excluded 1 outliers)
>    2025-03-10 03:19:08.687 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 03:19:08.688 EDT [573/T580] INFO: Tried to resolve PTR "195.50.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 03:47:23.819 EDT [573/T577] INFO: Received 8/8 valid NTP replies from pool.ntp.org
>    2025-03-10 03:47:23.819 EDT [573/T577] INFO: Time offset: -6.471872e+00 ms (excluded 1 outliers)
>    2025-03-10 03:47:23.819 EDT [573/T577] INFO: Round-trip delay: 5.689601e+01 ms (excluded 1 outliers)
>    2025-03-10 04:00:03.119 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 04:00:03.120 EDT [573/T580] INFO: Tried to resolve PTR "19.60.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 04:00:05.295 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 04:00:05.296 EDT [573/T580] INFO: Tried to resolve PTR "30.50.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 04:00:07.567 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 04:00:07.568 EDT [573/T580] INFO: Tried to resolve PTR "20.60.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 04:00:09.615 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 04:00:09.615 EDT [573/T580] INFO: Tried to resolve PTR "160.20.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 04:00:11.887 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 04:00:11.888 EDT [573/T580] INFO: Tried to resolve PTR "50.60.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 04:00:14.159 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 04:00:14.160 EDT [573/T580] INFO: Tried to resolve PTR "111.20.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 04:00:16.431 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 04:00:16.432 EDT [573/T580] INFO: Tried to resolve PTR "170.20.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 04:00:18.735 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 04:00:18.735 EDT [573/T580] INFO: Tried to resolve PTR "1.0.0.127.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 04:00:20.943 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 04:00:20.944 EDT [573/T580] INFO: Tried to resolve PTR "6.0.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 04:00:23.183 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 04:00:23.184 EDT [573/T580] INFO: Tried to resolve PTR "24.60.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 04:00:25.327 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
> 
>    -----tail of FTL.log------
>    2025-03-10 11:00:09.423 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:09.423 EDT [573/T580] INFO: Tried to resolve PTR "160.20.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:11.791 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:11.792 EDT [573/T580] INFO: Tried to resolve PTR "50.60.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:13.871 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:13.871 EDT [573/T580] INFO: Tried to resolve PTR "111.20.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:15.887 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:15.887 EDT [573/T580] INFO: Tried to resolve PTR "1.0.0.127.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:17.967 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:17.968 EDT [573/T580] INFO: Tried to resolve PTR "6.0.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:20.079 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:20.079 EDT [573/T580] INFO: Tried to resolve PTR "24.60.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:22.159 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:22.160 EDT [573/T580] INFO: Tried to resolve PTR "150.50.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:24.239 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:24.239 EDT [573/T580] INFO: Tried to resolve PTR "21.60.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:26.639 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:26.640 EDT [573/T580] INFO: Tried to resolve PTR "23.60.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:28.719 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:28.720 EDT [573/T580] INFO: Tried to resolve PTR "22.60.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:30.895 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:30.895 EDT [573/T580] INFO: Tried to resolve PTR "110.20.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:32.943 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:32.943 EDT [573/T580] INFO: Tried to resolve PTR "20.50.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:35.023 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:35.024 EDT [573/T580] INFO: Tried to resolve PTR "150.12.12.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:37.071 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:37.072 EDT [573/T580] INFO: Tried to resolve PTR "25.60.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:39.279 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:39.279 EDT [573/T580] INFO: Tried to resolve PTR "195.50.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:00:41.327 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
>    2025-03-10 11:00:41.328 EDT [573/T580] INFO: Tried to resolve PTR "1.0.0.127.in-addr.arpa" on 127.0.0.1#53 (UDP)
>    2025-03-10 11:10:20.926 EDT [573/T577] INFO: Received 8/8 valid NTP replies from pool.ntp.org
>    2025-03-10 11:10:20.926 EDT [573/T577] INFO: Time offset: -6.152153e+00 ms (excluded 0 outliers)
>    2025-03-10 11:10:20.926 EDT [573/T577] INFO: Round-trip delay: 1.524997e+01 ms (excluded 0 outliers)

-----tail of FTL.log------
   2025-03-10 11:35:43.686 EDT [1318M] WARNING: domain_in_list("a8064043ce323404585112ebf508e998-297616628.us-east-1.elb.amazonaws.com", 0x7f950962a8, blacklist): Database is busy, assuming domain is NO                                                           T on list
   2025-03-10 11:35:43.686 EDT [1318M] WARNING: domain_in_list("a8064043ce323404585112ebf508e998-297616628.us-east-1.elb.amazonaws.com", 0x7f95096028, antigravity): Database is busy, assuming domain is                                                            NOT on list
   2025-03-10 11:35:43.687 EDT [1318M] WARNING: domain_in_list("a8064043ce323404585112ebf508e998-297616628.us-east-1.elb.amazonaws.com", 0x7f9511fdf8, gravity): Database is busy, assuming domain is NOT                                                            on list
   2025-03-10 11:35:43.687 EDT [1318M] WARNING: domain_in_list("a8064043ce323404585112ebf508e998-297616628.us-east-1.elb.amazonaws.com", 0x7f9511fb78, whitelist): Database is busy, assuming domain is NO                                                           T on list
   2025-03-10 11:35:43.687 EDT [1318M] WARNING: domain_in_list("a8064043ce323404585112ebf508e998-297616628.us-east-1.elb.amazonaws.com", 0x7f950962a8, blacklist): Database is busy, assuming domain is NO                                                           T on list
   2025-03-10 11:35:43.687 EDT [1318M] WARNING: domain_in_list("a8064043ce323404585112ebf508e998-297616628.us-east-1.elb.amazonaws.com", 0x7f95096028, antigravity): Database is busy, assuming domain is                                                            NOT on list
   2025-03-10 11:35:43.687 EDT [1318M] WARNING: domain_in_list("a8064043ce323404585112ebf508e998-297616628.us-east-1.elb.amazonaws.com", 0x7f9511fdf8, gravity): Database is busy, assuming domain is NO

Anyone have any thoughts what may be causing this?
I attempted to remove
127.0.0.1#5335

and add
1.1.1.1
1.0.0.1

no change to the concern, slow DNS and timeouts across the network, may consider reverting to a previous version

Thanks.

nprampage · March 10, 2025, 4:11pm

Look in the Pihole query logs for that device, and see what it's trying to resolve, since it seems specific to one device.

bombz88 · March 10, 2025, 6:34pm

Hello,

Appreciate the follow-up. So far any workstation PC that has been using Pihole general day to day traffic, ramps up the CPU. It's almost as if general queries are pushing the CPU and the pihole can't keep up on the traffic. Logs show the db has busy.

When the CPU is in this state (28% +) performing a pihole -d
unbound and queries become unresponsive.

Once I flip DNS to another provider (not pihole) the CPU (2%) drops and pihole -d reports unbound and queries successful.

CPU 2%

** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] g0-get-msg.net is NOERROR on lo (127.0.0.1)
[✓] g0-get-msg.net is NOERROR on eth0 (10.200.0.6)
[✓] doubleclick.com is 172.217.165.14 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] www.metger.metplxx.com is NOERROR on lo (::1)
[✓] www.metger.metplxx.com is NOERROR on eth0 (fe80::3e46:111c:c495:4fbf%eth0)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

CPU 28%

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve hlitomarnei.xyz on lo (127.0.0.1)
[✗] Failed to resolve hlitomarnei.xyz on eth0 (10.200.0.6)
[✓] doubleclick.com is 172.217.165.14 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve stats.sharenet.co.za on lo (::1)
[✗] Failed to resolve stats.sharenet.co.za on eth0 (fe80::3e46:111c:c495:4fbf%eth0)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

If any windows PC client comes online using Pihole DNS , the CPU spikes... not sure why, no changes recently.
Reviewing queries there is nothing that stands out too much

nprampage · March 10, 2025, 7:19pm

Your original post said "one client on the network causing many DNS queries..." and now you're changing that to say any workstation using Pihole causes this behavior? Just trying to figure out what our scope of concern might be.

25% usage doesn't sound like a problem to me - that's 75% free resources! But I'm not a CPU load expert.

Suggest you submit the devs a debug log so they can do more than my guessing blindly.

bombz88 · March 10, 2025, 7:30pm

Hello,
Sounds good.
May revert to a previous build (backup) for now, its affecting all clients. Mobile devices are having issues accessing wireless network, etc. due to all the queries.

At this state, is where DNS stops and times out completely.
When i disconnect the clients, the CPU drops to 1-2% and everything is operational again

Bucking_Horn · March 10, 2025, 8:54pm

It's highly unlikely that 28 queries per minute would cause a 25% load.
For comparison, Pi-hole's rate limit would kick in at 1,000 queries per minute, and we deal with user reports where that has been triggered.

Did you check what actually causes the load, e.g. via htop?

bombz88 · March 10, 2025, 9:13pm

Hello @Bucking_Horn

Thank you for the follow-up.

it's much more than 28 queries per 60sec.
I attempted to change the rate limit to 2000/30 but it didn't seem to help.

I have been picking away at seeing why any workstation on the network ramps up the CPU and effectively kills DNS as a whole.

I am open to anything to assist with this before reverting to my previous backup before I pushed the last update.

Look forward to hearing from you.

Thank you

Bucking_Horn · March 10, 2025, 9:25pm

Well, what about:

bombz88 · March 10, 2025, 9:29pm

Apologies, learning some of these troubleshooting steps as I go, I do appreciate your patience and thankful for the help

Correct me if I am wrong, it looks like FTL is pinning 1 of the CPUs?

Bucking_Horn · March 10, 2025, 9:34pm

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or if you run your Pi-hole as a Docker container:

docker exec -it <pihole-container-name-or-id> pihole -d

where you substitute <pihole-container-name-or-id> as required.

bombz88 · March 10, 2025, 9:36pm

Copy that....

Here you are
https://tricorder.pi-hole.net/ft3JJu5w/

Thanks, I am probably overlooking something.. or possibly not sure what is causing it.

Bucking_Horn · March 10, 2025, 9:53pm

Your debug log shows you are using unbound as upstream.
For some OS releases, the package manager may have installed an unbound configuration file that could cause a DNS loop.

What's the result of

sudo grep -v '^\s*#\|^$' -R /etc/unbound/unbound.conf*

bombz88 · March 10, 2025, 9:56pm

output

sudo grep -v '^\s*#\|^$' -R /etc/unbound/unbound.conf*
/etc/unbound/unbound.conf:include-toplevel: "/etc/unbound/unbound.conf.d/*.conf"
/etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf:server:
/etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf:    auto-trust-anchor-file: "/var/lib/unbound/root.key"
/etc/unbound/unbound.conf.d/remote-control.conf:remote-control:
/etc/unbound/unbound.conf.d/remote-control.conf:  control-enable: yes
/etc/unbound/unbound.conf.d/remote-control.conf:  control-interface: /run/unbound.ctl
/etc/unbound/unbound.conf.d/pi-hole.conf:server:
/etc/unbound/unbound.conf.d/pi-hole.conf:    verbosity: 0
/etc/unbound/unbound.conf.d/pi-hole.conf:    interface: 127.0.0.1
/etc/unbound/unbound.conf.d/pi-hole.conf:    port: 5335
/etc/unbound/unbound.conf.d/pi-hole.conf:    do-ip4: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    do-udp: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    do-tcp: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    do-ip6: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    prefer-ip6: no
/etc/unbound/unbound.conf.d/pi-hole.conf:    harden-glue: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    harden-dnssec-stripped: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    use-caps-for-id: no
/etc/unbound/unbound.conf.d/pi-hole.conf:    edns-buffer-size: 1232
/etc/unbound/unbound.conf.d/pi-hole.conf:    prefetch: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    num-threads: 1
/etc/unbound/unbound.conf.d/pi-hole.conf:    so-rcvbuf: 1m
/etc/unbound/unbound.conf.d/pi-hole.conf:    private-address: 192.168.0.0/16
/etc/unbound/unbound.conf.d/pi-hole.conf:    private-address: 169.254.0.0/16
/etc/unbound/unbound.conf.d/pi-hole.conf:    private-address: 172.16.0.0/12
/etc/unbound/unbound.conf.d/pi-hole.conf:    private-address: 10.0.0.0/8
/etc/unbound/unbound.conf.d/pi-hole.conf:    private-address: fd00::/8
/etc/unbound/unbound.conf.d/pi-hole.conf:    private-address: fe80::/10

Bucking_Horn · March 10, 2025, 10:14pm

No unwanted additional configuration files - that looks OK.

Your debug log has quite a few of these statements:

2025-03-10 04:00:03.120 EDT [573/T580] INFO: Tried to resolve PTR "19.60.200.10.in-addr.arpa" on 127.0.0.1#53 (UDP)
2025-03-10 04:00:05.295 EDT [573/T580] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server

At the same time, DNS requests don't make it to Pi-hole's IPv4 addresses:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve www.gxtworld.com on lo (127.0.0.1)
[✗] Failed to resolve www.gxtworld.com on eth0 (10.200.0.6)
[✓] doubleclick.com is 172.217.165.14 via a remote, public DNS server (8.8.8.8)

Are you perhaps running a firewall on your Pi-hole machine that would filter DNS traffic?

bombz88 · March 10, 2025, 10:23pm

Hey @Bucking_Horn

Happy to hear the configuration looks OK.
Hm interesting.

Pi-hole is running of a Rpi SD... no other instances running with it.
Before I updated my Pihole instance, I was running the following:

Core version is v6.0.4
Web version is v6.0.1 
FTL version is v6.0.3

This issue seemed to start happening once pushed up to the current instance:

Core version is v6.0.5
Web version is v6.0.2 
FTL version is v6.0.4

I am not saying it has anything to do with the current version. However, that's when I noticed the concerns to start... I am puzzled to be honest why FTL is pinning the CPU.

Do you think I should revert to my backup/previous version to see if it helps?

Bucking_Horn · March 10, 2025, 10:47pm

What about:

Also, please try

sudo strace -p $(cat /var/run/pihole-FTL.pid)

Exit with Ctrl + C and provide some of the output.

Is it generating output really fast or only a few lines every few seconds?

bombz88 · March 10, 2025, 10:50pm

Hello,
It generated a ton of lines very fast, and I had to ctrl+C to stop it.

Output

recvmsg(20, {msg_name={sa_family=AF_INET, sin_port=htons(40782), sin_addr=inet_addr("10.200.60.21")}, msg_namelen=28 => 16, msg_iov=[{iov_base="\10\247\1\0\0\1\0\0\0\0\0\0\7aws-iot\7wyzecam\3com"..., iov_len=1232}], msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO, cmsg_data={ipi_ifindex=if_nametoindex("eth0"), ipi_spec_dst=inet_addr("10.200.0.6"), ipi_addr=inet_addr("10.200.0.6")}}], msg_controllen=32, msg_flags=0}, 0) = 37
ioctl(20, SIOCGIFNAME, {ifr_ifindex=2, ifr_name="eth0"}) = 0
getpid()                                = 40659
getpid()                                = 40659
gettid()                                = 40659
getpid()                                = 40659
write(39, "Mar 10 18:48:37 dnsmasq[40659]: "..., 79) = 79
getpid()                                = 40659
gettid()                                = 40659
getpid()                                = 40659
gettid()                                = 40659
getpid()                                = 40659
getpid()                                = 40659
gettid()                                = 40659
getpid()                                = 40659
write(39, "Mar 10 18:48:37 dnsmasq[40659]: "..., 70) = 70
getpid()                                = 40659
gettid()                                = 40659
getpid()                                = 40659
getpid()                                = 40659
gettid()                                = 40659
getpid()                                = 40659
write(39, "Mar 10 18:48:37 dnsmasq[40659]: "..., 99) = 99
getpid()                                = 40659
gettid()                                = 40659
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d4a0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d4a0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d430, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d430, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
futex(0x7fad13d004, FUTEX_WAKE, 1)      = 1
getpid()                                = 40659
gettid()                                = 40659
getpid()                                = 40659
getpid()                                = 40659
gettid()                                = 40659
getpid()                                = 40659
write(39, "Mar 10 18:48:37 dnsmasq[40659]: "..., 100) = 100
getpid()                                = 40659
gettid()                                = 40659
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d4a0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d4a0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d430, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d430, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
fcntl(31, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0
fcntl(31, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-journal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
pread64(31, "\0\0\0%\0\0;\357\0\0\0\0\0\0\0\0", 16, 24) = 16
newfstatat(AT_FDCWD, "/etc/pihole/gravity.db-wal", 0x7fe762d3d0, 0) = -1 ENOENT (No such file or directory)
fstat(31, {st_mode=S_IFREG|0640, st_size=62844928, ...}) = 0
^Cstrace: Process 40659 detached

I tried to stop the FTL service to see if the CPU pinning would stop, and learned if that service is stopped so is the admin interface, so I restarted it