Hello good people -
I was excited to see that Pi-Hole had been updated such that the latest version could be installed again, where previously a DNSmasq conflict prevented it. Unfortunately, when I installed it both DNSmasq and Pi-Hole services died.
Filed an issue several weeks ago but thus far no one appears to be viewing them.
opened 06:45PM - 25 Sep 21 UTC
Several hours after installing Pi-hole (latest available, FTLDNS), my yunohost (… 4.2.8.3 (stable) running on rpi4 generated mail quoted below:
> =================================
> Services status check (services)
> =================================
>
> [ERROR] Service dnsmasq is exited :(
> - You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart dnsmasq' and 'yunohost service log dnsmasq').
>
> [ERROR] Service pihole-FTL is exited :(
> - You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart pihole-FTL' and 'yunohost service log pihole-FTL').
Status in the admin panel confirms that Yunohost sees both services disabled. From command line:
> admin@net:~ $ sudo yunohost service log dnsmasq
> journalctl:
> - -- Logs begin at Mon 2021-09-20 10:05:21 BST, end at Sat 2021-09-25 19:27:13 BST. --
> - Sep 25 16:17:40 systemd[1]: Stopping dnsmasq - A lightweight DHCP and caching DNS server...
> - Sep 25 16:17:41 dnsmasq[1228]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf
> - Sep 25 16:17:41 dnsmasq[25851]: exiting on receipt of SIGTERM
> - Sep 25 16:17:41 systemd[1]: dnsmasq.service: Succeeded.
> - Sep 25 16:17:41 systemd[1]: Stopped dnsmasq - A lightweight DHCP and caching DNS server.
> admin@net:~ $ sudo service dnsmasq status
> ● pihole-FTL.service - LSB: pihole-FTL daemon
> Loaded: loaded (/etc/init.d/pihole-FTL; generated)
> Active: active (exited) since Sat 2021-09-25 16:18:15 BST; 3h 9min ago
> Docs: man:systemd-sysv-generator(8)
> Process: 3608 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
<img width="501" alt="Screenshot 2021-09-25 at 20 42 22" src="https://user-images.githubusercontent.com/1538027/134782874-d38f5828-cd31-4a56-b2a8-6cf1cde83e1c.png">
<img width="330" alt="Screenshot 2021-09-25 at 20 42 33" src="https://user-images.githubusercontent.com/1538027/134782876-fa428998-f753-4a89-b9f7-5401aaa8d55e.png">
Thanks for all you are doing to make yunohost freely available. It's important work, and your generosity is very much appreciated.
My question is: Should I do something to downgrade the status of the pi-hole application package (or add a “broken” tag?) in the application directory? From what I can tell the issue should affect everyone who uses the FTLDNS configuration option, to have the latest version installed.
Many thanks to everyone in the community for all their contributions.