Advertisement
Guest User

Untitled

a guest
Jul 2nd, 2018
261
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.72 KB | None | 0 0
  1. This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.
  2.  
  3. 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.
  4.  
  5. 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.
  6.  
  7. *** [ INITIALIZING ]
  8. [i] 2018-07-02:18:15:17 debug log has been initialized.
  9.  
  10. *** [ INITIALIZING ] Sourcing setup variables
  11. [i] Sourcing /etc/pihole/setupVars.conf...
  12.  
  13. *** [ DIAGNOSING ]: Core version
  14. git status failed
  15.  
  16. *** [ DIAGNOSING ]: Web version
  17. git status failed
  18.  
  19. *** [ DIAGNOSING ]: FTL version
  20. [✓] FTL: v3.0
  21.  
  22. *** [ DIAGNOSING ]: dnsmasq version
  23. [i] 2.72
  24.  
  25. *** [ DIAGNOSING ]: lighttpd version
  26. [i] opt
  27.  
  28. *** [ DIAGNOSING ]: php version
  29. [i] 5.6.33
  30.  
  31. *** [ DIAGNOSING ]: Operating system
  32. [✗] ReadyNASOS 6.9.3 (https://discourse.pi-hole.net/t/hardware-software-requirements/273)
  33.  
  34. *** [ DIAGNOSING ]: SELinux
  35. [i] SELinux not detected
  36.  
  37. *** [ DIAGNOSING ]: Processor
  38.  
  39. *** [ DIAGNOSING ]: Networking
  40. [✗] No IPv4 address(es) found on the eth0 interface.
  41.  
  42. [✗] No IPv6 address(es) found on the eth0 interface.
  43.  
  44. [i] Default IPv4 gateway: 192.168.0.1
  45. * Pinging 192.168.0.1...
  46. [✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
  47.  
  48.  
  49. *** [ DIAGNOSING ]: Ports in use
  50. [10000] is in use by upnphttpd
  51. [1194] is in use by vpnserver
  52. [139] is in use by smbd
  53. [14443] is in use by vpnserver
  54. [] is in use by
  55. [] is in use by
  56. [22] is in use by sshd
  57. [32400] is in use by Plex
  58. [3702] is in use by wsdd2
  59. [443] is in use by apache2
  60. [445] is in use by smbd
  61. [5355] is in use by wsdd2
  62. [548] is in use by afpd
  63. [5555] is in use by vpnserver
  64. [80] is in use by lighttpd
  65. [8200] is in use by minidlnad
  66. [992] is in use by vpnserver
  67. [6887] is in use by leafp2p
  68. [14369] is in use by xagent
  69. [32401] is in use by Plex
  70. [32600] is in use by Plex
  71. [41518] is in use by Plex
  72. [4711] is in use by pihole-FTL
  73. [7000] is in use by leafp2p
  74.  
  75. *** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
  76. [✗] Failed to resolve clevercoupons.co.uk via localhost (127.0.0.1)
  77. [✗] Failed to resolve clevercoupons.co.uk via Pi-hole (192.168.0.152)
  78. [✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)
  79.  
  80. *** [ DIAGNOSING ]: Pi-hole processes
  81. [✗] dnsmasq daemon is failed
  82. [✗] lighttpd daemon is inactive
  83. [✓] pihole-FTL daemon is active
  84.  
  85. *** [ DIAGNOSING ]: Setup variables
  86. PIHOLE_INTERFACE=eth0
  87. IPV4_ADDRESS=192.168.0.152/24
  88. IPV6_ADDRESS=
  89. PIHOLE_DNS_1=208.67.222.222
  90. PIHOLE_DNS_2=208.67.220.220
  91. QUERY_LOGGING=
  92. INSTALL_WEB=
  93. TEMPERATUREUNIT=F
  94. WEBUIBOXEDLAYOUT=boxed
  95.  
  96. *** [ DIAGNOSING ]: Dashboard and block page
  97. [✗] X-Header does not match or could not be retrieved.
  98. HTTP/1.1 302 Found
  99. Date: Tue, 03 Jul 2018 01:15:22 GMT
  100. Server: Apache/2.2.34 (Debian)
  101. Location: http://localhost/admin
  102. Connection: close
  103. Content-Type: text/html; charset=iso-8859-1
  104.  
  105. [✗] X-Header does not match or could not be retrieved.
  106. HTTP/1.1 401 Authorization Required
  107. Date: Tue, 03 Jul 2018 01:15:22 GMT
  108. Server: Apache/2.2.34 (Debian)
  109. WWW-Authenticate: Basic realm="ReadyNAS Admin"
  110. Last-Modified: Thu, 01 Feb 2018 23:34:11 GMT
  111. ETag: "b25-1e2-5642f086aa2c0"
  112. Accept-Ranges: bytes
  113. Content-Length: 482
  114. Vary: User-Agent
  115. Access-Control-Allow-Origin: http://readycloud.netgear.com
  116. Access-Control-Allow-Headers: X-Requested-With
  117. Connection: close
  118. Content-Type: text/html
  119.  
  120.  
  121. *** [ DIAGNOSING ]: Gravity list
  122. -rw-r--r-- 1 root root 4689897 Jul 2 18:13 /etc/pihole/gravity.list
  123. -----head of gravity.list------
  124. 192.168.0.152 0.0.0.0
  125. 192.168.0.152 0000mps.webpreview.dsl.net
  126. 192.168.0.152 000.0x1f4b0.com
  127. 192.168.0.152 0001.2waky.com
  128.  
  129. -----tail of gravity.list------
  130. 192.168.0.152 zz.zeroredirect1.com
  131. 192.168.0.152 zzzezeroe.fr
  132. 192.168.0.152 zzzpooeaz-france.com
  133. 192.168.0.152 zzzrtrcm2.com
  134.  
  135. *** [ DIAGNOSING ]: contents of /etc/pihole
  136.  
  137. -rw-r--r-- 1 pihole admin 633 Jul 2 17:57 /etc/pihole/adlists.list
  138. https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
  139. https://mirror1.malwaredomains.com/files/justdomains
  140. http://sysctl.org/cameleon/hosts
  141. https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
  142. https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
  143. https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
  144. https://hosts-file.net/ad_servers.txt
  145.  
  146. -rw-r--r-- 1 pihole admin 49 Jul 2 18:13 /etc/pihole/local.list
  147. 192.168.0.152 nas-6B-BD-0D
  148. 192.168.0.152 pi.hole
  149.  
  150. -rw-r--r-- 1 pihole admin 117 Jul 2 17:58 /etc/pihole/whitelist.txt
  151. raw.githubusercontent.com
  152. mirror1.malwaredomains.com
  153. sysctl.org
  154. zeustracker.abuse.ch
  155. s3.amazonaws.com
  156. hosts-file.net
  157.  
  158. *** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
  159.  
  160. -rw-r--r-- 1 root root 1547 Jul 2 18:13 /etc/dnsmasq.d/01-pihole.conf
  161. addn-hosts=/etc/pihole/gravity.list
  162. addn-hosts=/etc/pihole/black.list
  163. addn-hosts=/etc/pihole/local.list
  164. domain-needed
  165. localise-queries
  166. bogus-priv
  167. no-resolv
  168. server=208.67.222.222
  169. server=208.67.220.220
  170. interface=eth0
  171. cache-size=10000
  172. log-queries=extra
  173. log-facility=/var/log/pihole.log
  174. local-ttl=2
  175. log-async
  176.  
  177. *** [ DIAGNOSING ]: contents of /etc/lighttpd
  178. /etc/lighttpd does not exist.
  179.  
  180. *** [ DIAGNOSING ]: contents of /etc/cron.d
  181.  
  182. *** [ DIAGNOSING ]: contents of /var/log/lighttpd
  183. /var/log/lighttpd does not exist.
  184.  
  185. *** [ DIAGNOSING ]: contents of /var/log
  186.  
  187. -rw-r--r-- 1 pihole pihole 8618 Jul 2 18:14 /var/log/pihole-FTL.log
  188. [2018-07-02 17:58:04.177]
  189. [2018-07-02 17:58:04.177] FTL branch: v3.0
  190. [2018-07-02 17:58:04.177] FTL version: v3.0
  191. [2018-07-02 17:58:04.177] FTL commit: a1b2fa03f8f3e3713b57a26a4e9a062fec0573d7
  192. [2018-07-02 17:58:04.177] FTL date: 2018-02-14 12:45:47 -0800
  193. [2018-07-02 17:58:04.178] FTL user: pihole
  194. [2018-07-02 17:58:04.178] Notice: Found no readable FTL config file
  195. [2018-07-02 17:58:04.178] Using default settings
  196. [2018-07-02 17:58:04.178] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
  197. [2018-07-02 17:58:04.178] SOCKET_LISTENING: only local
  198. [2018-07-02 17:58:04.178] QUERY_DISPLAY: Show queries
  199. [2018-07-02 17:58:04.178] AAAA_QUERY_ANALYSIS: Show AAAA queries
  200. [2018-07-02 17:58:04.178] MAXDBDAYS: max age for stored queries is 365 days
  201. [2018-07-02 17:58:04.178] RESOLVE_IPV6: Resolve IPv6 addresses
  202. [2018-07-02 17:58:04.178] RESOLVE_IPV4: Resolve IPv4 addresses
  203. [2018-07-02 17:58:04.178] DBINTERVAL: saving to DB file every minute
  204. [2018-07-02 17:58:04.178] DBFILE: Using /etc/pihole/pihole-FTL.db
  205. [2018-07-02 17:58:04.178] MAXLOGAGE: Importing up to 24.0 hours of log data
  206. [2018-07-02 17:58:04.178] Finished config file parsing
  207. [2018-07-02 17:58:04.187] Found no other running pihole-FTL process
  208. [2018-07-02 17:58:04.189] PID of FTL process: 29660
  209. [2018-07-02 17:58:05.016] Gravity list entries: 127788
  210. [2018-07-02 17:58:05.016] No blacklist present
  211. [2018-07-02 17:58:05.016] No wildcard blocking list present
  212. [2018-07-02 17:58:05.017] db_init() - Cannot open database (14): unable to open database file
  213.  
  214. *** [ DIAGNOSING ]: Pi-hole log
  215. -rw-r--r-- 1 pihole admin 0 Jul 2 17:58 /var/log/pihole.log
  216. -----head of pihole.log------
  217.  
  218.  
  219. ********************************************
  220. ********************************************
  221. [✓] ** FINISHED DEBUGGING! **
  222.  
  223. * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
  224. * For more information, see: https://pi-hole.net/2016/11/07/crack-our-medical-tricorder-win-a-raspberry-pi-3/
  225. * If available, we'll use openssl to upload the log, otherwise it will fall back to netcat.
  226. [i] Debug script running in automated mode
  227. * Using openssl for transmission.
  228.  
  229. ***********************************
  230. ***********************************
  231. [✓] Your debug token is: b78o6pkibv
  232. ***********************************
  233. ***********************************
  234.  
  235. * Provide the token above to the Pi-hole team for assistance at
  236. * https://discourse.pi-hole.net
  237. * Your log will self-destruct on our server after 48 hours.
  238. * 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