I have Pi-hole up and running on q QNAP NAS via container station and can access the console fine. I have all my clients pointing to the pi-hole and seems to be working fine. I have one concern, below is the output of pi-hole starting:
**dnsmasq: failed to create listening socket for port 53: Address already in use **
**Stopping pihole-FTL **
**./finish: line 4: kill: (345) - No such process ** Starting pihole-FTL (no-daemon)
Should I be concerned with the "failed to create socket for port 53: Address already in use" even though all seems to be working fine?
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.1.25/24 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
-rw-r--r-- 1 root root 47 Sep 8 18:48 /etc/pihole/local.list
192.168.1.22 0077f5031d48
192.168.1.22 pi.hole
The query in the failed line should have resulted in a block and 0.0.0.0 return.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] jhhwo.googlevideo.com is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve jhhwo.googlevideo.com via Pi-hole (192.168.1.22)
[✓] doubleclick.com is 216.58.194.46 via a remote, public DNS server (8.8.8.8)
Have you changed user permissions? FTL user is typically pihole.
-rw-r--r-- 1 pihole pihole 47687 Sep 8 18:48 /var/log/pihole-FTL.log
-----head of pihole-FTL.log------
[2018-09-08 17:37:49.694] ########## FTL started! ##########
....
[2018-09-08 17:37:49.694] FTL user: root
[2018-09-08 17:37:49.694] WARNING: Starting pihole-FTL as user root is not recommended
...
The "ports in use" section of your debug log returned nothing. What is the output of:
Still trying to determine the one last error from the debug log even though pi-hole starts fine w/ out errors and filtering accordingly.
I am running pi-hole via container station on a QNAP NAS and pi-hole is configured as bridge w/ a static of 192.168.1.25. The QNAP IP is 192.168.1.22. I added 192.168.1.25 to the ServerIP variable but still receive the following error:
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.1.25/24 does not match the IP found in /etc/pihole/setupVars.conf
✗] Checking apt-get for upgraded packages
Kernel update detected. If the install fails, please reboot and try again
[i] Installer Dependency checks...
[i] Checking for apt-utils (will be installed)
[i] Checking for dialog (will be installed)
[i] Checking for debconf (will be installed)
[i] Checking for dhcpcd5 (will be installed)
[i] Checking for git (will be installed)
[i] Checking for iproute2 (will be installed)
[i] Checking for whiptail (will be installed)
[i] Using Google DNS servers
RTNETLINK answers: Operation not permitted
Just a note from my side with QNAP: The webinterface of Pi-Hole will show you a CPU utilization over 3.0 to 5.0 if the RAID gets scrubbed (http://docs.qnap.com/nas/QTS4.3.4/en/GUID-0BE980D3-1190-486B-A1E8-228DB71A9C93.html). I was wondering and researching until I saw that procedure. So you don‘t have to spent your time for researching
