API tools faq
paste
Advertisement
GlassOnion420

Debug Pi-Hole install 2-11-19

GlassOnion420
Feb 11th, 2019
358
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 20.11 KB | None | 0 0
raw download clone embed print report
  1.  
  2. Pi-hole
  3. Toggle navigation
  4.  
  5. MAXINET-HomeHub
  6. Pi-hole logo Pi-hole
  7.  
  8. Pi-hole logo
  9.  
  10. Status
  11. Active Temp: 118.4 °F
  12. Load: 0.5 0.7 0.33
  13. Memory usage: 8.3 %
  14.  
  15. MAIN NAVIGATION
  16. Dashboard
  17. Query Log
  18. Long term data
  19. Whitelist
  20. Blacklist
  21. Disable
  22. Tools
  23. Update Gravity
  24. Query Lists
  25. Audit log
  26. Tail pihole.log
  27. Tail pihole-FTL.log
  28. Generate debug log
  29. Settings
  30. Logout
  31. Donate
  32. Help
  33.  
  34. Generate debug log
  35.  
  36. Upload debug log and provide token once finished
  37.  
  38. Once you click this button a debug log will be generated and can automatically be uploaded if we detect a working internet connection.
  39.  
  40. This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.
  41.  
  42. 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.
  43.  
  44. 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.
  45.  
  46. *** [ INITIALIZING ]
  47. [i] 2019-02-11:08:53:18 debug log has been initialized.
  48.  
  49. *** [ INITIALIZING ] Sourcing setup variables
  50. [i] Sourcing /etc/pihole/setupVars.conf...
  51.  
  52. *** [ DIAGNOSING ]: Core version
  53. [i] Core: v4.2.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
  54. [i] Branch: master
  55. [i] Commit: v4.2.1-0-ge967fe2
  56.  
  57. *** [ DIAGNOSING ]: Web version
  58. [i] Web: v4.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
  59. [i] Branch: master
  60. [i] Commit: v4.2-0-g347994d
  61.  
  62. *** [ DIAGNOSING ]: FTL version
  63. [✓] FTL: v4.2.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
  64.  
  65. *** [ DIAGNOSING ]: lighttpd version
  66. [i] 1.4.45
  67.  
  68. *** [ DIAGNOSING ]: php version
  69. [i] 7.2.10
  70.  
  71. *** [ DIAGNOSING ]: Operating system
  72. [✓] Ubuntu 18.04.2 LTS
  73.  
  74. *** [ DIAGNOSING ]: SELinux
  75. [i] SELinux not detected
  76.  
  77. *** [ DIAGNOSING ]: Processor
  78. [i] x86_64
  79.  
  80. *** [ DIAGNOSING ]: Networking
  81. [✓] IPv4 address(es) bound to the enp3s0 interface:
  82. 192.168.1.7/24 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)
  83. 192.168.1.17/24 matches the IP found in /etc/pihole/setupVars.conf
  84.  
  85. [✓] IPv6 address(es) bound to the enp3s0 interface:
  86. 2600:6c5e:107f:f8c1:519a:ee1f:a03e:f621 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)
  87. 2600:6c5e:107f:f8c1:3124:379a:56dd:905c matches the IP found in /etc/pihole/setupVars.conf
  88. 2600:6c5e:107f:f8c1:70c2:e84b:72a4:248a 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)
  89. 2600:6c5e:107f:f8c1:bde9:1a31:cc7c:cc10 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)
  90. fe80::9d5a:5fb2:27f9:4d7c 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)
  91.  
  92. ^ Please note that you may have more than one IP address listed.
  93. As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.
  94.  
  95. The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.
  96.  
  97. [i] Default IPv4 gateway: 192.168.1.1
  98. * Pinging 192.168.1.1...
  99. [✓] Gateway responded.
  100. [i] Default IPv6 gateway: fe80::12da:43ff:fe70:ae85
  101. fe80::12da:43ff:fe70:ae85
  102. * Pinging fe80::12da:43ff:fe70:ae85
  103. fe80::12da:43ff:fe70:ae85...
  104. [✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
  105.  
  106.  
  107. *** [ DIAGNOSING ]: Ports in use
  108. [::1]:631 cupsd (IPv6)
  109. 127.0.0.1:631 cupsd (IPv4)
  110. *:22 sshd (IPv4)
  111. *:22 sshd (IPv6)
  112. 127.0.0.1:5353 unbound (IPv4)
  113. 127.0.0.1:8953 unbound (IPv4)
  114. [*:80] is in use by lighttpd
  115. [*:80] is in use by lighttpd
  116. [*:53] is in use by pihole-FTL
  117. [*:53] is in use by pihole-FTL
  118. [127.0.0.1:4711] is in use by pihole-FTL
  119. [[::1]:4711] is in use by pihole-FTL
  120.  
  121. *** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
  122. [✓] estsuelcon.com is 0.0.0.0 via localhost (127.0.0.1)
  123. [✓] estsuelcon.com is 0.0.0.0 via Pi-hole (192.168.1.17)
  124. [✓] doubleclick.com is 216.58.217.238 via a remote, public DNS server (8.8.8.8)
  125.  
  126. *** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
  127. [✓] ad195.hpg.com.br is :: via localhost (::1)
  128. [✓] ad195.hpg.com.br is :: via Pi-hole (2600:6c5e:107f:f8c1:3124:379a:56dd:905c)
  129. [✓] doubleclick.com is 2607:f8b0:4002:804::200e via a remote, public DNS server (2001:4860:4860::8888)
  130.  
  131. *** [ DIAGNOSING ]: Pi-hole processes
  132. [✓] lighttpd daemon is active
  133. [✓] pihole-FTL daemon is active
  134.  
  135. *** [ DIAGNOSING ]: Setup variables
  136. PIHOLE_INTERFACE=enp3s0
  137. IPV4_ADDRESS=192.168.1.17/24
  138. IPV6_ADDRESS=2600:6c5e:107f:f8c1:3124:379a:56dd:905c
  139. QUERY_LOGGING=true
  140. INSTALL_WEB_SERVER=true
  141. INSTALL_WEB_INTERFACE=true
  142. LIGHTTPD_ENABLED=true
  143. TEMPERATUREUNIT=F
  144. WEBUIBOXEDLAYOUT=boxed
  145. DNSMASQ_LISTENING=all
  146. PIHOLE_DNS_1=127.0.0.1#5353
  147. PIHOLE_DNS_2=127.0.0.1#5353
  148. DNS_FQDN_REQUIRED=true
  149. DNS_BOGUS_PRIV=true
  150. DNSSEC=false
  151. CONDITIONAL_FORWARDING=true
  152. CONDITIONAL_FORWARDING_IP=192.168.1.1
  153. CONDITIONAL_FORWARDING_DOMAIN=WORKGROUP
  154. CONDITIONAL_FORWARDING_REVERSE=1.168.192.in-addr.arpa
  155. BLOCKING_ENABLED=true
  156.  
  157. *** [ DIAGNOSING ]: Dashboard and block page
  158. [✓] Block page X-Header: X-Pi-hole: A black hole for Internet advertisements.
  159. [✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working!
  160.  
  161. *** [ DIAGNOSING ]: Gravity list
  162. -rw-r--r-- 1 root root 2641491 Feb 10 21:50 /etc/pihole/gravity.list
  163. -----head of gravity.list------
  164. 0.0.0.0
  165. 0.r.msn.com
  166. 0.start.bz
  167. 000.0x1f4b0.com
  168.  
  169. -----tail of gravity.list------
  170. zzz.clickbank.net
  171. zzzezeroe.fr
  172. zzzpooeaz-france.com
  173. zzzrtrcm2.com
  174.  
  175. *** [ DIAGNOSING ]: contents of /etc/pihole
  176.  
  177. -rw-r--r-- 1 root root 381 Feb 10 16:32 /etc/pihole/adlists.list
  178. https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
  179. https://mirror1.malwaredomains.com/files/justdomains
  180. http://sysctl.org/cameleon/hosts
  181. https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
  182. https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
  183. https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
  184. https://hosts-file.net/ad_servers.txt
  185.  
  186. -rw-r--r-- 1 root root 154 Feb 10 21:50 /etc/pihole/local.list
  187. 192.168.1.17 MAXINET-HomeHub
  188. 2600:6c5e:107f:f8c1:3124:379a:56dd:905c MAXINET-HomeHub
  189. 192.168.1.17 pi.hole
  190. 2600:6c5e:107f:f8c1:3124:379a:56dd:905c pi.hole
  191.  
  192. -rw-r--r-- 1 root root 238 Feb 10 16:33 /etc/pihole/logrotate
  193. /var/log/pihole.log {
  194. su root syslog
  195. daily
  196. copytruncate
  197. rotate 5
  198. compress
  199. delaycompress
  200. notifempty
  201. nomail
  202. }
  203. /var/log/pihole-FTL.log {
  204. su root syslog
  205. weekly
  206. copytruncate
  207. rotate 3
  208. compress
  209. delaycompress
  210. notifempty
  211. nomail
  212. }
  213.  
  214. *** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
  215.  
  216. -rw-r--r-- 1 root root 1671 Feb 10 18:05 /etc/dnsmasq.d/01-pihole.conf
  217. addn-hosts=/etc/pihole/gravity.list
  218. addn-hosts=/etc/pihole/black.list
  219. addn-hosts=/etc/pihole/local.list
  220. localise-queries
  221. no-resolv
  222. cache-size=10000
  223. log-queries
  224. log-facility=/var/log/pihole.log
  225. local-ttl=2
  226. log-async
  227. dhcp-name-match=set:wpad-ignore,wpad
  228. dhcp-ignore-names=tag:wpad-ignore
  229. domain-needed
  230. bogus-priv
  231. except-interface=nonexisting
  232. server=/WORKGROUP/192.168.1.1
  233. server=/1.168.192.in-addr.arpa/192.168.1.1
  234.  
  235. *** [ DIAGNOSING ]: contents of /etc/lighttpd
  236.  
  237. -rw-r--r-- 1 root root 3102 Feb 10 16:33 /etc/lighttpd/lighttpd.conf
  238. server.modules = (
  239. "mod_access",
  240. "mod_accesslog",
  241. "mod_auth",
  242. "mod_expire",
  243. "mod_compress",
  244. "mod_redirect",
  245. "mod_setenv",
  246. "mod_rewrite"
  247. )
  248. server.document-root = "/var/www/html"
  249. server.error-handler-404 = "pihole/index.php"
  250. server.upload-dirs = ( "/var/cache/lighttpd/uploads" )
  251. server.errorlog = "/var/log/lighttpd/error.log"
  252. server.pid-file = "/var/run/lighttpd.pid"
  253. server.username = "www-data"
  254. server.groupname = "www-data"
  255. server.port = 80
  256. accesslog.filename = "/var/log/lighttpd/access.log"
  257. accesslog.format = "%{%s}t|%V|%r|%s|%b"
  258. index-file.names = ( "index.php", "index.html", "index.lighttpd.html" )
  259. url.access-deny = ( "~", ".inc", ".md", ".yml", ".ini" )
  260. static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
  261. compress.cache-dir = "/var/cache/lighttpd/compress/"
  262. compress.filetype = ( "application/javascript", "text/css", "text/html", "text/plain" )
  263. include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
  264. include_shell "/usr/share/lighttpd/create-mime.assign.pl"
  265. include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include \"%p\"
  266. ' 2>/dev/null"
  267. $HTTP["url"] =~ "^/admin/" {
  268.  
  269. setenv.add-response-header = (
  270. "X-Pi-hole" => "The Pi-hole Web interface is working!",
  271. "X-Frame-Options" => "DENY"
  272. )
  273. $HTTP["url"] =~ ".ttf$" {
  274.  
  275. setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
  276. }
  277. }
  278. $HTTP["url"] =~ "^/admin/\.(.*)" {
  279. url.access-deny = ("")
  280. }
  281. include_shell "cat external.conf 2>/dev/null"
  282.  
  283. *** [ DIAGNOSING ]: contents of /etc/cron.d
  284.  
  285. -rw-r--r-- 1 root root 1704 Feb 10 16:33 /etc/cron.d/pihole
  286. 15 3 * * 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity >/var/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log
  287. 00 00 * * * root PATH="$PATH:/usr/local/bin/" pihole flush once quiet
  288. @reboot root /usr/sbin/logrotate /etc/pihole/logrotate
  289. */10 * * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker local
  290. 27 15 * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
  291. @reboot root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot
  292.  
  293. *** [ DIAGNOSING ]: contents of /var/log/lighttpd
  294.  
  295. -rw-r--r-- 1 www-data www-data 1000 Feb 11 08:49 /var/log/lighttpd/error.log
  296. 2019-02-10 16:33:42: (log.c.217) server started
  297. 2019-02-10 16:34:03: (server.c.1828) server stopped by UID = 0 PID = 1
  298. 2019-02-10 16:34:04: (log.c.217) server started
  299. 2019-02-10 16:35:18: (server.c.1828) server stopped by UID = 0 PID = 1
  300. 2019-02-10 16:36:42: (log.c.217) server started
  301. 2019-02-10 17:45:19: (server.c.1828) server stopped by UID = 0 PID = 1
  302. 2019-02-10 17:46:38: (log.c.217) server started
  303. 2019-02-10 19:12:45: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: unlink(../custom_disable_timer): No such file or directory in /var/www/html/admin/api.php on line 72
  304. 2019-02-10 21:43:35: (server.c.1828) server stopped by UID = 0 PID = 1
  305. 2019-02-10 21:44:43: (log.c.217) server started
  306. 2019-02-10 21:44:51: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: unlink(../custom_disable_timer): No such file or directory in /var/www/html/admin/api.php on line 47
  307. 2019-02-11 08:19:57: (server.c.1828) server stopped by UID = 0 PID = 1
  308. 2019-02-11 08:49:58: (log.c.217) server started
  309.  
  310. *** [ DIAGNOSING ]: contents of /var/log
  311.  
  312. -rw-r--r-- 1 pihole pihole 5695 Feb 11 08:50 /var/log/pihole-FTL.log
  313. -----head of pihole-FTL.log------
  314. [2019-02-11 00:23:25.526] Resizing "/FTL-queries" from 2359296 to 2654208
  315. [2019-02-11 01:13:50.783] Resizing "/FTL-queries" from 2654208 to 2949120
  316. [2019-02-11 02:04:46.285] Resizing "/FTL-queries" from 2949120 to 3244032
  317. [2019-02-11 02:55:11.530] Resizing "/FTL-queries" from 3244032 to 3538944
  318. [2019-02-11 03:46:07.019] Resizing "/FTL-queries" from 3538944 to 3833856
  319. [2019-02-11 04:35:31.524] Resizing "/FTL-queries" from 3833856 to 4128768
  320. [2019-02-11 05:26:26.772] Resizing "/FTL-queries" from 4128768 to 4423680
  321. [2019-02-11 06:15:51.282] Resizing "/FTL-queries" from 4423680 to 4718592
  322. [2019-02-11 07:06:46.774] Resizing "/FTL-queries" from 4718592 to 5013504
  323. [2019-02-11 07:57:12.024] Resizing "/FTL-queries" from 5013504 to 5308416
  324. [2019-02-11 08:19:57.236] Shutting down...
  325. [2019-02-11 08:19:58.544] Finished final database update
  326. [2019-02-11 08:19:58.546] ########## FTL terminated after 38114660.0 ms! ##########
  327. [2019-02-11 08:49:59.363] Using log file /var/log/pihole-FTL.log
  328. [2019-02-11 08:49:59.387] ########## FTL started! ##########
  329. [2019-02-11 08:49:59.387] FTL branch: master
  330. [2019-02-11 08:49:59.387] FTL version: v4.2.1
  331. [2019-02-11 08:49:59.387] FTL commit: 5f98312
  332. [2019-02-11 08:49:59.387] FTL date: 2019-02-06 18:36:55 -0800
  333. [2019-02-11 08:49:59.387] FTL user: pihole
  334. [2019-02-11 08:49:59.388] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
  335. [2019-02-11 08:49:59.388] SOCKET_LISTENING: only local
  336. [2019-02-11 08:49:59.388] AAAA_QUERY_ANALYSIS: Show AAAA queries
  337. [2019-02-11 08:49:59.388] MAXDBDAYS: max age for stored queries is 365 days
  338. [2019-02-11 08:49:59.388] RESOLVE_IPV6: Resolve IPv6 addresses
  339. [2019-02-11 08:49:59.388] RESOLVE_IPV4: Resolve IPv4 addresses
  340. [2019-02-11 08:49:59.388] DBINTERVAL: saving to DB file every minute
  341. [2019-02-11 08:49:59.388] DBFILE: Using /etc/pihole/pihole-FTL.db
  342. [2019-02-11 08:49:59.388] MAXLOGAGE: Importing up to 24.0 hours of log data
  343. [2019-02-11 08:49:59.388] PRIVACYLEVEL: Set to 0
  344. [2019-02-11 08:49:59.388] IGNORE_LOCALHOST: Show queries from localhost
  345. [2019-02-11 08:49:59.388] BLOCKINGMODE: Null IPs for blocked domains
  346. [2019-02-11 08:49:59.388] REGEX_DEBUGMODE: Inactive
  347. [2019-02-11 08:49:59.388] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
  348. [2019-02-11 08:49:59.388] DBIMPORT: Importing history from database
  349.  
  350. -----tail of pihole-FTL.log------
  351. [2019-02-11 08:49:59.724] New forward server: 192.168.1.1 (0/4096)
  352. [2019-02-11 08:49:59.813] Resizing "/FTL-queries" from 294912 to 589824
  353. [2019-02-11 08:49:59.828] Resizing "/FTL-queries" from 589824 to 884736
  354. [2019-02-11 08:49:59.839] Resizing "/FTL-queries" from 884736 to 1179648
  355. [2019-02-11 08:49:59.876] Resizing "/FTL-queries" from 1179648 to 1474560
  356. [2019-02-11 08:49:59.932] Resizing "/FTL-queries" from 1474560 to 1769472
  357. [2019-02-11 08:49:59.942] Resizing "/FTL-queries" from 1769472 to 2064384
  358. [2019-02-11 08:49:59.951] Resizing "/FTL-queries" from 2064384 to 2359296
  359. [2019-02-11 08:49:59.961] Resizing "/FTL-queries" from 2359296 to 2654208
  360. [2019-02-11 08:50:00.016] Resizing "/FTL-queries" from 2654208 to 2949120
  361. [2019-02-11 08:50:00.045] Resizing "/FTL-queries" from 2949120 to 3244032
  362. [2019-02-11 08:50:00.054] Resizing "/FTL-queries" from 3244032 to 3538944
  363. [2019-02-11 08:50:00.064] Resizing "/FTL-queries" from 3538944 to 3833856
  364. [2019-02-11 08:50:00.073] Resizing "/FTL-queries" from 3833856 to 4128768
  365. [2019-02-11 08:50:00.088] Resizing "/FTL-queries" from 4128768 to 4423680
  366. [2019-02-11 08:50:00.099] Resizing "/FTL-queries" from 4423680 to 4718592
  367. [2019-02-11 08:50:00.109] Resizing "/FTL-queries" from 4718592 to 5013504
  368. [2019-02-11 08:50:00.290] Resizing "/FTL-queries" from 5013504 to 5308416
  369. [2019-02-11 08:50:00.294] Imported 71482 queries from the long-term database
  370. [2019-02-11 08:50:00.295] -> Total DNS queries: 71482
  371. [2019-02-11 08:50:00.295] -> Cached DNS queries: 102
  372. [2019-02-11 08:50:00.295] -> Forwarded DNS queries: 92
  373. [2019-02-11 08:50:00.295] -> Exactly blocked DNS queries: 4
  374. [2019-02-11 08:50:00.295] -> Unknown DNS queries: 71284
  375. [2019-02-11 08:50:00.295] -> Unique domains: 31
  376. [2019-02-11 08:50:00.295] -> Unique clients: 4
  377. [2019-02-11 08:50:00.295] -> Known forward destinations: 1
  378. [2019-02-11 08:50:00.295] Successfully accessed setupVars.conf
  379. [2019-02-11 08:50:00.301] PID of FTL process: 1125
  380. [2019-02-11 08:50:00.301] Listening on port 4711 for incoming IPv4 telnet connections
  381. [2019-02-11 08:50:00.301] Listening on port 4711 for incoming IPv6 telnet connections
  382. [2019-02-11 08:50:00.301] Listening on Unix socket
  383. [2019-02-11 08:50:00.452] INFO: No whitelist file found
  384. [2019-02-11 08:50:00.452] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)
  385. [2019-02-11 08:50:02.064] /etc/pihole/gravity.list: parsed 112857 domains (took 1611.5 ms)
  386.  
  387. *** [ DIAGNOSING ]: contents of /dev/shm
  388. -rw------- 1 pihole pihole 16384 Feb 11 08:50 /dev/shm/FTL-client-0
  389. -rw------- 1 pihole pihole 16384 Feb 11 08:49 /dev/shm/FTL-client-1
  390. -rw------- 1 pihole pihole 16384 Feb 11 08:49 /dev/shm/FTL-client-2
  391. -rw------- 1 pihole pihole 16384 Feb 11 08:49 /dev/shm/FTL-client-3
  392. -rw------- 1 pihole pihole 16384 Feb 11 08:53 /dev/shm/FTL-client-4
  393. -rw------- 1 pihole pihole 163840 Feb 11 08:49 /dev/shm/FTL-clients
  394. -rw------- 1 pihole pihole 112 Feb 11 08:49 /dev/shm/FTL-counters
  395. -rw------- 1 pihole pihole 131072 Feb 11 08:50 /dev/shm/FTL-domains
  396. -rw------- 1 pihole pihole 163840 Feb 11 08:49 /dev/shm/FTL-forwarded
  397. -rw------- 1 pihole pihole 48 Feb 11 08:50 /dev/shm/FTL-lock
  398. -rw------- 1 pihole pihole 262144 Feb 11 08:50 /dev/shm/FTL-overTime
  399. -rw------- 1 pihole pihole 5308416 Feb 11 08:53 /dev/shm/FTL-queries
  400. -rw------- 1 pihole pihole 4096 Feb 11 08:49 /dev/shm/FTL-strings
  401.  
  402. *** [ DIAGNOSING ]: Locale
  403. LANG=en_US.UTF-8
  404.  
  405. *** [ DIAGNOSING ]: Pi-hole log
  406. -rw-r--r-- 1 pihole pihole 5202549 Feb 11 08:53 /var/log/pihole.log
  407. -----head of pihole.log------
  408. Feb 11 00:00:14 dnsmasq[1119]: query[A] ntp.ubuntu.com from 127.0.0.1
  409. Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
  410. Feb 11 00:00:14 dnsmasq[1119]: query[AAAA] ntp.ubuntu.com from 127.0.0.1
  411. Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
  412. Feb 11 00:00:14 dnsmasq[1119]: query[A] ntp.ubuntu.com from 127.0.0.1
  413. Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
  414. Feb 11 00:00:14 dnsmasq[1119]: query[AAAA] ntp.ubuntu.com from 127.0.0.1
  415. Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
  416. Feb 11 00:00:14 dnsmasq[1119]: query[A] ntp.ubuntu.com from 127.0.0.1
  417. Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
  418. Feb 11 00:00:14 dnsmasq[1119]: query[AAAA] ntp.ubuntu.com from 127.0.0.1
  419. Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
  420. Feb 11 00:00:14 dnsmasq[1119]: query[A] ntp.ubuntu.com from 127.0.0.1
  421. Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
  422. Feb 11 00:00:14 dnsmasq[1119]: query[AAAA] ntp.ubuntu.com from 127.0.0.1
  423. Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
  424. Feb 11 00:00:14 dnsmasq[1119]: query[A] ntp.ubuntu.com from 127.0.0.1
  425. Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
  426. Feb 11 00:00:14 dnsmasq[1119]: query[AAAA] ntp.ubuntu.com from 127.0.0.1
  427. Feb 11 00:00:14 dnsmasq[1119]: config error is REFUSED
  428.  
  429.  
  430. ********************************************
  431. ********************************************
  432. [✓] ** FINISHED DEBUGGING! **
  433.  
  434. * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
  435. * For more information, see: https://pi-hole.net/2016/11/07/crack-our-medical-tricorder-win-a-raspberry-pi-3/
  436. * If available, we'll use openssl to upload the log, otherwise it will fall back to netcat.
  437. [i] Debug script running in automated mode
  438. * Using openssl for transmission.
  439. [✗] There was an error uploading your debug log.
  440. * Please try again or contact the Pi-hole team for assistance.
  441. * A local copy of the debug log can be found at: /var/log/pihole_debug-sanitized.log
  442.  
  443. Donate if you found this useful.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!