Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.
I have a standard install of Pihole updated to the latest version
Earlier today, I updated my RPi to bullseye following the instructions at Raspberry Pi Documentation - Raspberry Pi OS
I noted a few errors when attempting to update GCC 8 and libGCC 8 but was able to resolve those issues by manually updating those libraries. A few other prompts on retaining existing versions of lighttpd.conf and another conf that I don't remember the name of right now.
Post the OS upgrade, I rebooted the RPi and then upgraded Pihole to the latest version using pihole -up command
Ever since, Pihole has stopped working. I'm consistently receiving the message FTL was not started and the DNSresolver is not listening. I've run pihole -r and attempting both repair and reconfiguration steps but neither seems to have resolved the issue.
Exploring more on this, I came across the following threads:
and
The first does not apply directly to me and the 2nd looks like it. But even in the Raspbian forums, I was unable to find any way to fix the blocking of port 53 by connmand.
How do I fix this? I'd prefer not to perform a reset of the RPi OS and Pihole.
*** [ DIAGNOSING ]: Ports in use
[53] is in use by connmand (https://docs.pi-hole.net/main/prerequisites/#ports)
[53] is in use by connmand (https://docs.pi-hole.net/main/prerequisites/#ports)
Port 53 is in use by connmand but required by Pi-hole.
Yes. How do I fix this? I'm not familiar with this service and I've not installed or enabled it. This appears to have happened automatically as a result of upgrading the OS
pi@raspberrypi:~ $ sudo systemctl disable connman.service
Synchronizing state of connman.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable connman
Removed /etc/systemd/system/multi-user.target.wants/connman.service.
pi@raspberrypi:~ $ sudo service pihole-FTL start
pi@raspberrypi:~ $ sudo service pihole-FTL status
â—Ź pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: active (exited) since Sun 2021-10-24 16:48:59 IST; 30min ago
Docs: man:systemd-sysv-generator(8)
Tasks: 0 (limit: 4915)
CPU: 0
CGroup: /system.slice/pihole-FTL.service
Oct 24 16:48:29 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
Oct 24 16:48:29 raspberrypi pihole-FTL[1680]: Not running
Oct 24 16:48:30 raspberrypi su[1692]: (to pihole) root on none
Oct 24 16:48:30 raspberrypi su[1692]: pam_unix(su:session): session opened for user pihole(uid=999) by (uid=0)
Oct 24 16:48:59 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
pi@raspberrypi:~ $
Running this command killed all the network connections (specifically, also the ethernet connection which is the only connection channel to the Pi). I don't think this is usable as is
If you are running a local DNS server, it will likely have problems binding to port 53 (TCP and/or UDP) after installing Connman. This is because Connman includes its own DNS proxy which also tries to bind to those ports. If you see log messages from BIND or dnsmasq like
named[529]: could not listen on UDP socket: address in use
this could be the problem. To verify which application is listening on the ports, you can execute ss -tulpn as root.
To fix this connmand can be started with the options -r or --nodnsproxy by overriding the systemd service file. Create the folder /etc/systemd/system/connman.service.d/ and add the file disable_dns_proxy.conf :
