So I thought I'd set up pihole on a beaglebone with the latest image
Installed it several times now (including wiping the image clean and starting again from scratch), but no matter what I do I just cannot get the FTL service to run properly at boot.
I can fix it manually though:
chown -R pihole:pihole /var/run/dnsmasq
touch /var/run/dnsmasq.leases
chown pihole:pihole dnsmasq.leases
systemctl restart pihole-FTL
But I shouldn't need to do this every time - so what's wrong?
After boot:
systemctl status pihole-FTL returns:
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Fri 2018-11-16 10:45:00 AWST; 8min ago
Docs: man:systemd-sysv-generator(8)
Process: 1002 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/pihole-FTL.service
Nov 16 10:44:42 beaglebone systemd[1]: Starting LSB: pihole-FTL daemon...
Nov 16 10:44:43 beaglebone pihole-FTL[1002]: Not running
Nov 16 10:44:44 beaglebone pihole-FTL[1002]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
Nov 16 10:44:59 beaglebone su[1478]: Successful su for pihole by root
Nov 16 10:44:59 beaglebone su[1478]: + ??? root:pihole
Nov 16 10:44:59 beaglebone su[1478]: pam_unix(su:session): session opened for user pihole by (uid=0)
Nov 16 10:45:00 beaglebone pihole-FTL[1002]: dnsmasq: cannot open or create lease file /var/run/dnsmasq.leases: Permission denied
Nov 16 10:45:00 beaglebone systemd[1]: Started LSB: pihole-FTL daemon.
Debug Token:
5gb7b1fq1w