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] 2019-05-22:16:00:48 debug log has been initialized. *** [ INITIALIZING ] Sourcing setup variables [i] Sourcing /etc/pihole/setupVars.conf... *** [ DIAGNOSING ]: Core version [i] Core: v4.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249) [i] Branch: master [i] Commit: v4.3-0-g1d43c0a *** [ DIAGNOSING ]: Web version [i] Web: v4.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249) [i] Branch: master [i] Commit: v4.3-0-g44aff72 *** [ DIAGNOSING ]: FTL version [✓] FTL: v4.3 *** [ DIAGNOSING ]: lighttpd version [i] 1.4.45 *** [ DIAGNOSING ]: php version [i] 7.0.33 *** [ DIAGNOSING ]: Operating system [✓] Debian GNU/Linux 9 (stretch) *** [ DIAGNOSING ]: SELinux [i] SELinux not detected *** [ DIAGNOSING ]: Processor [✓] armv7l *** [ DIAGNOSING ]: Networking [✓] IPv4 address(es) bound to the wlan0 interface: 192.168.1.43/24 matches the IP found in /etc/pihole/setupVars.conf [✓] IPv6 address(es) bound to the wlan0 interface: fe80::6c00:cdc:7b94:a1ec 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.1 * Pinging 192.168.1.1... [✓] Gateway responded. *** [ DIAGNOSING ]: Ports in use *:22 sshd (IPv4) *:22 sshd (IPv6) [*:53] is in use by pihole-FTL [*:53] is in use by pihole-FTL [127.0.0.1:4711] is in use by pihole-FTL [*:80] is in use by lighttpd [*:80] is in use by lighttpd *** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain [✓] adluminious.go2affise.com is 0.0.0.0 via localhost (127.0.0.1) [✓] adluminious.go2affise.com is 0.0.0.0 via Pi-hole (192.168.1.43) [✓] doubleclick.com is 216.58.205.110 via a remote, public DNS server (8.8.8.8) *** [ DIAGNOSING ]: Pi-hole processes [✓] lighttpd daemon is active [✓] pihole-FTL daemon is active *** [ DIAGNOSING ]: Setup variables PIHOLE_INTERFACE=wlan0 IPV4_ADDRESS=192.168.1.43/24 IPV6_ADDRESS= QUERY_LOGGING=true INSTALL_WEB_SERVER=true INSTALL_WEB_INTERFACE=true LIGHTTPD_ENABLED=true BLOCKING_ENABLED=true DNSMASQ_LISTENING=single PIHOLE_DNS_1=8.8.4.4 PIHOLE_DNS_2=1.1.1.1 DNS_FQDN_REQUIRED=true DNS_BOGUS_PRIV=true DNSSEC=false CONDITIONAL_FORWARDING=false *** [ DIAGNOSING ]: Dashboard and block page [✓] Block page X-Header: X-Pi-hole: A black hole for Internet advertisements. [✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working! *** [ DIAGNOSING ]: Gravity list -rw-r--r-- 1 root root 2646926 May 22 15:24 /etc/pihole/gravity.list -----head of gravity.list------ 0.0.0.0 0.nextyourcontent.com 0.r.msn.com 0.start.bz -----tail of gravity.list------ zzz.clickbank.net zzzezeroe.fr zzzpooeaz-france.com zzzrtrcm2.com *** [ DIAGNOSING ]: contents of /etc/pihole -rw-r--r-- 1 root root 381 May 21 22:38 /etc/pihole/adlists.list https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts https://mirror1.malwaredomains.com/files/justdomains http://sysctl.org/cameleon/hosts https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt https://hosts-file.net/ad_servers.txt -rw-r--r-- 1 root root 47 May 22 15:24 /etc/pihole/local.list 192.168.1.43 orangepilite 192.168.1.43 pi.hole -rw-r--r-- 1 root root 234 May 21 22:40 /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 1612 May 22 15:21 /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 log-facility=/var/log/pihole.log local-ttl=2 log-async dhcp-name-match=set:wpad-ignore,wpad dhcp-ignore-names=tag:wpad-ignore server=8.8.4.4 server=1.1.1.1 domain-needed bogus-priv interface=wlan0 *** [ DIAGNOSING ]: contents of /etc/lighttpd -rw-r--r-- 1 root root 3102 May 21 22:40 /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 1704 May 21 22:40 /etc/cron.d/pihole 23 4 * * 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity >/var/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log 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 58 18 * * * 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 -rwxr-xr-x 1 www-data www-data 7479 May 22 15:17 /var/log/lighttpd/error.log 2019-05-21 23:11:44: (log.c.217) server started 2019-05-21 23:12:43: (server.c.1828) server stopped by UID = 0 PID = 1 2019-05-21 23:12:51: (log.c.217) server started 2019-05-22 03:00:01: (server.c.1828) server stopped by UID = 0 PID = 1 2019-05-22 03:00:17: (log.c.217) server started 2019-05-22 03:01:01: (server.c.1828) server stopped by UID = 0 PID = 1 2019-05-22 03:01:17: (log.c.217) server started 2019-05-22 03:02:01: (server.c.1828) server stopped by UID = 0 PID = 1 2019-05-22 03:02:16: (log.c.217) server started 2019-05-22 03:03:01: (server.c.1828) server stopped by UID = 0 PID = 1 2019-05-22 03:03:13: (log.c.217) server started 2019-05-22 03:04:01: (server.c.1828) server stopped by UID = 0 PID = 1 2019-05-22 03:04:12: (log.c.217) server started 2019-05-22 03:05:01: (server.c.1828) server stopped by UID = 0 PID = 1 2019-05-22 03:05:10: (log.c.217) server started 2019-05-22 03:06:00: (server.c.1828) server stopped by UID = 0 PID = 1 2019-05-22 03:06:10: (log.c.217) server started 2019-05-22 03:07:00: (server.c.1828) server stopped by UID = 0 PID = 1 2019-05-22 03:07:10: (log.c.217) server started 2019-05-22 03:08:01: (server.c.1828) server stopped by UID = 0 PID = 1 2019-05-22 03:08:10: (log.c.217) server started 2019-05-22 03:09:01: (server.c.1828) server stopped by UID = 0 PID = 1 2019-05-22 03:09:10: (log.c.217) server started 2019-05-22 03:10:00: (server.c.1828) server stopped by UID = 0 PID = 1 2019-05-22 03:10:10: (log.c.217) server started *** [ DIAGNOSING ]: contents of /var/log -rw-r--r-- 1 pihole pihole 261032 May 22 15:17 /var/log/pihole-FTL.log -----head of pihole-FTL.log------ [2019-05-22 00:52:10.891 9453] Resizing "/FTL-strings" from 4096 to 8192 [2019-05-22 01:23:59.809 9453] Resizing "/FTL-strings" from 8192 to 12288 [2019-05-22 01:39:43.760 9453] Resizing "/FTL-strings" from 12288 to 16384 [2019-05-22 03:00:01.886 9453] Shutting down... [2019-05-22 03:00:02.080 9453] Finished final database update [2019-05-22 03:00:02.081 9453] ########## FTL terminated after 13058106.0 ms! ########## [2019-05-22 03:00:17.279 996] Using log file /var/log/pihole-FTL.log [2019-05-22 03:00:17.280 996] ########## FTL started! ########## [2019-05-22 03:00:17.280 996] FTL branch: master [2019-05-22 03:00:17.280 996] FTL version: v4.3 [2019-05-22 03:00:17.280 996] FTL commit: 9e8273b [2019-05-22 03:00:17.280 996] FTL date: 2019-05-18 16:00:39 -0400 [2019-05-22 03:00:17.280 996] FTL user: pihole [2019-05-22 03:00:17.280 996] Starting config file parsing (/etc/pihole/pihole-FTL.conf) [2019-05-22 03:00:17.280 996] SOCKET_LISTENING: only local [2019-05-22 03:00:17.280 996] AAAA_QUERY_ANALYSIS: Show AAAA queries [2019-05-22 03:00:17.280 996] MAXDBDAYS: max age for stored queries is 365 days [2019-05-22 03:00:17.281 996] RESOLVE_IPV6: Resolve IPv6 addresses [2019-05-22 03:00:17.281 996] RESOLVE_IPV4: Resolve IPv4 addresses [2019-05-22 03:00:17.281 996] DBINTERVAL: saving to DB file every minute [2019-05-22 03:00:17.281 996] DBFILE: Using /etc/pihole/pihole-FTL.db [2019-05-22 03:00:17.281 996] MAXLOGAGE: Importing up to 24.0 hours of log data [2019-05-22 03:00:17.281 996] PRIVACYLEVEL: Set to 0 [2019-05-22 03:00:17.281 996] IGNORE_LOCALHOST: Show queries from localhost [2019-05-22 03:00:17.281 996] BLOCKINGMODE: Null IPs for blocked domains [2019-05-22 03:00:17.281 996] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries [2019-05-22 03:00:17.282 996] DBIMPORT: Importing history from database [2019-05-22 03:00:17.282 996] PIDFILE: Using /var/run/pihole-FTL.pid [2019-05-22 03:00:17.282 996] PORTFILE: Using /var/run/pihole-FTL.port [2019-05-22 03:00:17.282 996] SOCKETFILE: Using /var/run/pihole/FTL.sock [2019-05-22 03:00:17.282 996] WHITELISTFILE: Using /etc/pihole/whitelist.txt [2019-05-22 03:00:17.282 996] BLACKLISTFILE: Using /etc/pihole/black.list [2019-05-22 03:00:17.282 996] GRAVITYFILE: Using /etc/pihole/gravity.list [2019-05-22 03:00:17.282 996] REGEXLISTFILE: Using /etc/pihole/regex.list [2019-05-22 03:00:17.282 996] SETUPVARSFILE: Using /etc/pihole/setupVars.conf -----tail of pihole-FTL.log------ [2019-05-22 15:17:11.241 1009] PARSE_ARP_CACHE: Active [2019-05-22 15:17:11.241 1009] Finished config file parsing [2019-05-22 15:17:11.388 1009] SQLite3 message: recovered 2 pages from /etc/pihole/pihole-FTL.db-journal (539) [2019-05-22 15:17:11.403 1009] Database version is 3 [2019-05-22 15:17:11.403 1009] Database successfully initialized [2019-05-22 15:17:11.411 1009] New forward server: 8.8.4.4 (0/512) [2019-05-22 15:17:11.412 1009] New forward server: 8.8.8.8 (1/512) [2019-05-22 15:17:11.447 1009] Resizing "/FTL-strings" from 4096 to 8192 [2019-05-22 15:17:11.464 1009] Resizing "/FTL-strings" from 8192 to 12288 [2019-05-22 15:17:11.468 1009] Resizing "/FTL-strings" from 12288 to 16384 [2019-05-22 15:17:11.483 1009] Resizing "/FTL-queries" from 196608 to 393216 [2019-05-22 15:17:11.494 1009] Resizing "/FTL-strings" from 16384 to 20480 [2019-05-22 15:17:11.504 1009] Resizing "/FTL-strings" from 20480 to 24576 [2019-05-22 15:17:11.523 1009] Resizing "/FTL-strings" from 24576 to 28672 [2019-05-22 15:17:11.566 1009] Resizing "/FTL-strings" from 28672 to 32768 [2019-05-22 15:17:11.576 1009] Resizing "/FTL-queries" from 393216 to 589824 [2019-05-22 15:17:11.588 1009] Imported 8595 queries from the long-term database [2019-05-22 15:17:11.589 1009] -> Total DNS queries: 8595 [2019-05-22 15:17:11.589 1009] -> Cached DNS queries: 715 [2019-05-22 15:17:11.589 1009] -> Forwarded DNS queries: 6310 [2019-05-22 15:17:11.589 1009] -> Exactly blocked DNS queries: 1546 [2019-05-22 15:17:11.590 1009] -> Unknown DNS queries: 24 [2019-05-22 15:17:11.590 1009] -> Unique domains: 1036 [2019-05-22 15:17:11.590 1009] -> Unique clients: 7 [2019-05-22 15:17:11.590 1009] -> Known forward destinations: 2 [2019-05-22 15:17:11.590 1009] Successfully accessed setupVars.conf [2019-05-22 15:17:11.623 1048] PID of FTL process: 1048 [2019-05-22 15:17:11.623 1048] Listening on port 4711 for incoming IPv4 telnet connections [2019-05-22 15:17:11.624 1048] Listening on Unix socket [2019-05-22 15:17:11.625 1048] Received SIGHUP, reloading cache [2019-05-22 15:17:11.626 1048] Blocking status is enabled [2019-05-22 15:17:11.626 1048] INFO: No whitelist file found [2019-05-22 15:17:11.626 1048] Compiled 0 Regex filters and 0 whitelisted domains in 0.3 msec (0 errors) [2019-05-22 15:17:13.457 1048] /etc/pihole/gravity.list: parsed 113155 domains (took 1820.3 ms) [2019-05-22 15:17:16.193 1048] New forward server: 1.1.1.1 (2/512) *** [ DIAGNOSING ]: contents of /dev/shm -rw------- 1 pihole pihole 323584 May 22 15:17 /dev/shm/FTL-clients -rw------- 1 pihole pihole 108 May 22 15:17 /dev/shm/FTL-counters -rw------- 1 pihole pihole 65536 May 22 15:17 /dev/shm/FTL-domains -rw------- 1 pihole pihole 12288 May 22 15:17 /dev/shm/FTL-forwarded -rw------- 1 pihole pihole 28 May 22 15:17 /dev/shm/FTL-lock -rw------- 1 pihole pihole 53248 May 22 15:17 /dev/shm/FTL-overTime -rw------- 1 pihole pihole 589824 May 22 15:59 /dev/shm/FTL-queries -rw------- 1 pihole pihole 12 May 22 15:17 /dev/shm/FTL-settings -rw------- 1 pihole pihole 32768 May 22 15:17 /dev/shm/FTL-strings *** [ DIAGNOSING ]: Locale LANG= *** [ DIAGNOSING ]: Pi-hole log -rw-r--r-- 1 pihole pihole 1213061 May 22 16:01 /var/log/pihole.log -----head of pihole.log------ May 22 00:00:03 dnsmasq[9453]: query[A] 1.debian.pool.ntp.org from 192.168.1.43 May 22 00:00:03 dnsmasq[9453]: forwarded 1.debian.pool.ntp.org to 8.8.4.4 May 22 00:00:03 dnsmasq[9453]: forwarded 1.debian.pool.ntp.org to 8.8.8.8 May 22 00:00:03 dnsmasq[9453]: query[AAAA] 1.debian.pool.ntp.org from 192.168.1.43 May 22 00:00:03 dnsmasq[9453]: forwarded 1.debian.pool.ntp.org to 8.8.4.4 May 22 00:00:03 dnsmasq[9453]: forwarded 1.debian.pool.ntp.org to 8.8.8.8 May 22 00:00:05 dnsmasq[9453]: query[PTR] 79.1.168.192.in-addr.arpa from 192.168.1.43 May 22 00:00:05 dnsmasq[9453]: forwarded 79.1.168.192.in-addr.arpa to 8.8.4.4 May 22 00:00:05 dnsmasq[9453]: forwarded 79.1.168.192.in-addr.arpa to 8.8.8.8 May 22 00:00:08 dnsmasq[9453]: query[A] 1.debian.pool.ntp.org from 192.168.1.43 May 22 00:00:08 dnsmasq[9453]: forwarded 1.debian.pool.ntp.org to 8.8.4.4 May 22 00:00:08 dnsmasq[9453]: forwarded 1.debian.pool.ntp.org to 8.8.8.8 May 22 00:00:08 dnsmasq[9453]: query[AAAA] 1.debian.pool.ntp.org from 192.168.1.43 May 22 00:00:08 dnsmasq[9453]: forwarded 1.debian.pool.ntp.org to 8.8.4.4 May 22 00:00:08 dnsmasq[9453]: forwarded 1.debian.pool.ntp.org to 8.8.8.8 May 22 00:00:10 dnsmasq[9453]: query[PTR] 58.1.168.192.in-addr.arpa from 192.168.1.43 May 22 00:00:10 dnsmasq[9453]: forwarded 58.1.168.192.in-addr.arpa to 8.8.4.4 May 22 00:00:10 dnsmasq[9453]: forwarded 58.1.168.192.in-addr.arpa to 8.8.8.8 May 22 00:00:13 dnsmasq[9453]: query[A] 1.debian.pool.ntp.org.homenet.telecomitalia.it from 192.168.1.43 May 22 00:00:13 dnsmasq[9453]: forwarded 1.debian.pool.ntp.org.homenet.telecomitalia.it to 8.8.4.4 ******************************************** ******************************************** [✓] ** 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. [i] Debug script running in automated mode * Using curl 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.log