i've been running 3.2.1 for a while now and haven't updated to 3.3 because of dnsmasq since i'm using Jessie Lite as described in blog post below.
When checking my dnsmasq version it shows i have 2.76, assume I'm good to go?
https://pi-hole.net/2018/02/14/pi-hole-v3-3-released-its-extra-special/
If you have v2.76 installed then you should be fine with 3.3. That is the only issue that is outstanding for v3.3.
yep, I see 2.76 when running dnsmasq -v, have a script that keeps it up to date.
Do you think its better to update to Strech?
well that didn't work.
✓] Creating directory for blocking page, and copying files
[✗] Backing up index.lighttpd.html
No default index.lighttpd.html file found... not backing up
[✓] Installing sudoer file
[✓] Installing latest Cron script
[✓] Installing latest logrotate script
[i] FTL Checks...
[✓] Detected ARM-hf architecture (armv6 or lower) Using ARM binary
[i] Checking for existing FTL binary...
[✗] Downloading and Installing FTL
Error: Unable to get latest release location from GitHub
[✗] FTL Engine not installed.
[i] Restarting services...
[i] Starting dnsmasq service...pi@pihole:~ $ ^C
pi@pihole:~ $ pihole -up
[i] Checking for updates...
fatal: unable to access 'https://github.com/pi-hole/pi-hole.git/': Could not resolve host: github.com
[i] Pi-hole Core: up to date
[i] FTL: update available
[i] FTL out of date
[i] FTL Checks...
[✓] Detected ARM-hf architecture (armv6 or lower) Using ARM binary
[i] Checking for existing FTL binary...
[✗] Downloading and Installing FTL
Error: Unable to get latest release location from GitH
Check /etc/resolv.conf
and make sure it's not set to 127.0.0.1
, try setting it temporarily to 8.8.8.8
or another public DNS server and then run the update again.
But given the options I would suggest updating to Stretch if it's possible.
i have to type sudo dnsmasq each time the rpi reboots, after that everything works.
seems dnsmasq is messed up
pi@pihole:~ $ systemctl status dnsmasq
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled)
Drop-In: /run/systemd/generator/dnsmasq.service.d
└─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
Active: failed (Result: exit-code) since Sat 2018-07-14 21:17:16 EDT; 12min ago
Process: 574 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=1/FAILURE)
Process: 549 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS)
pi@pihole:~ $ 8.1.3)
upgraded to stretch and ran pihole -r which has fixed dnsmasq not starting on startup.
1 Like