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] 2018-07-08:04:32:57 debug log has been initialized.
- *** [ INITIALIZING ] Sourcing setup variables
- [i] Sourcing /etc/pihole/setupVars.conf...
- *** [ DIAGNOSING ]: Core version
- [i] Core: v3.3.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
- [i] Branch: master
- [i] Commit: v3.3.1-0-gfbee18e
- *** [ 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
- *** [ DIAGNOSING ]: dnsmasq version
- [i] 2.76
- *** [ DIAGNOSING ]: lighttpd version
- [i] 1.4.45
- *** [ DIAGNOSING ]: php version
- [i] 7.0.30
- *** [ DIAGNOSING ]: Operating system
- [✓] Raspbian GNU/Linux 9 (stretch)
- *** [ DIAGNOSING ]: SELinux
- [i] SELinux not detected
- *** [ DIAGNOSING ]: Processor
- *** [ DIAGNOSING ]: Networking
- [✓] IPv4 address(es) bound to the eth0 interface:
- 192.168.0.116/24 matches the IP found in /etc/pihole/setupVars.conf
- [✓] IPv6 address(es) bound to the eth0 interface:
- 2601:883:8000:48f0:53cc:71f7:1902:eda matches the IP found in /etc/pihole/setupVars.conf
- fe80::6eec:9f24:16e8:47fb 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.0.1
- * Pinging 192.168.0.1...
- [✓] Gateway responded.
- [i] Default IPv6 gateway: fe80::b2b9:8aff:fed4:f01b
- * Pinging fe80::b2b9:8aff:fed4:f01b...
- [✓] Gateway responded.
- *** [ DIAGNOSING ]: Ports in use
- [22] is in use by sshd
- [53] is in use by dnsmasq
- [80] is in use by lighttpd
- [] is in use by
- [4711] is in use by pihole-FTL
- *** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
- [✓] sview.avenuea.com is 192.168.0.116 via localhost (127.0.0.1)
- [✓] sview.avenuea.com is 192.168.0.116 via Pi-hole (192.168.0.116)
- [✓] doubleclick.com is 172.217.3.78 via a remote, public DNS server (8.8.8.8)
- *** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
- [✓] hustler-life.com is 2601:883:8000:48f0:53cc:71f7:1902:eda via localhost (::1)
- [✓] hustler-life.com is 2601:883:8000:48f0:53cc:71f7:1902:eda via Pi-hole (2601:883:8000:48f0:53cc:71f7:1902:eda)
- [✓] doubleclick.com is 2607:f8b0:4008:811::200e via a remote, public DNS server (2001:4860:4860::8888)
- *** [ DIAGNOSING ]: Pi-hole processes
- [✓] dnsmasq daemon is active
- [✓] lighttpd daemon is active
- [✓] pihole-FTL daemon is active
- *** [ DIAGNOSING ]: Setup variables
- DNSMASQ_LISTENING=single
- PIHOLE_DNS_3=2001:4860:4860:0:0:0:0:8888
- PIHOLE_DNS_4=2001:4860:4860:0:0:0:0:8844
- DNS_FQDN_REQUIRED=true
- DNS_BOGUS_PRIV=true
- DNSSEC=false
- CONDITIONAL_FORWARDING=false
- DHCP_ACTIVE=true
- DHCP_START=192.168.0.117
- DHCP_END=192.168.0.254
- DHCP_ROUTER=192.168.0.1
- DHCP_LEASETIME=24
- PIHOLE_DOMAIN=lan
- DHCP_IPv6=true
- PIHOLE_INTERFACE=eth0
- IPV4_ADDRESS=192.168.0.116/24
- IPV6_ADDRESS=2601:883:8000:48f0:53cc:71f7:1902:eda
- PIHOLE_DNS_1=8.8.8.8
- PIHOLE_DNS_2=8.8.4.4
- QUERY_LOGGING=true
- INSTALL_WEB=true
- LIGHTTPD_ENABLED=1
- *** [ DIAGNOSING ]: Dashboard and block page
- [✓] X-Pi-hole: A black hole for Internet advertisements.
- [✓] X-Pi-hole: The Pi-hole Web interface is working!
- *** [ DIAGNOSING ]: Gravity list
- -rw-r--r-- 1 root root 12921244 Jul 8 04:31 /etc/pihole/gravity.list
- -----head of gravity.list------
- 192.168.0.116 0.0.0.0
- 2601:883:8000:48f0:53cc:71f7:1902:eda 0.0.0.0
- 192.168.0.116 0.r.msn.com
- 2601:883:8000:48f0:53cc:71f7:1902:eda 0.r.msn.com
- -----tail of gravity.list------
- 192.168.0.116 zzzpooeaz-france.com
- 2601:883:8000:48f0:53cc:71f7:1902:eda zzzpooeaz-france.com
- 192.168.0.116 zzzrtrcm2.com
- 2601:883:8000:48f0:53cc:71f7:1902:eda zzzrtrcm2.com
- *** [ DIAGNOSING ]: contents of /etc/pihole
- -rw-r--r-- 1 root root 1036 Jul 7 14: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
- https://wally3k.github.io/
- rcm-na.amazon-adsystem.com
- pagead2.googlesyndication.com
- r4---sn-vgqs7nez.googlevideo.com
- r4.sn-vgqs7nez.googlevideo.com
- www.youtube-nocookie.com
- i1.ytimg.com
- r17---sn-vgqsenes.googlevideo.com
- r2---sn-vgqs7n7k.googlevideo.com
- clients6.google.com
- r1---sn-vgqsen7z.googlevideo.com
- r1.sn-vgqsen7z.googlevideo.com
- r20---sn-vgqs7ne7.googlevideo.com
- r20.sn-vgqs7ne7.googlevideo.com
- -rw-r--r-- 1 root root 144 Jul 8 04:31 /etc/pihole/local.list
- 192.168.0.116 raspberrypi
- 2601:883:8000:48f0:53cc:71f7:1902:eda raspberrypi
- 192.168.0.116 pi.hole
- 2601:883:8000:48f0:53cc:71f7:1902:eda pi.hole
- -rw-r--r-- 1 root root 234 Jul 8 04:20 /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 1603 Jul 8 04:20 /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=8.8.8.8
- server=8.8.4.4
- server=2001:4860:4860:0:0:0:0:8888
- server=2001:4860:4860:0:0:0:0:8844
- domain-needed
- bogus-priv
- interface=eth0
- -rw-r--r-- 1 root root 618 Jul 8 04:20 /etc/dnsmasq.d/02-pihole-dhcp.conf
- dhcp-authoritative
- dhcp-range=192.168.0.117,192.168.0.254,24h
- dhcp-option=option:router,192.168.0.1
- dhcp-leasefile=/etc/pihole/dhcp.leases
- domain=lan
- dhcp-option=option6:dns-server,[::]
- dhcp-range=::100,::1ff,constructor:eth0,ra-names,slaac,24h
- ra-param=*,0,0
- *** [ DIAGNOSING ]: contents of /etc/lighttpd
- -rw-r--r-- 1 root root 3027 Jul 8 04:20 /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 Jul 8 04:20 /etc/cron.d/pihole
- 31 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
- 18 16 * * * 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 1569 Jul 8 04:20 /var/log/lighttpd/error.log
- 2018-07-07 04:32:00: (log.c.217) server started
- 2018-07-07 04:33:11: (server.c.1828) server stopped by UID = 0 PID = 1
- 2018-07-07 04:33:11: (log.c.217) server started
- 2018-07-07 04:33:11: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
- 2018-07-07 05:01:14: (log.c.217) server started
- 2018-07-07 05:01:14: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
- 2018-07-07 05:25:36: (server.c.1828) server stopped by UID = 0 PID = 1
- 2018-07-07 05:36:33: (log.c.217) server started
- 2018-07-07 05:36:33: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
- 2018-07-07 05:38:36: (server.c.1828) server stopped by UID = 0 PID = 1
- 2018-07-07 05:44:00: (log.c.217) server started
- 2018-07-07 05:44:00: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
- 2018-07-07 06:39:09: (server.c.1828) server stopped by UID = 0 PID = 1
- 2018-07-07 06:39:09: (log.c.217) server started
- 2018-07-07 06:39:09: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
- 2018-07-07 14:08:59: (server.c.1828) server stopped by UID = 0 PID = 1
- 2018-07-07 14:11:20: (log.c.217) server started
- 2018-07-07 14:11:20: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
- 2018-07-07 14:17:16: (log.c.217) server started
- 2018-07-07 14:17:16: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
- 2018-07-08 04:20:09: (server.c.1828) server stopped by UID = 0 PID = 1
- 2018-07-08 04:20:10: (log.c.217) server started
- 2018-07-08 04:20:10: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
- *** [ DIAGNOSING ]: contents of /var/log
- -rw-r--r-- 1 pihole pihole 11736 Jul 8 04:31 /var/log/pihole-FTL.log
- [2018-07-08 00:00:02.027] NOTICE: pihole.log has been flushed
- [2018-07-08 00:00:02.028] Resetting internal data structure
- [2018-07-08 00:00:02.028] Queries in memory before flushing: 18061
- [2018-07-08 00:00:02.029] FATAL: Trying to free NULL pointer in pihole_log_flushed() (flush.c:61)
- [2018-07-08 00:00:02.353] Gravity list entries: 132580
- [2018-07-08 00:00:02.353] No blacklist present
- [2018-07-08 00:00:02.353] No wildcard blocking list present
- [2018-07-08 00:00:02.354] Notice: Increasing queries struct size from 0 to 10000 (440.77 KB)
- [2018-07-08 00:00:02.354] Notice: Increasing domains struct size from 0 to 1000 (460.77 KB)
- [2018-07-08 00:00:02.354] Notice: Increasing clients struct size from 0 to 10 (460.93 KB)
- [2018-07-08 00:00:02.354] New client: 127.0.0.1 localhost (0/10)
- [2018-07-08 00:00:02.354] Notice: Increasing forwarded struct size from 0 to 4 (461.04 KB)
- [2018-07-08 00:00:02.401] New forward server: 8.8.4.4 google-public-dns-b.google.com (0/4)
- [2018-07-08 00:00:02.401] Notice: Increasing overTime struct size from 0 to 100 (465.08 KB)
- [2018-07-08 00:00:02.449] New forward server: 8.8.8.8 google-public-dns-a.google.com (1/4)
- [2018-07-08 00:00:02.494] New forward server: 208.67.220.220 resolver2.opendns.com (2/4)
- [2018-07-08 00:00:02.501] New client: 174.58.247.12 c-174-58-247-12.hsd1.fl.comcast.net (1/10)
- [2018-07-08 00:00:02.508] New client: 192.168.0.117 pavilion.lan (2/10)
- [2018-07-08 00:00:02.515] New client: 192.168.0.121 chromecast.lan (3/10)
- [2018-07-08 00:00:02.521] New client: 192.168.0.122 desktop-3cmd4t0.lan (4/10)
- [2018-07-08 00:00:02.528] New client: 192.168.0.124 ex6100v2.lan (5/10)
- [2018-07-08 00:00:02.535] New client: 192.168.0.126 android-2191b92f0672cd4.lan (6/10)
- [2018-07-08 00:00:02.542] New client: 192.168.0.116 raspberrypi (7/10)
- [2018-07-08 00:00:02.588] New forward server: 208.67.222.222 resolver1.opendns.com (3/4)
- [2018-07-08 00:00:02.588] Notice: Increasing forwarded struct size from 4 to 8 (467.31 KB)
- *** [ DIAGNOSING ]: Pi-hole log
- -rw-r--r-- 1 dnsmasq root 1214666 Jul 8 04:33 /var/log/pihole.log
- -----head of pihole.log------
- Jul 8 00:00:02 dnsmasq[524]: 2176 127.0.0.1/51925 query[PTR] 4.4.8.8.in-addr.arpa from 127.0.0.1
- Jul 8 00:00:02 dnsmasq[524]: 2176 127.0.0.1/51925 forwarded 4.4.8.8.in-addr.arpa to 2001:4860:4860::8844
- Jul 8 00:00:02 dnsmasq[524]: 2176 127.0.0.1/51925 forwarded 4.4.8.8.in-addr.arpa to 2001:4860:4860::8888
- Jul 8 00:00:02 dnsmasq[524]: 2176 127.0.0.1/51925 forwarded 4.4.8.8.in-addr.arpa to 8.8.4.4
- Jul 8 00:00:02 dnsmasq[524]: 2176 127.0.0.1/51925 forwarded 4.4.8.8.in-addr.arpa to 8.8.8.8
- Jul 8 00:00:02 dnsmasq[524]: 2176 127.0.0.1/51925 reply 8.8.4.4 is google-public-dns-b.google.com
- Jul 8 00:00:02 dnsmasq[524]: 2177 127.0.0.1/34406 query[PTR] 8.8.8.8.in-addr.arpa from 127.0.0.1
- Jul 8 00:00:02 dnsmasq[524]: 2177 127.0.0.1/34406 forwarded 8.8.8.8.in-addr.arpa to 2001:4860:4860::8888
- Jul 8 00:00:02 dnsmasq[524]: 2177 127.0.0.1/34406 reply 8.8.8.8 is google-public-dns-a.google.com
- Jul 8 00:00:02 dnsmasq[524]: 2178 127.0.0.1/41891 query[PTR] 220.220.67.208.in-addr.arpa from 127.0.0.1
- Jul 8 00:00:02 dnsmasq[524]: 2178 127.0.0.1/41891 forwarded 220.220.67.208.in-addr.arpa to 2001:4860:4860::8888
- Jul 8 00:00:02 dnsmasq[524]: 2178 127.0.0.1/41891 reply 208.67.220.220 is resolver2.opendns.com
- Jul 8 00:00:02 dnsmasq[524]: 2179 127.0.0.1/55006 query[PTR] 12.247.58.174.in-addr.arpa from 127.0.0.1
- Jul 8 00:00:02 dnsmasq[524]: 2179 127.0.0.1/55006 cached 174.58.247.12 is c-174-58-247-12.hsd1.fl.comcast.net
- Jul 8 00:00:02 dnsmasq[524]: 2180 127.0.0.1/45664 query[PTR] 117.0.168.192.in-addr.arpa from 127.0.0.1
- Jul 8 00:00:02 dnsmasq[524]: 2180 127.0.0.1/45664 DHCP 192.168.0.117 is Pavilion.lan
- Jul 8 00:00:02 dnsmasq[524]: 2181 127.0.0.1/53324 query[PTR] 121.0.168.192.in-addr.arpa from 127.0.0.1
- Jul 8 00:00:02 dnsmasq[524]: 2181 127.0.0.1/53324 DHCP 192.168.0.121 is Chromecast.lan
- Jul 8 00:00:02 dnsmasq[524]: 2182 127.0.0.1/47291 query[PTR] 122.0.168.192.in-addr.arpa from 127.0.0.1
- Jul 8 00:00:02 dnsmasq[524]: 2182 127.0.0.1/47291 DHCP 192.168.0.122 is DESKTOP-3CMD4T0.lan
- ********************************************
- ********************************************
- [✓] ** 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: 9cg8c3cex1
- ***********************************
- ***********************************
- * 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
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement