Please follow the below template, it will help us to help you!
Expected Behaviour:
pihole-FTL should work without any interruptions
Actual Behaviour:
pihole-FTL stops working every few days
Debug Token:
https://tricorder.pi-hole.net/e3ztalkqoa
Hello everyone!
So my my pihole on my Raspberry pi 3b+ stops working every few days, maybe weeks. I'm always getting the same error message: "dnsmasq: failed to create listening socket for port 53: Address already in use". As far as I know this problem only started to appear after following the guide on how to "Configuring DNS-Over-HTTPS on Pi-hole". Stopping and then restarting the pihole-FTL service fixes this, but as I said only for a few days.
pihole-FTL status:
> root@DietPi:~# sudo service pihole-FTL status
> ● pihole-FTL.service - LSB: pihole-FTL daemon
> Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
> Active: active (exited) since Thu 2019-08-08 00:17:03 BST; 15h ago
> Docs: man:systemd-sysv-generator(8)
> Process: 4948 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
> Process: 4985 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
>
> Aug 08 00:17:03 DietPi systemd[1]: Starting LSB: pihole-FTL daemon...
> Aug 08 00:17:03 DietPi pihole-FTL[4985]: Not running
> Aug 08 00:17:03 DietPi su[5018]: Successful su for pihole by root
> Aug 08 00:17:03 DietPi su[5018]: + ??? root:pihole
> Aug 08 00:17:03 DietPi su[5018]: pam_unix(su:session): session opened for user pihole by (uid=0)
> Aug 08 00:17:03 DietPi pihole-FTL[4985]: dnsmasq: failed to create listening socket for port 53: Address already in use
> Aug 08 00:17:03 DietPi dnsmasq[5024]: failed to create listening socket for port 53: Address already in use
> Aug 08 00:17:03 DietPi dnsmasq[5024]: FAILED to start up
> Aug 08 00:17:03 DietPi su[5018]: pam_unix(su:session): session closed for user pihole
> Aug 08 00:17:03 DietPi systemd[1]: Started LSB: pihole-FTL daemon.
Ports used while pihole-FTL is working:
> root@DietPi:~# netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471 \|:5053'
> Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
> tcp 0 0 127.0.0.1:5053 0.0.0.0:* LISTEN 596/cloudflared
> tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 883/lighttpd
> tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 15610/pihole-FTL
> tcp6 0 0 :::80 :::* LISTEN 883/lighttpd
> tcp6 0 0 :::53 :::* LISTEN 15610/pihole-FTL
> udp 0 0 127.0.0.1:5053 0.0.0.0:* 596/cloudflared
> udp 0 0 0.0.0.0:53 0.0.0.0:* 15610/pihole-FTL
> udp6 0 0 :::53 :::* 15610/pihole-FTL
Ports used when pihole-FTL stopped working:
> root@DietPi:~# netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471 \|:5053'
> Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
> tcp 0 0 127.0.0.1:5053 0.0.0.0:* LISTEN 596/cloudflared
> tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 883/lighttpd
> tcp6 0 0 :::80 :::* LISTEN 883/lighttpd
> udp 0 0 127.0.0.1:5053 0.0.0.0:* 596/cloudflared
Anyone got an idea why this is happening, and more importantly how to fix this?