Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 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-01-21:17:37:45 debug log has been initialized.
- *** [ INITIALIZING ] Sourcing setup variables
- [i] Sourcing /etc/pihole/setupVars.conf...
- *** [ DIAGNOSING ]: Core version
- [i] Core: v4.1.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
- [i] Branch: master
- [i] Commit: v4.1.1-0-g8d85d46
- *** [ DIAGNOSING ]: Web version
- [i] Web: v4.1.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
- [i] Branch: master
- [i] Commit: v4.1.1-0-gde7aa5a
- *** [ DIAGNOSING ]: FTL version
- [✓] FTL: v4.1.2
- *** [ DIAGNOSING ]: lighttpd version
- [i] 1.4.45
- *** [ DIAGNOSING ]: php version
- [i] 7.0.33
- *** [ DIAGNOSING ]: Operating system
- [✓] Raspbian GNU/Linux 9 (stretch)
- *** [ DIAGNOSING ]: SELinux
- [i] SELinux not detected
- *** [ DIAGNOSING ]: Processor
- [✓] armv6l
- *** [ DIAGNOSING ]: Networking
- [✓] IPv4 address(es) bound to the eth0 interface:
- 192.168.1.4/24 matches the IP found in /etc/pihole/setupVars.conf
- [✓] IPv6 address(es) bound to the eth0 interface:
- fe80::8b40:34c7:37de:dfd4 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)
- [*:80] is in use by lighttpd
- [*:80] is in use by lighttpd
- [*: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
- [[::1]:4711] is in use by pihole-FTL
- *** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
- [✓] ad255.hpg.com.br is 0.0.0.0 via localhost (127.0.0.1)
- [✓] ad255.hpg.com.br is 0.0.0.0 via Pi-hole (192.168.1.4)
- [✓] doubleclick.com is 216.58.210.14 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=eth0
- IPV4_ADDRESS=192.168.1.4/24
- IPV6_ADDRESS=
- PIHOLE_DNS_1=8.8.8.8
- PIHOLE_DNS_2=8.8.4.4
- QUERY_LOGGING=false
- INSTALL_WEB_SERVER=true
- INSTALL_WEB_INTERFACE=true
- LIGHTTPD_ENABLED=true
- DHCP_ACTIVE=true
- DHCP_START=192.168.1.2
- DHCP_END=192.168.1.199
- DHCP_ROUTER=192.168.1.1
- DHCP_LEASETIME=0
- PIHOLE_DOMAIN=lan
- DHCP_IPv6=false
- BLOCKING_ENABLED=true
- *** [ 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 2635660 Jan 20 03:45 /etc/pihole/gravity.list
- -----head of gravity.list------
- 0.0.0.0
- 0.r.msn.com
- 0.start.bz
- 000.0x1f4b0.com
- -----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 Jan 6 13:01 /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 44 Jan 20 03:45 /etc/pihole/local.list
- 192.168.1.4 raspberrypi
- 192.168.1.4 pi.hole
- -rw-r--r-- 1 root root 234 Jan 6 13:06 /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 1414 Jan 7 17:52 /etc/dnsmasq.d/01-pihole.conf
- addn-hosts=/etc/pihole/gravity.list
- addn-hosts=/etc/pihole/black.list
- addn-hosts=/etc/pihole/local.list
- user=pihole
- group=pihole
- localise-queries
- no-resolv
- cache-size=10000
- log-facility=/var/log/pihole.log
- local-ttl=2
- log-async
- server=8.8.8.8
- server=8.8.4.4
- interface=eth0
- -rw-r--r-- 1 root root 486 Jan 6 14:46 /etc/dnsmasq.d/02-pihole-dhcp.conf
- dhcp-authoritative
- dhcp-range=192.168.1.2,192.168.1.199,infinite
- dhcp-option=option:router,192.168.1.1
- dhcp-leasefile=/etc/pihole/dhcp.leases
- domain=lan
- *** [ DIAGNOSING ]: contents of /etc/lighttpd
- -rw-r--r-- 1 root root 3102 Jan 6 13:06 /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 Jan 6 13:06 /etc/cron.d/pihole
- 45 3 * * 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
- 16 14 * * * 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 73 Jan 21 06:25 /var/log/lighttpd/error.log
- 2019-01-21 06:25:07: (server.c.1534) logfiles cycled UID = 0 PID = 6282
- *** [ DIAGNOSING ]: contents of /var/log
- -rw-r--r-- 1 pihole pihole 0 Jan 21 00:00 /var/log/pihole-FTL.log
- -----head of pihole-FTL.log------
- -----tail of pihole-FTL.log------
- *** [ DIAGNOSING ]: Locale
- LANG=
- *** [ DIAGNOSING ]: Pi-hole log
- -rw-r--r-- 1 pihole pihole 14805 Jan 21 17:36 /var/log/pihole.log
- -----head of pihole.log------
- Jan 21 00:30:12 dnsmasq-dhcp[581]: DHCPDISCOVER(eth0) dc:68:eb:b3:75:ea
- Jan 21 00:30:12 dnsmasq-dhcp[581]: DHCPOFFER(eth0) 192.168.1.175 dc:68:eb:b3:75:ea
- Jan 21 00:30:12 dnsmasq-dhcp[581]: DHCPREQUEST(eth0) 192.168.1.175 dc:68:eb:b3:75:ea
- Jan 21 00:30:12 dnsmasq-dhcp[581]: DHCPACK(eth0) 192.168.1.175 dc:68:eb:b3:75:ea
- Jan 21 00:48:17 dnsmasq-dhcp[581]: DHCPREQUEST(eth0) 192.168.1.3 70:3e:ac:94:83:69
- Jan 21 00:48:17 dnsmasq-dhcp[581]: DHCPACK(eth0) 192.168.1.3 70:3e:ac:94:83:69 johnnysiPhone8
- Jan 21 01:00:28 dnsmasq-dhcp[581]: DHCPDISCOVER(eth0) dc:68:eb:b3:75:ea
- Jan 21 01:00:28 dnsmasq-dhcp[581]: DHCPOFFER(eth0) 192.168.1.175 dc:68:eb:b3:75:ea
- Jan 21 01:00:28 dnsmasq-dhcp[581]: DHCPREQUEST(eth0) 192.168.1.175 dc:68:eb:b3:75:ea
- Jan 21 01:00:28 dnsmasq-dhcp[581]: DHCPACK(eth0) 192.168.1.175 dc:68:eb:b3:75:ea
- Jan 21 01:30:44 dnsmasq-dhcp[581]: DHCPDISCOVER(eth0) dc:68:eb:b3:75:ea
- Jan 21 01:30:44 dnsmasq-dhcp[581]: DHCPOFFER(eth0) 192.168.1.175 dc:68:eb:b3:75:ea
- Jan 21 01:30:44 dnsmasq-dhcp[581]: DHCPREQUEST(eth0) 192.168.1.175 dc:68:eb:b3:75:ea
- Jan 21 01:30:44 dnsmasq-dhcp[581]: DHCPACK(eth0) 192.168.1.175 dc:68:eb:b3:75:ea
- Jan 21 02:01:00 dnsmasq-dhcp[581]: DHCPDISCOVER(eth0) dc:68:eb:b3:75:ea
- Jan 21 02:01:00 dnsmasq-dhcp[581]: DHCPOFFER(eth0) 192.168.1.175 dc:68:eb:b3:75:ea
- Jan 21 02:01:00 dnsmasq-dhcp[581]: DHCPREQUEST(eth0) 192.168.1.175 dc:68:eb:b3:75:ea
- Jan 21 02:01:00 dnsmasq-dhcp[581]: DHCPACK(eth0) 192.168.1.175 dc:68:eb:b3:75:ea
- Jan 21 02:07:09 dnsmasq-dhcp[581]: DHCPREQUEST(eth0) 192.168.1.3 70:3e:ac:94:83:69
- Jan 21 02:07:09 dnsmasq-dhcp[581]: DHCPACK(eth0) 192.168.1.3 70:3e:ac:94:83:69 johnnysiPhone8
- ********************************************
- ********************************************
- [✓] ** 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 openssl for transmission.
- ***********************************
- ***********************************
- [✓] Your debug token is: afrwz19l00
- ***********************************
- ***********************************
- * Provide the token above to the Pi-hole team for assistance at
- * https://discourse.pi-hole.net
- * Your log will self-destruct on our server after 48 hours.
- * A local copy of the debug log can be found at: /var/log/pihole_debug-sanitized.log
- Pi-hole Version v4.1.1 Web Interface Version v4.1.1 FTL Version v4.1.2 Donate if you found this useful.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement