I felt adventurous the other day and based on all the notices at the bottom of the page of new version of pihole and its components, I choose to update. I ran into issues similar to others, FTL issues. I followed steps listed in numerous threads here, none of which worked for me.
I got my backup of the pihole settings and decided to start all over. I reinstalled Raspbian Jessie, booted to it, uninstalled libreoffice, wolfram, applications like that which I don't use. Yes, I had desktop version local, so I decided to use it. I ran apt-get update, apt-upgrade, then did a "sudo curl -sSL https://install.pi-hole.net | bash"
I did not notice any alerts during the install.
both the jessie apt-get update/upgrade and the pihole install were performed on March 25. This was an updated Jessie OS.
I log into the webpage and now it is worse that before, not it says both "DNS service not running" and "FTL offline". Yesterday it only said FTL offline.
No amount of clicking "Enable" in the navigation bar helps.
So, I locate raspbian Jessie lite in the web, download, install to microsd. This time, no update/upgrade before installing pihole. pihole installs.
According to pihole web interface it again says both "DNS service not running" and "FTL offline".
sudo apt-get update fails, the OS can't resolve any hostname whatsoever.
I just don't recall that the installation of my original install of pihole as having any kind of problem whatsoever, IIRC it was soo easy. I just can't seem to find whatever I am missing to get this working. Pi is a Model 3 B, micro sd is 16GB.
I ran the pihole -d of the latest install attempt described above; jessie lite, no apt-get upgrade before pihole install, but it seems it can't upload as the pi can no longer resolve hostnames. So I'll paste below.
pi@raspberrypi:~ $ pihole -d
This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.
The intent of this script is to allow users to self-diagnose their installations. This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected. Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.
NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.
*** [ INITIALIZING ]
[i] 2018-03-25:22:59:02 debug log has been initialized.
*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...
*** [ DIAGNOSING ]: Core version
[i] Core: v3.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v3.3-0-g1e87850
*** [ DIAGNOSING ]: Web version
[i] Web: v3.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v3.3-0-ge48aa29
*** [ DIAGNOSING ]: FTL version
[✓] FTL: v3.0 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
*** [ DIAGNOSING ]: dnsmasq version
[i] 2.72
*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.35
*** [ DIAGNOSING ]: php version
[i] 5.6.33
*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 8 (jessie)
*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected
*** [ DIAGNOSING ]: Processor
/opt/pihole/piholeDebug.sh: line 474: $'[\E[32m✓\E[0m] \E[32marmv7l\E[0m': command not found
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.1.5/24 matches the IP found in /etc/pihole/setupVars.conf
[✓] IPv6 address(es) bound to the eth0 interface:
fe80::c14f:3ea1:8d07:d413 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
^ Please note that you may have more than one IP address listed.
As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.
The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.
[i] Default IPv4 gateway: 192.168.1.2
* Pinging 192.168.1.2...
[✓] Gateway responded.
*** [ DIAGNOSING ]: Ports in use
[22] is in use by sshd
[80] is in use by lighttpd
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
shuf: /etc/pihole/gravity.list: No such file or directory
dig: '' is not a legal name (unexpected end of input)
[✗] Failed to resolve via localhost (127.0.0.1)
dig: '' is not a legal name (unexpected end of input)
[✗] Failed to resolve via Pi-hole (192.168.1.5)
[✓] doubleclick.com is 172.217.4.46 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Pi-hole processes
[✗] dnsmasq daemon is failed
[✓] lighttpd daemon is active
[✗] pihole-FTL daemon is unknown
*** [ DIAGNOSING ]: Setup variables
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.1.5/24
IPV6_ADDRESS=
PIHOLE_DNS_1=208.67.222.222
PIHOLE_DNS_2=208.67.220.220
QUERY_LOGGING=true
INSTALL_WEB=true
LIGHTTPD_ENABLED=1
*** [ DIAGNOSING ]: Dashboard and block page
[✗] X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-type: text/html; charset=UTF-8
Date: Sun, 25 Mar 2018 22:59:06 GMT
Server: lighttpd/1.4.35
[✓] X-Pi-hole: The Pi-hole Web interface is working!
*** [ DIAGNOSING ]: Gravity list
ls: cannot access /etc/pihole/gravity.list: No such file or directory
head: cannot open ‘/etc/pihole/gravity.list’ for reading: No such file or directory
-----head of gravity.list------
tail: cannot open ‘/etc/pihole/gravity.list’ for reading: No such file or directory
-----tail of gravity.list------
*** [ DIAGNOSING ]: contents of /etc/pihole
-rw-r--r-- 1 root root 234 Mar 25 22:28 /etc/pihole/logrotate
/var/log/pihole.log {
su root root
daily
copytruncate
rotate 5
compress
delaycompress
notifempty
nomail
}
/var/log/pihole-FTL.log {
su root root
weekly
copytruncate
rotate 3
compress
delaycompress
notifempty
nomail
}
*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
-rw-r--r-- 1 root root 1522 Mar 25 22:34 /etc/dnsmasq.d/01-pihole.conf
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
localise-queries
no-resolv
cache-size=10000
log-queries=extra
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=208.67.222.222
server=208.67.220.220
interface=eth0
*** [ DIAGNOSING ]: contents of /etc/lighttpd
-rw-r--r-- 1 root root 3027 Mar 25 22:28 /etc/lighttpd/lighttpd.conf
server.modules = (
"mod_access",
"mod_accesslog",
"mod_auth",
"mod_expire",
"mod_compress",
"mod_redirect",
"mod_setenv",
"mod_rewrite"
)
server.document-root = "/var/www/html"
server.error-handler-404 = "pihole/index.php"
server.upload-dirs = ( "/var/cache/lighttpd/uploads" )
server.errorlog = "/var/log/lighttpd/error.log"
server.pid-file = "/var/run/lighttpd.pid"
server.username = "www-data"
server.groupname = "www-data"
server.port = 80
accesslog.filename = "/var/log/lighttpd/access.log"
accesslog.format = "%{%s}t|%V|%r|%s|%b"
index-file.names = ( "index.php", "index.html", "index.lighttpd.html" )
url.access-deny = ( "~", ".inc", ".md", ".yml", ".ini" )
static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
compress.cache-dir = "/var/cache/lighttpd/compress/"
compress.filetype = ( "application/javascript", "text/css", "text/html", "text/plain" )
include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
include_shell "/usr/share/lighttpd/create-mime.assign.pl"
include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include \"%p\"
' 2>/dev/null"
$HTTP["url"] =~ "^/admin/" {
setenv.add-response-header = (
"X-Pi-hole" => "The Pi-hole Web interface is working!",
"X-Frame-Options" => "DENY"
)
$HTTP["url"] =~ ".ttf$" {
setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
}
}
$HTTP["url"] =~ "^/admin/\.(.*)" {
url.access-deny = ("")
}
include_shell "cat external.conf 2>/dev/null"
*** [ DIAGNOSING ]: contents of /etc/cron.d
-rw-r--r-- 1 root root 1496 Mar 25 22:28 /etc/cron.d/pihole
34 4 * * 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity
00 00 * * * root PATH="$PATH:/usr/local/bin/" pihole flush once quiet
@reboot root /usr/sbin/logrotate /etc/pihole/logrotate
*/10 * * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker local
57 13 * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
@reboot root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot
*** [ DIAGNOSING ]: contents of /var/log/lighttpd
-rw-r--r-- 1 www-data www-data 516 Mar 25 22:34 /var/log/lighttpd/error.log
2018-03-25 22:28:35: (log.c.164) server started
2018-03-25 22:30:33: (server.c.1558) server stopped by UID = 0 PID = 1
2018-03-25 22:30:40: (log.c.164) server started
2018-03-25 22:31:56: (mod_fastcgi.c.2702) FastCGI-stderr: PHP Warning: unlink(../custom_disable_timer): No such file or directory in /var/www/html/admin/api.php on line 47
2018-03-25 22:33:59: (mod_fastcgi.c.2702) FastCGI-stderr: PHP Warning: unlink(../custom_disable_timer): No such file or directory in /var/www/html/admin/api.php on line 47
*** [ DIAGNOSING ]: contents of /var/log
*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 dnsmasq root 0 Mar 25 22:28 /var/log/pihole.log
-----head of pihole.log------
********************************************
********************************************
[✓] ** FINISHED DEBUGGING! **
* The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
* For more information, see: https://pi-hole.net/2016/11/07/crack-our-medical-tricorder-win-a-raspberry-pi-3/
* If available, we'll use openssl to upload the log, otherwise it will fall back to netcat.
[?] Would you like to upload the log? [y/N] y
* Using openssl for transmission.
[✗] There was an error uploading your debug log.
* Please try again or contact the Pi-hole team for assistance.
* A local copy of the debug log can be found at: /var/log/pihole_debug-sanitized.log
pi@raspberrypi:~ $
