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-03:14:41:54 debug log has been initialized.
- *** [ INITIALIZING ] Sourcing setup variables
- [i] Sourcing /etc/pihole/setupVars.conf...
- *** [ DIAGNOSING ]: Core version
- git status failed
- *** [ DIAGNOSING ]: Web version
- git status failed
- *** [ DIAGNOSING ]: FTL version
- [✓] FTL: v3.0
- *** [ DIAGNOSING ]: dnsmasq version
- [i] 2.72
- *** [ DIAGNOSING ]: lighttpd version
- [i] opt
- *** [ DIAGNOSING ]: php version
- [i] 5.6.33
- *** [ DIAGNOSING ]: Operating system
- [✓] Debian GNU/Linux 8 (jessie)
- *** [ DIAGNOSING ]: SELinux
- [i] SELinux not detected
- *** [ DIAGNOSING ]: Processor
- *** [ DIAGNOSING ]: Networking
- [✓] IPv4 address(es) bound to the eth0 interface:
- 192.168.0.152/24 matches the IP found in /etc/pihole/setupVars.conf
- [✓] IPv6 address(es) bound to the eth0 interface:
- fe80::b239:56ff:fe6b:bd0d 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.
- *** [ DIAGNOSING ]: Ports in use
- [10000] is in use by upnphttpd
- [1194] is in use by vpnserver
- [139] is in use by smbd
- [14443] is in use by vpnserver
- [] is in use by
- [] is in use by
- [22] is in use by sshd
- [2708] is in use by SABnzbd.p
- [32400] is in use by Plex
- [3702] is in use by wsdd2
- [443] is in use by apache2
- [445] is in use by smbd
- [5355] is in use by wsdd2
- [548] is in use by afpd
- [5555] is in use by vpnserver
- [80] is in use by lighttpd
- [8200] is in use by minidlnad
- [992] is in use by vpnserver
- [6887] is in use by leafp2p
- [14369] is in use by xagent
- [32401] is in use by Plex
- [32600] is in use by Plex
- [41518] is in use by Plex
- [4711] is in use by pihole-FTL
- [7000] is in use by leafp2p
- *** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
- [✗] Failed to resolve wilberadam.com via localhost (127.0.0.1)
- [✗] Failed to resolve wilberadam.com via Pi-hole (192.168.0.152)
- [✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)
- *** [ DIAGNOSING ]: Pi-hole processes
- [✗] dnsmasq daemon is failed
- [✗] lighttpd daemon is inactive
- [✓] pihole-FTL daemon is active
- *** [ DIAGNOSING ]: Setup variables
- PIHOLE_INTERFACE=eth0
- IPV4_ADDRESS=192.168.0.152/24
- IPV6_ADDRESS=
- PIHOLE_DNS_1=208.67.222.222
- PIHOLE_DNS_2=208.67.220.220
- QUERY_LOGGING=
- INSTALL_WEB=
- TEMPERATUREUNIT=F
- WEBUIBOXEDLAYOUT=boxed
- *** [ DIAGNOSING ]: Dashboard and block page
- [✗] X-Header does not match or could not be retrieved.
- HTTP/1.1 302 Found
- Date: Tue, 03 Jul 2018 18:41:59 GMT
- Server: Apache/2.2.34 (Debian)
- Location: http://localhost/admin
- Connection: close
- Content-Type: text/html; charset=iso-8859-1
- [✗] X-Header does not match or could not be retrieved.
- HTTP/1.1 401 Authorization Required
- Date: Tue, 03 Jul 2018 18:41:59 GMT
- Server: Apache/2.2.34 (Debian)
- WWW-Authenticate: Basic realm="ReadyNAS Admin"
- Last-Modified: Thu, 01 Feb 2018 23:34:11 GMT
- ETag: "b25-1e2-5642f086aa2c0"
- Accept-Ranges: bytes
- Content-Length: 482
- Vary: User-Agent
- Access-Control-Allow-Origin: http://readycloud.netgear.com
- Access-Control-Allow-Headers: X-Requested-With
- Connection: close
- Content-Type: text/html
- *** [ DIAGNOSING ]: Gravity list
- -rw-r--r-- 1 pihole admin 4689897 Jul 2 22:18 /etc/pihole/gravity.list
- -----head of gravity.list------
- 192.168.0.152 0.0.0.0
- 192.168.0.152 0000mps.webpreview.dsl.net
- 192.168.0.152 000.0x1f4b0.com
- 192.168.0.152 0001.2waky.com
- -----tail of gravity.list------
- 192.168.0.152 zz.zeroredirect1.com
- 192.168.0.152 zzzezeroe.fr
- 192.168.0.152 zzzpooeaz-france.com
- 192.168.0.152 zzzrtrcm2.com
- *** [ DIAGNOSING ]: contents of /etc/pihole
- -rw-r--r-- 1 pihole admin 633 Jul 2 20:57 /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 pihole admin 49 Jul 2 22:18 /etc/pihole/local.list
- 192.168.0.152 nas-6B-BD-0D
- 192.168.0.152 pi.hole
- -rw-r--r-- 1 pihole admin 117 Jul 2 20:58 /etc/pihole/whitelist.txt
- raw.githubusercontent.com
- mirror1.malwaredomains.com
- sysctl.org
- zeustracker.abuse.ch
- s3.amazonaws.com
- hosts-file.net
- *** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
- -rw-r--r-- 1 root root 1547 Jul 3 14:41 /etc/dnsmasq.d/01-pihole.conf
- addn-hosts=/etc/pihole/gravity.list
- addn-hosts=/etc/pihole/black.list
- addn-hosts=/etc/pihole/local.list
- domain-needed
- localise-queries
- bogus-priv
- no-resolv
- server=208.67.222.222
- server=208.67.220.220
- interface=eth0
- cache-size=10000
- log-queries=extra
- log-facility=/var/log/pihole.log
- local-ttl=2
- log-async
- *** [ DIAGNOSING ]: contents of /etc/lighttpd
- /etc/lighttpd does not exist.
- *** [ DIAGNOSING ]: contents of /etc/cron.d
- *** [ DIAGNOSING ]: contents of /var/log/lighttpd
- /var/log/lighttpd does not exist.
- *** [ DIAGNOSING ]: contents of /var/log
- -rw-r--r-- 1 pihole pihole 19474 Jul 3 14:41 /var/log/pihole-FTL.log
- [2018-07-02 17:58:04.177]
- [2018-07-02 17:58:04.177] FTL branch: v3.0
- [2018-07-02 17:58:04.177] FTL version: v3.0
- [2018-07-02 17:58:04.177] FTL commit: a1b2fa03f8f3e3713b57a26a4e9a062fec0573d7
- [2018-07-02 17:58:04.177] FTL date: 2018-02-14 12:45:47 -0800
- [2018-07-02 17:58:04.178] FTL user: pihole
- [2018-07-02 17:58:04.178] Notice: Found no readable FTL config file
- [2018-07-02 17:58:04.178] Using default settings
- [2018-07-02 17:58:04.178] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
- [2018-07-02 17:58:04.178] SOCKET_LISTENING: only local
- [2018-07-02 17:58:04.178] QUERY_DISPLAY: Show queries
- [2018-07-02 17:58:04.178] AAAA_QUERY_ANALYSIS: Show AAAA queries
- [2018-07-02 17:58:04.178] MAXDBDAYS: max age for stored queries is 365 days
- [2018-07-02 17:58:04.178] RESOLVE_IPV6: Resolve IPv6 addresses
- [2018-07-02 17:58:04.178] RESOLVE_IPV4: Resolve IPv4 addresses
- [2018-07-02 17:58:04.178] DBINTERVAL: saving to DB file every minute
- [2018-07-02 17:58:04.178] DBFILE: Using /etc/pihole/pihole-FTL.db
- [2018-07-02 17:58:04.178] MAXLOGAGE: Importing up to 24.0 hours of log data
- [2018-07-02 17:58:04.178] Finished config file parsing
- [2018-07-02 17:58:04.187] Found no other running pihole-FTL process
- [2018-07-02 17:58:04.189] PID of FTL process: 29660
- [2018-07-02 17:58:05.016] Gravity list entries: 127788
- [2018-07-02 17:58:05.016] No blacklist present
- [2018-07-02 17:58:05.016] No wildcard blocking list present
- [2018-07-02 17:58:05.017] db_init() - Cannot open database (14): unable to open database file
- *** [ DIAGNOSING ]: Pi-hole log
- -rw-r--r-- 1 pihole admin 0 Jul 2 22:18 /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.
- [i] Debug script running in automated mode
- * 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
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement