01-05-2019 02:34 PM
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 ]
2019-01-05:17:22:43 debug log has been initialized.
*** [ INITIALIZING ] Sourcing setup variables
Sourcing /etc/pihole/setupVars.conf...
*** [ DIAGNOSING ]: Core version
Core: v4.1.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
Branch: master
Commit: v4.1.1-0-g8d85d46
*** [ DIAGNOSING ]: Web version
Web: v4.1.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
Branch: master
Commit: v4.1.1-0-gde7aa5a
*** [ DIAGNOSING ]: FTL version
[✓] FTL: v4.1.2
*** [ DIAGNOSING ]: lighttpd version
1.4.45
*** [ DIAGNOSING ]: php version
7.0.33
*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 9 (stretch)
*** [ DIAGNOSING ]: SELinux
SELinux not detected
*** [ DIAGNOSING ]: Processor
[✓] armv7l
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.1.105/24 matches the IP found in /etc/pihole/setupVars.conf
[✓] IPv6 address(es) bound to the eth0 interface:
fe80::ee5d:eabd:2c7f:98a1 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.
Default IPv4 gateway: 192.168.1.1
192.168.1.1
* Pinging 192.168.1.1
192.168.1.1...
[✓] Gateway responded.
*** [ DIAGNOSING ]: Ports in use
*:22 sshd (IPv4)
*:22 sshd (IPv6)
01-05-2019 08:12 PM
01-06-2019 12:46 AM
01-06-2019 03:57 AM
01-06-2019 06:33 AM
01-06-2019 11:41 AM
01-06-2019 12:09 PM
01-07-2019 04:49 PM