"Restart DNS resolver" required every few days to make browsing work again! #5608
Comments
|
I have been experiencing the same thing but it appears to be weekly on Sunday morning. I am running on a HP micro server. I have a number of Docker containers plus MySQL nginz etc and other services. Pihole in installed natively not virtualised. I have a second pihole on a pi4 as redundancy. However seems only the main pihole is being used and other devices such as desktop is unable to resolve 90% on domain until I do a server reboot. Haven't been able to pinpoint the cause but after a full server reboot all just works again. |
|
Same for me running Pi-hole in a Proxmox LXC. After an LXC restart, everything is working fine for the next 7 days.
Pi-hole version is v5.17.3 (Latest: v5.17.3) |
|
@lionslair I thought I was the only one experiencing this! 💪 If it's worth knowing, some 20 hours since posting the question and restarting DNS resolver:
|
|
I will have to note stats next week |
|
My Pi became unresponsive this evening, had to reboot. |
|
Happened again today but this time the pihole-FTL service crashed and was restarted by systemd. RAM usage was at ~60MB until ~03:30 UTC, then jumped to 215MB at ~05:00 UTC.
(Times in screenshots are in UTC+1) Relevant log entries from journal: |
|
Happened again today. Started from midnight. No real issues again. Only thing in the log I could see was Since I have two running I do not know why its not falling over to the second IP. My guess is the first is answering it but not responding. Really confusing it does not seem to be all. Also had log records of I don't know what started this or what the issue is but it is weekly on Sunday it occurs. |
|
Happened again today. Started from midnight. No real issues again. Only thing in the log I could see was Since I have two running I do not know why its not falling over to the second IP. My guess is the first is answering it but not responding. Really confusing it does not seem to be all. Also had log records of I don't know what started this or what the issue is but it is weekly on Sunday it occurs. Gone through all logs and nothing seems off. |
|
starting to think somehow it might be connected to my tailscale / headscale install messing something up |
|
Hopefully a project contributor sees this soon as an issue 👀 |
|
Sorry for not picking this earlier, family life (outside the computer) is quite busy for me these days :-) Let's see if I can extract the key points that have been made herein so far:
This is not unexpected and rather indicates that Pi-hole is indeed still working. The most likely cause IMO for the rapid increase in memory needs: mere fact that no name resolution was running caused all the clients in your network to retry their queries quite often. As Pi-hole stores all queries in memory to have them available at an instant for the Query Log - this increase is expected.
The log excerpt you posted contains no details about a crash, the only pointer to might might be:
but this can have easily caused by something not a crash. Please review the files in your Overall, to all of you: Please check your |
|
@DL6ER Thank you for your response. The RAM usage only increases that much when the DNS gets really slow/unresponsive. From the At this time the increased RAM usage also starts. Probably cause of "Keeping queries in memory for later new attempt". From then on there are multiple messages like Always for the same devices. I've defined local DNS records for most of my devices to the IPv4 and fe80 IPv6 of the devices. The warning messages above are only logged for some of my devices. Later the log stops at 04:46 and the restart at 06:16 is logged: From Also some queries seems to be served from cache: So the queries are received but cannot be handled due to a hanging pihole-FTL service? SHM size in the LCX is currently 7.8G which should be enough. |
No, they are processed and the result is:
I heard @lionslair is also using tailscale / headscale, maybe some connection gets lost here. Others are running in some containerized/virtualized environment and maybe something is happening to the network interface here, too. |
|
I prepared a special FTL version for you to try, it does nothing more than trying to be somewhat more verbose when sending packets failed the way we observe them failing for you. Please run and check for new log lines like once you see this happening the next time. Important This special branch is only meant to be used by Pi-hole v5.x users. Do not try to use them if you are currently participating in Pi-hole's public v6 beta. |
|
Hello everyone, I can confirm this problem on my system and maybe I can contribute by adding my setup information. Pi-hole [v5.17.3] It is a Debian 12 "bookworm" VM on a Proxmox server, all packages are up to date on both the guest and the host system. Problems started on Friday evening, all of a sudden no DNS queries could get resolved anymore. I stopped and restarted "blocking" via the web frontend, since it gave me a red dot and "blocking disabled" on the upper left of the screen. This worked up untill 11:54 am today, at least that's when all of my Proxmox VMs stopped responding and giving load updates to the host system. Unfortunately, I was not able to reach the web frontend today, so I ultimately had to reboot the whole Proxmox server. I had extensive logging going on the last weeks as I was trying to identify a dodgy iot device that repeatedly kept spamming ntp servers. After finding and eliminating the problem, I switched off logging, flushed the 24h logs, removed some temporary "helper" local DNS entries and deleted the long-term logs manually by doing "rm pihole-FTL.db" after stopping the FTL-service and restarting it afterwards, as described here: https://discourse.pi-hole.net/t/how-to-clear-all-logs-including-long-term-data/39514 This can be a simple coincidence though, as I also recently updated the FTL component from 5.24 to 5.25.1 via pihole -up. EDIT: I added EDIT2: I have no upstream DNS servers configured, I use unbound on localhost. |
|
Using two servers both ipv4 and IPv6 I think I mentioned I also have a backup instance but requests seem to be using the primary instance. I will try your branch. As I said It happens every Sunday morning for over a month and I really appreciate the feedback and help as I have tried to find it myself but I am missing something. Can not find anything in the log. Programmer myself so not phased scanning logs and after three hours found nothing today. Will try the branch thank you. |
Getting GitHub error
|
|
My upstream DNS servers are Cloudflare IPv4: I don't think it's related to network errors in my case, since I'm monitoring my network including the online connection and there are no problems logged. Trying to checkout the test branch also gives me the error Edit: |
Hmm, this should not happen (quite obviously). Can you resolve any names on your Pi-hole? Note that if your Pi-hole is using itself as resolver ( |
Was on phone but will try again this morning. On same network from phone. It's very odd I have had strange GitHub resolution issues when building Docker and the host connected to tail scale before but that seems to have resolved itself last few months. |
|
Ran this ╰─$ pihole checkout ftl fix/ede_neterr
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
[✓] Branch fix/ede_neterr exists
[i] Switching to branch: "fix/ede_neterr" from "fix/ede_neterr"
[✓] Downloading and Installing FTL
[✓] Restarting pihole-FTL service...
[✓] Enabling pihole-FTL service to start on reboot...
fatal: unable to access 'https://github.com/pi-hole/pi-hole/': Could not resolve host: github.com
fatal: unable to access 'https://github.com/pi-hole/web/': Could not resolve host: github.com
fatal: unable to access 'https://github.com/pi-hole/FTL/': Could not resolve host: github.com
but the log has this ar 25 07:49:54 llserver systemd[1]: pihole-FTL.service: Succeeded.
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.710 1294888M] Using log file /var/log/pihole/FTL.log
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.710 1294888M] ########## FTL started on llserver.lionslair.net.au! ##########
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] FTL branch: fix/ede_neterr
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] FTL version: vDev-d0f1682
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] FTL commit: d0f16824
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] FTL date: 2024-03-24 12:42:49 +0100
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] FTL user: pihole
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] Compiled for x86_64 (compiled on CI) using gcc (Debian 8.3.0-6) 8.3.0
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] SOCKET_LISTENING: only local
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] AAAA_QUERY_ANALYSIS: Show AAAA queries
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] MAXDBDAYS: max age for stored queries is 365 days
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] RESOLVE_IPV6: Resolve IPv6 addresses
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] RESOLVE_IPV4: Resolve IPv4 addresses
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] DBINTERVAL: saving to DB file every minute
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] DBFILE: Using /etc/pihole/pihole-FTL.db
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] MAXLOGAGE: Importing up to 24.0 hours of log data
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] PRIVACYLEVEL: Set to 0
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] IGNORE_LOCALHOST: Show queries from localhost
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] BLOCKINGMODE: Null IPs for blocked domains
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] DBIMPORT: Importing history from database
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] PIDFILE: Using /run/pihole-FTL.pid
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] SOCKETFILE: Using /run/pihole/FTL.sock
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] SETUPVARSFILE: Using /etc/pihole/setupVars.conf
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] MACVENDORDB: Using /etc/pihole/macvendor.db
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] GRAVITYDB: Using /etc/pihole/gravity.db
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] PARSE_ARP_CACHE: Active
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] CNAME_DEEP_INSPECT: Active
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] DELAY_STARTUP: No delay requested.
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] BLOCK_ESNI: Enabled, blocking _esni.{blocked domain}
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] NICE: Set process niceness to -10 (default)
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] MAXNETAGE: Removing IP addresses and host names from network table after 365 days
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] NAMES_FROM_NETDB: Enabled, trying to get names from network database
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] EDNS0_ECS: Overwrite client from ECS information
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] REFRESH_HOSTNAMES: Periodically refreshing IPv4 names
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.711 1294888M] RATE_LIMIT: Rate-limiting client making more than 5000 queries in 60 seconds
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] LOCAL_IPV4: Automatic interface-dependent detection of address
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] LOCAL_IPV6: Automatic interface-dependent detection of address
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] BLOCK_IPV4: Automatic interface-dependent detection of address
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] BLOCK_IPV6: Automatic interface-dependent detection of address
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] SHOW_DNSSEC: Enabled, showing automatically generated DNSSEC queries
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] MOZILLA_CANARY: Enabled
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] PIHOLE_PTR: internal PTR generation enabled (pi.hole)
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] ADDR2LINE: Enabled
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] REPLY_WHEN_BUSY: Drop queries when the database is busy
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] BLOCK_TTL: 2 seconds
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] BLOCK_ICLOUD_PR: Enabled
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] CHECK_LOAD: Enabled
Mar 25 07:49:54 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] CHECK_SHMEM: Warning if shared-memory usage exceeds 90%
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] CHECK_DISK: Warning if certain disk usage exceeds 90%
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] Finished config file parsing
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] Creating mutex
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.712 1294888M] Creating mutex
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.713 1294888M] PID of FTL process: 1294888
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.714 1294888M] Database version is 12
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.714 1294888M] Resizing "FTL-strings" from 40960 to (81920 * 1) == 81920 (/dev/shm: 712.7KB used, 2.0GB total, FTL uses 700.8KB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.714 1294888M] Imported 0 alias-clients
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.715 1294888M] Database successfully initialized
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.770 1294888M] New upstream server: 1.0.0.1:53 (0/512)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.838 1294888M] New upstream server: 9.9.9.9:53 (1/512)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.911 1294888M] Resizing "FTL-queries" from 229376 to (8192 * 56) == 458752 (/dev/shm: 753.7KB used, 2.0GB total, FTL uses 741.7KB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.917 1294888M] New upstream server: 149.112.112.112:53 (2/512)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:54.921 1294888M] New upstream server: 1.1.1.1:53 (3/512)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:55.036 1294888M] Resizing "FTL-queries" from 458752 to (12288 * 56) == 688128 (/dev/shm: 983.0KB used, 2.0GB total, FTL uses 971.1KB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:55.154 1294888M] Resizing "FTL-queries" from 688128 to (16384 * 56) == 917504 (/dev/shm: 1.2MB used, 2.0GB total, FTL uses 1.2MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:55.225 1294888M] Resizing "FTL-domains" from 12288 to (1024 * 24) == 24576 (/dev/shm: 1.4MB used, 2.0GB total, FTL uses 1.4MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:55.230 1294888M] Resizing "FTL-queries" from 917504 to (20480 * 56) == 1146880 (/dev/shm: 1.5MB used, 2.0GB total, FTL uses 1.4MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:55.316 1294888M] Resizing "FTL-queries" from 1146880 to (24576 * 56) == 1376256 (/dev/shm: 1.7MB used, 2.0GB total, FTL uses 1.7MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:55.380 1294888M] Resizing "FTL-queries" from 1376256 to (28672 * 56) == 1605632 (/dev/shm: 1.9MB used, 2.0GB total, FTL uses 1.9MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:55.434 1294888M] Resizing "FTL-queries" from 1605632 to (32768 * 56) == 1835008 (/dev/shm: 2.1MB used, 2.0GB total, FTL uses 2.1MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:55.513 1294888M] Resizing "FTL-queries" from 1835008 to (36864 * 56) == 2064384 (/dev/shm: 2.4MB used, 2.0GB total, FTL uses 2.4MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:55.590 1294888M] Resizing "FTL-queries" from 2064384 to (40960 * 56) == 2293760 (/dev/shm: 2.6MB used, 2.0GB total, FTL uses 2.6MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:55.655 1294888M] Resizing "FTL-queries" from 2293760 to (45056 * 56) == 2523136 (/dev/shm: 2.8MB used, 2.0GB total, FTL uses 2.8MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:55.739 1294888M] Resizing "FTL-domains" from 24576 to (1536 * 24) == 36864 (/dev/shm: 3.1MB used, 2.0GB total, FTL uses 3.0MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:55.778 1294888M] Resizing "FTL-queries" from 2523136 to (49152 * 56) == 2752512 (/dev/shm: 3.1MB used, 2.0GB total, FTL uses 3.1MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:55.871 1294888M] Resizing "FTL-queries" from 2752512 to (53248 * 56) == 2981888 (/dev/shm: 3.3MB used, 2.0GB total, FTL uses 3.3MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:55.942 1294888M] Resizing "FTL-queries" from 2981888 to (57344 * 56) == 3211264 (/dev/shm: 3.5MB used, 2.0GB total, FTL uses 3.5MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:56.042 1294888M] Resizing "FTL-queries" from 3211264 to (61440 * 56) == 3440640 (/dev/shm: 3.8MB used, 2.0GB total, FTL uses 3.7MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:56.112 1294888M] Resizing "FTL-queries" from 3440640 to (65536 * 56) == 3670016 (/dev/shm: 4.0MB used, 2.0GB total, FTL uses 4.0MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:56.210 1294888M] Resizing "FTL-queries" from 3670016 to (69632 * 56) == 3899392 (/dev/shm: 4.2MB used, 2.0GB total, FTL uses 4.2MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:56.289 1294888M] Resizing "FTL-queries" from 3899392 to (73728 * 56) == 4128768 (/dev/shm: 4.4MB used, 2.0GB total, FTL uses 4.4MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:56.360 1294888M] Resizing "FTL-queries" from 4128768 to (77824 * 56) == 4358144 (/dev/shm: 4.7MB used, 2.0GB total, FTL uses 4.7MB)
Mar 25 07:49:56 llserver pihole-FTL[1294888]: [2024-03-25 07:49:56.415 1294888M] Resizing "FTL-queries" from 4358144 to (81920 * 56) == 4587520 (/dev/shm: 4.9MB used, 2.0GB total, FTL uses 4.9MB)
Mar 25 07:49:57 llserver pihole-FTL[1294888]: [2024
Mar 25 07:55:55 llserver systemd[1]: pihole-FTL.service: Succeeded.
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] Using log file /var/log/pihole/FTL.log
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] ########## FTL started on llserver.lionslair.net.au! ##########
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] FTL branch: fix/ede_neterr
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] FTL version: vDev-d0f1682
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] FTL commit: d0f16824
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] FTL date: 2024-03-24 12:42:49 +0100
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] FTL user: pihole
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] Compiled for x86_64 (compiled on CI) using gcc (Debian 8.3.0-6) 8.3.0
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] SOCKET_LISTENING: only local
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] AAAA_QUERY_ANALYSIS: Show AAAA queries
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] MAXDBDAYS: max age for stored queries is 365 days
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] RESOLVE_IPV6: Resolve IPv6 addresses
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] RESOLVE_IPV4: Resolve IPv4 addresses
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] DBINTERVAL: saving to DB file every minute
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] DBFILE: Using /etc/pihole/pihole-FTL.db
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] MAXLOGAGE: Importing up to 24.0 hours of log data
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] PRIVACYLEVEL: Set to 0
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] IGNORE_LOCALHOST: Show queries from localhost
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] BLOCKINGMODE: Null IPs for blocked domains
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] DBIMPORT: Importing history from database
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] PIDFILE: Using /run/pihole-FTL.pid
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] SOCKETFILE: Using /run/pihole/FTL.sock
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] SETUPVARSFILE: Using /etc/pihole/setupVars.conf
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] MACVENDORDB: Using /etc/pihole/macvendor.db
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] GRAVITYDB: Using /etc/pihole/gravity.db
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] PARSE_ARP_CACHE: Active
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] CNAME_DEEP_INSPECT: Active
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] DELAY_STARTUP: No delay requested.
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.537 1299648M] BLOCK_ESNI: Enabled, blocking _esni.{blocked domain}
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] NICE: Set process niceness to -10 (default)
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] MAXNETAGE: Removing IP addresses and host names from network table after 365 days
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] NAMES_FROM_NETDB: Enabled, trying to get names from network database
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] EDNS0_ECS: Overwrite client from ECS information
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] REFRESH_HOSTNAMES: Periodically refreshing IPv4 names
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] RATE_LIMIT: Rate-limiting client making more than 5000 queries in 60 seconds
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] LOCAL_IPV4: Automatic interface-dependent detection of address
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] LOCAL_IPV6: Automatic interface-dependent detection of address
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] BLOCK_IPV4: Automatic interface-dependent detection of address
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] BLOCK_IPV6: Automatic interface-dependent detection of address
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] SHOW_DNSSEC: Enabled, showing automatically generated DNSSEC queries
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] MOZILLA_CANARY: Enabled
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] PIHOLE_PTR: internal PTR generation enabled (pi.hole)
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] ADDR2LINE: Enabled
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] REPLY_WHEN_BUSY: Drop queries when the database is busy
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] BLOCK_TTL: 2 seconds
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] BLOCK_ICLOUD_PR: Enabled
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] CHECK_LOAD: Enabled
Mar 25 07:55:55 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] CHECK_SHMEM: Warning if shared-memory usage exceeds 90%
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] CHECK_DISK: Warning if certain disk usage exceeds 90%
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] Finished config file parsing
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] Creating mutex
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.538 1299648M] Creating mutex
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.549 1299648M] PID of FTL process: 1299648
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.549 1299648M] Database version is 12
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.549 1299648M] Resizing "FTL-strings" from 40960 to (81920 * 1) == 81920 (/dev/shm: 712.7KB used, 2.0GB total, FTL uses 700.8KB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.550 1299648M] Imported 0 alias-clients
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.550 1299648M] Database successfully initialized
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.617 1299648M] New upstream server: 1.0.0.1:53 (0/512)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.674 1299648M] New upstream server: 9.9.9.9:53 (1/512)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.739 1299648M] New upstream server: 149.112.112.112:53 (2/512)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.741 1299648M] New upstream server: 1.1.1.1:53 (3/512)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.745 1299648M] Resizing "FTL-queries" from 229376 to (8192 * 56) == 458752 (/dev/shm: 753.7KB used, 2.0GB total, FTL uses 741.7KB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.776 1299648M] Resizing "FTL-queries" from 458752 to (12288 * 56) == 688128 (/dev/shm: 983.0KB used, 2.0GB total, FTL uses 971.1KB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.800 1299648M] Resizing "FTL-queries" from 688128 to (16384 * 56) == 917504 (/dev/shm: 1.2MB used, 2.0GB total, FTL uses 1.2MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.821 1299648M] Resizing "FTL-domains" from 12288 to (1024 * 24) == 24576 (/dev/shm: 1.4MB used, 2.0GB total, FTL uses 1.4MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.824 1299648M] Resizing "FTL-queries" from 917504 to (20480 * 56) == 1146880 (/dev/shm: 1.5MB used, 2.0GB total, FTL uses 1.4MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.846 1299648M] Resizing "FTL-queries" from 1146880 to (24576 * 56) == 1376256 (/dev/shm: 1.7MB used, 2.0GB total, FTL uses 1.7MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.868 1299648M] Resizing "FTL-queries" from 1376256 to (28672 * 56) == 1605632 (/dev/shm: 1.9MB used, 2.0GB total, FTL uses 1.9MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.890 1299648M] Resizing "FTL-queries" from 1605632 to (32768 * 56) == 1835008 (/dev/shm: 2.1MB used, 2.0GB total, FTL uses 2.1MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.916 1299648M] Resizing "FTL-queries" from 1835008 to (36864 * 56) == 2064384 (/dev/shm: 2.4MB used, 2.0GB total, FTL uses 2.4MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.950 1299648M] Resizing "FTL-queries" from 2064384 to (40960 * 56) == 2293760 (/dev/shm: 2.6MB used, 2.0GB total, FTL uses 2.6MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:55.984 1299648M] Resizing "FTL-queries" from 2293760 to (45056 * 56) == 2523136 (/dev/shm: 2.8MB used, 2.0GB total, FTL uses 2.8MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:56.004 1299648M] Resizing "FTL-domains" from 24576 to (1536 * 24) == 36864 (/dev/shm: 3.1MB used, 2.0GB total, FTL uses 3.0MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:56.019 1299648M] Resizing "FTL-queries" from 2523136 to (49152 * 56) == 2752512 (/dev/shm: 3.1MB used, 2.0GB total, FTL uses 3.1MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:56.049 1299648M] Resizing "FTL-queries" from 2752512 to (53248 * 56) == 2981888 (/dev/shm: 3.3MB used, 2.0GB total, FTL uses 3.3MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:56.090 1299648M] Resizing "FTL-queries" from 2981888 to (57344 * 56) == 3211264 (/dev/shm: 3.5MB used, 2.0GB total, FTL uses 3.5MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:56.133 1299648M] Resizing "FTL-queries" from 3211264 to (61440 * 56) == 3440640 (/dev/shm: 3.8MB used, 2.0GB total, FTL uses 3.7MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:56.163 1299648M] Resizing "FTL-queries" from 3440640 to (65536 * 56) == 3670016 (/dev/shm: 4.0MB used, 2.0GB total, FTL uses 4.0MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:56.208 1299648M] Resizing "FTL-queries" from 3670016 to (69632 * 56) == 3899392 (/dev/shm: 4.2MB used, 2.0GB total, FTL uses 4.2MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:56.254 1299648M] Resizing "FTL-queries" from 3899392 to (73728 * 56) == 4128768 (/dev/shm: 4.4MB used, 2.0GB total, FTL uses 4.4MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:56.299 1299648M] Resizing "FTL-queries" from 4128768 to (77824 * 56) == 4358144 (/dev/shm: 4.7MB used, 2.0GB total, FTL uses 4.7MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024-03-25 07:55:56.332 1299648M] Resizing "FTL-queries" from 4358144 to (81920 * 56) == 4587520 (/dev/shm: 4.9MB used, 2.0GB total, FTL uses 4.9MB)
Mar 25 07:55:56 llserver pihole-FTL[1299648]: [2024
Mar 25 07:56:41 llserver systemd[1]: pihole-FTL.service: Succeeded.
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] Using log file /var/log/pihole/FTL.log
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] ########## FTL started on llserver.lionslair.net.au! ##########
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] FTL branch: fix/ede_neterr
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] FTL version: vDev-d0f1682
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] FTL commit: d0f16824
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] FTL date: 2024-03-24 12:42:49 +0100
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] FTL user: pihole
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] Compiled for x86_64 (compiled on CI) using gcc (Debian 8.3.0-6) 8.3.0
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] SOCKET_LISTENING: only local
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] AAAA_QUERY_ANALYSIS: Show AAAA queries
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] MAXDBDAYS: max age for stored queries is 365 days
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] RESOLVE_IPV6: Resolve IPv6 addresses
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] RESOLVE_IPV4: Resolve IPv4 addresses
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] DBINTERVAL: saving to DB file every minute
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] DBFILE: Using /etc/pihole/pihole-FTL.db
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] MAXLOGAGE: Importing up to 24.0 hours of log data
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] PRIVACYLEVEL: Set to 0
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] IGNORE_LOCALHOST: Show queries from localhost
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.485 1300005M] BLOCKINGMODE: Null IPs for blocked domains
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] DBIMPORT: Importing history from database
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] PIDFILE: Using /run/pihole-FTL.pid
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] SOCKETFILE: Using /run/pihole/FTL.sock
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] SETUPVARSFILE: Using /etc/pihole/setupVars.conf
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] MACVENDORDB: Using /etc/pihole/macvendor.db
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] GRAVITYDB: Using /etc/pihole/gravity.db
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] PARSE_ARP_CACHE: Active
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] CNAME_DEEP_INSPECT: Active
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] DELAY_STARTUP: No delay requested.
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] BLOCK_ESNI: Enabled, blocking _esni.{blocked domain}
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] NICE: Set process niceness to -10 (default)
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] MAXNETAGE: Removing IP addresses and host names from network table after 365 days
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] NAMES_FROM_NETDB: Enabled, trying to get names from network database
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] EDNS0_ECS: Overwrite client from ECS information
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] REFRESH_HOSTNAMES: Periodically refreshing IPv4 names
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] RATE_LIMIT: Rate-limiting client making more than 5000 queries in 60 seconds
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] LOCAL_IPV4: Automatic interface-dependent detection of address
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] LOCAL_IPV6: Automatic interface-dependent detection of address
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] BLOCK_IPV4: Automatic interface-dependent detection of address
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] BLOCK_IPV6: Automatic interface-dependent detection of address
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] SHOW_DNSSEC: Enabled, showing automatically generated DNSSEC queries
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] MOZILLA_CANARY: Enabled
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] PIHOLE_PTR: internal PTR generation enabled (pi.hole)
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] ADDR2LINE: Enabled
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] REPLY_WHEN_BUSY: Drop queries when the database is busy
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] BLOCK_TTL: 2 seconds
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] BLOCK_ICLOUD_PR: Enabled
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] CHECK_LOAD: Enabled
Mar 25 07:56:41 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] CHECK_SHMEM: Warning if shared-memory usage exceeds 90%
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] CHECK_DISK: Warning if certain disk usage exceeds 90%
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] Finished config file parsing
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] Creating mutex
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.486 1300005M] Creating mutex
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.489 1300005M] PID of FTL process: 1300005
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.491 1300005M] Database version is 12
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.492 1300005M] Resizing "FTL-strings" from 40960 to (81920 * 1) == 81920 (/dev/shm: 712.7KB used, 2.0GB total, FTL uses 700.8KB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.492 1300005M] Imported 0 alias-clients
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.492 1300005M] Database successfully initialized
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.565 1300005M] New upstream server: 1.0.0.1:53 (0/512)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.581 1300005M] New upstream server: 9.9.9.9:53 (1/512)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.618 1300005M] New upstream server: 149.112.112.112:53 (2/512)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.619 1300005M] New upstream server: 1.1.1.1:53 (3/512)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.630 1300005M] Resizing "FTL-queries" from 229376 to (8192 * 56) == 458752 (/dev/shm: 753.7KB used, 2.0GB total, FTL uses 741.7KB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.675 1300005M] Resizing "FTL-queries" from 458752 to (12288 * 56) == 688128 (/dev/shm: 983.0KB used, 2.0GB total, FTL uses 971.1KB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.704 1300005M] Resizing "FTL-queries" from 688128 to (16384 * 56) == 917504 (/dev/shm: 1.2MB used, 2.0GB total, FTL uses 1.2MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.722 1300005M] Resizing "FTL-domains" from 12288 to (1024 * 24) == 24576 (/dev/shm: 1.4MB used, 2.0GB total, FTL uses 1.4MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.726 1300005M] Resizing "FTL-queries" from 917504 to (20480 * 56) == 1146880 (/dev/shm: 1.5MB used, 2.0GB total, FTL uses 1.4MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.747 1300005M] Resizing "FTL-queries" from 1146880 to (24576 * 56) == 1376256 (/dev/shm: 1.7MB used, 2.0GB total, FTL uses 1.7MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.768 1300005M] Resizing "FTL-queries" from 1376256 to (28672 * 56) == 1605632 (/dev/shm: 1.9MB used, 2.0GB total, FTL uses 1.9MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.788 1300005M] Resizing "FTL-queries" from 1605632 to (32768 * 56) == 1835008 (/dev/shm: 2.1MB used, 2.0GB total, FTL uses 2.1MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.813 1300005M] Resizing "FTL-queries" from 1835008 to (36864 * 56) == 2064384 (/dev/shm: 2.4MB used, 2.0GB total, FTL uses 2.4MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.843 1300005M] Resizing "FTL-queries" from 2064384 to (40960 * 56) == 2293760 (/dev/shm: 2.6MB used, 2.0GB total, FTL uses 2.6MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.877 1300005M] Resizing "FTL-queries" from 2293760 to (45056 * 56) == 2523136 (/dev/shm: 2.8MB used, 2.0GB total, FTL uses 2.8MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.892 1300005M] Resizing "FTL-domains" from 24576 to (1536 * 24) == 36864 (/dev/shm: 3.1MB used, 2.0GB total, FTL uses 3.0MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.908 1300005M] Resizing "FTL-queries" from 2523136 to (49152 * 56) == 2752512 (/dev/shm: 3.1MB used, 2.0GB total, FTL uses 3.1MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.936 1300005M] Resizing "FTL-queries" from 2752512 to (53248 * 56) == 2981888 (/dev/shm: 3.3MB used, 2.0GB total, FTL uses 3.3MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.966 1300005M] Resizing "FTL-queries" from 2981888 to (57344 * 56) == 3211264 (/dev/shm: 3.5MB used, 2.0GB total, FTL uses 3.5MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:41.995 1300005M] Resizing "FTL-queries" from 3211264 to (61440 * 56) == 3440640 (/dev/shm: 3.8MB used, 2.0GB total, FTL uses 3.7MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:42.024 1300005M] Resizing "FTL-queries" from 3440640 to (65536 * 56) == 3670016 (/dev/shm: 4.0MB used, 2.0GB total, FTL uses 4.0MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:42.065 1300005M] Resizing "FTL-queries" from 3670016 to (69632 * 56) == 3899392 (/dev/shm: 4.2MB used, 2.0GB total, FTL uses 4.2MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:42.108 1300005M] Resizing "FTL-queries" from 3899392 to (73728 * 56) == 4128768 (/dev/shm: 4.4MB used, 2.0GB total, FTL uses 4.4MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:42.160 1300005M] Resizing "FTL-queries" from 4128768 to (77824 * 56) == 4358144 (/dev/shm: 4.7MB used, 2.0GB total, FTL uses 4.7MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024-03-25 07:56:42.203 1300005M] Resizing "FTL-queries" from 4358144 to (81920 * 56) == 4587520 (/dev/shm: 4.9MB used, 2.0GB total, FTL uses 4.9MB)
Mar 25 07:56:42 llserver pihole-FTL[1300005]: [2024
|
|
got same output with tailscale not running. I can access github Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
[✓] Branch fix/ede_neterr exists
[i] Switching to branch: "fix/ede_neterr" from "fix/ede_neterr"
[✓] Downloading and Installing FTL
[✓] Restarting pihole-FTL service...
[✓] Enabling pihole-FTL service to start on reboot...
fatal: unable to access 'https://github.com/pi-hole/pi-hole/': Could not resolve host: github.com
fatal: unable to access 'https://github.com/pi-hole/web/': Could not resolve host: github.com
fatal: unable to access 'https://github.com/pi-hole/FTL/': Could not resolve host: github.com
|
|
Maybe it is a concurrency issue when FTL is still restarting and taking a bit longer than it normally would (or you have configured a startup delay). In any case, as long as the checkout has worked ( You may want to try configuring a different |
5 tasks
╰─$ pihole -v
Pi-hole version is v5.17.3 (Latest: v5.17.3)
web version is v5.21 (Latest: v5.21)
FTL version is fix/ede_neterr vDev-d0f1682 (Latest: v5.25.1)Have updated the names servers to match the two dns server like the pi has nameserver 192.168.1.103
nameserver 192.168.1.104
|
|
Ok I am getting it again right now. Sample of some output for different domains. All seems directly related to IPV6. I have copy of the logs before reboot. anything specific you want to see. Funny not every domain is blocked there is stuff getting through. However a lot are blocked. Again after reboot all is back to normal. Those blocked domains are working |
|
hmm looking through the logs earlier in syslog. It seems bind is being started just after midnight. That is where the named errors start. |
|
I used to run bind9 before pihole. Feel I could uninstall bind9 now but I am not sure what has caused it to now automatically start on sundays last few months. |
|
Actually, I'd be more interested in the logs |
|
I've got them but need to jump on pc. Late here. Named is not usually running. It seems to now start at midnight on a Sunday. Could not find any reason why that is or what is starting it this morning. I've got the logs but was the syslog that lead me to when it started |
|
pihole.log.1 is up to midnight on the 20240330 sale with FTL.log and FTL.log.1 and added the other logs as reference. let me know if you want the full week. |
|
When did it happen exactly? None of the logs you uploaded contains a single
We may need more, see above. |
|
I looked again at your other logs from above, e.g., We do not see these queries at all in your Pi-hole logs, the last query for |
All of these lines llserver named[2795963]: client @0x7fa6b02bd940 100.64.0.5#59582Appeared in the syslog from named from just after midnight. which is why I posted that grepped snippet above. Correct the pihole logs look fine. Not all but most requests are all coming from 127.0.0.1 I feel the issue is with named or bind9 starting at sunday at midnight again. It is not configured to start on boot so reboot kills it and things return to normal. I have no idea what has started triggering this but I will remove and purge the bind9 stuff and see if it occurs again this Sunday. My guess is this was unrelated to pihole but as I was only aware of pihole running not the pre-pihole setup was looking in the wrong place. On;y thing I haven't found is now pihole and named could possibly be sharing the same port. My guess is they are not. |
By default, no two sockets can be bound to the same combination of source address and source port. But things are a bit more complex. First, we should clarify that Pi-hole is not using Another possibility for such an issue could be, for instance, (as you don't know where/how |
|
For me this issue seems to be related in some way to the log lines like which I had a lot for some devices. I'll keep watching it. |
You are right an I have said I believe this is a local issue not a pihole issue. I do understand what your saying and that is interesting. Because I had not realised NAMED/BIND was what was restarting until doing A RESTART OF THE SERVER I thought it was pihole. The two working together is very interesting. However I never did configure pihole when I set it up to pipe through bind9. I honestly count NOT find any use of bind in systemd or cron configs. I am sure there was something somewhere. Computers never just do what they feel like. I have uninstalled and purged the /etc/bind configs this morning. Will wait until this Sunday see if there is any more issues. I very strongly feel there won't be. I do have another micro server I had at my parents configured with bind9/named. I could disable on that and install pihole but then no good way to test it as I don't want to break dns. Fully aware two services can not share a port so I know that seems silly. From other devices they appear to have hit bind/named but from the server and the hosted docker containers they seems to use the pihole. Least that's how I think it looks like. |
5 tasks
|
No issues today. Nothing. All is working. So I feel the named / bond service that I discovered last week was my cause and issue. Do I checkout back to the main branch than the special branch you made? |
|
I'm glad we eventually solved your issue! The command you're looking for is |
Thank you for your help. |
|
Has a fix been merged? |
|
No, but I have seen no log lines from anyone besides @lionslair whose problem was solved. If you still experience this issue, you can surely reopen this ticket and we can go on if you have any of the log parts I've asked for further up here. |
|
For me, using the workaround described in #5608 (comment) did the trick to get a reliable, working system again. I eventually cleaned up the local DNS names i cluttered before, upgraded to the latest Pihole version, stopped using the workaround mentioned above and did not encounter the same problem again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Versions
Platform
Expected behavior
I shouldn't be required to restart DNS resolver all of the time
Actual behavior / bug
Hi 👋
I'm not completely sure whether here is the best place to put this but hope it gets some response. I've been running PiHole on my Raspberry Pi 4 4GB model for a few years now, always had the latest version of Pi Hole.
I've indentified some common issues that I can remedy by restarting DNS resolver, and also by rebooting the Pi (I've considered a timer)
Essentially, every few days when browsing the internet on devices the internet connection will appear to hang, the actual router and Pi both have a connection, it seems that clicking the "Restart DNS resolver" button will solve it temporarily and then I'll need to click it after a few more random days, and have done for months now.
In addition, it seems the Pi Hole just occassionally locks up entirely leading me to restarting the Pi, this solves 9/10 problems.
I'm just wondering, is the DNS resolver settings automatically restarting and i can change it's frequency, and also any tips for faster loading of pages
The text was updated successfully, but these errors were encountered: