henere
Goto Top

Frage zum PiHole logging

Servus zusammen,

hab nen PiHole unter Ubuntu 18.04.4 LTS laufen.

Pi-hole Version v4.4 Web Interface Version v4.3.3 FTL Version v4.3.1

Da ich hier mit einigen Netzwerkproblemen zu kämpfen habe, würde ich gerne sehen, was das Ding live macht.
Laut Internet: /var/log/pihole.log
Auch hier zu sehen, privacy steht auf 0 => Level 0 - show everything - Doesn't hide anything, all statistics are available

Aber mehr als das steht nicht drin:
[2020-04-01 22:19:24.303 985] ########## FTL started! ##########
[2020-04-01 22:19:24.303 985] FTL branch: master
[2020-04-01 22:19:24.303 985] FTL version: v4.3.1
[2020-04-01 22:19:24.303 985] FTL commit: b60d63f
[2020-04-01 22:19:24.303 985] FTL date: 2019-05-25 21:37:26 +0200
[2020-04-01 22:19:24.303 985] FTL user: pihole
[2020-04-01 22:19:24.303 985] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2020-04-01 22:19:24.303 985]    SOCKET_LISTENING: only local
[2020-04-01 22:19:24.303 985]    AAAA_QUERY_ANALYSIS: Show AAAA queries
[2020-04-01 22:19:24.303 985]    MAXDBDAYS: max age for stored queries is 365 days
[2020-04-01 22:19:24.303 985]    RESOLVE_IPV6: Resolve IPv6 addresses
[2020-04-01 22:19:24.304 985]    RESOLVE_IPV4: Resolve IPv4 addresses
[2020-04-01 22:19:24.304 985]    DBINTERVAL: saving to DB file every minute
[2020-04-01 22:19:24.304 985]    DBFILE: Using /etc/pihole/pihole-FTL.db
[2020-04-01 22:19:24.304 985]    MAXLOGAGE: Importing up to 24.0 hours of log data
[2020-04-01 22:19:24.304 985]    PRIVACYLEVEL: Set to 0
[2020-04-01 22:19:24.304 985]    IGNORE_LOCALHOST: Show queries from localhost
[2020-04-01 22:19:24.304 985]    BLOCKINGMODE: Null IPs for blocked domains
[2020-04-01 22:19:24.304 985]    ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
[2020-04-01 22:19:24.304 985]    DBIMPORT: Importing history from database
[2020-04-01 22:19:24.304 985]    PIDFILE: Using /var/run/pihole-FTL.pid
[2020-04-01 22:19:24.304 985]    PORTFILE: Using /var/run/pihole-FTL.port
[2020-04-01 22:19:24.304 985]    SOCKETFILE: Using /var/run/pihole/FTL.sock
[2020-04-01 22:19:24.304 985]    WHITELISTFILE: Using /etc/pihole/whitelist.txt
[2020-04-01 22:19:24.304 985]    BLACKLISTFILE: Using /etc/pihole/black.list
[2020-04-01 22:19:24.304 985]    GRAVITYFILE: Using /etc/pihole/gravity.list
[2020-04-01 22:19:24.304 985]    REGEXLISTFILE: Using /etc/pihole/regex.list
[2020-04-01 22:19:24.304 985]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
[2020-04-01 22:19:24.304 985]    AUDITLISTFILE: Using /etc/pihole/auditlog.list
[2020-04-01 22:19:24.304 985]    MACVENDORDB: Using /etc/pihole/macvendor.db
[2020-04-01 22:19:24.304 985]    PARSE_ARP_CACHE: Active
[2020-04-01 22:19:24.304 985] Finished config file parsing
[2020-04-01 22:19:24.309 985] Database version is 3
[2020-04-01 22:19:24.309 985] Database successfully initialized
[2020-04-01 22:19:24.312 985] New forward server: 208.67.220.220 (0/512)
[2020-04-01 22:19:24.313 985] New forward server: 208.67.222.222 (1/512)
[2020-04-01 22:19:24.314 985] Resizing "/FTL-strings" from 4096 to 8192  
[2020-04-01 22:19:24.315 985] Resizing "/FTL-strings" from 8192 to 12288  
[2020-04-01 22:19:24.317 985] Resizing "/FTL-strings" from 12288 to 16384  
[2020-04-01 22:19:24.318 985] Resizing "/FTL-strings" from 16384 to 20480  
[2020-04-01 22:19:24.321 985] Resizing "/FTL-queries" from 229376 to 458752  
[2020-04-01 22:19:24.321 985] Resizing "/FTL-strings" from 20480 to 24576  
[2020-04-01 22:19:24.324 985] Resizing "/FTL-strings" from 24576 to 28672  
[2020-04-01 22:19:24.328 985] Resizing "/FTL-strings" from 28672 to 32768  
[2020-04-01 22:19:24.330 985] Resizing "/FTL-strings" from 32768 to 36864  
[2020-04-01 22:19:24.331 985] Resizing "/FTL-queries" from 458752 to 688128  
[2020-04-01 22:19:24.336 985] Resizing "/FTL-strings" from 36864 to 40960  
[2020-04-01 22:19:24.340 985] Resizing "/FTL-strings" from 40960 to 45056  
[2020-04-01 22:19:24.342 985] Resizing "/FTL-queries" from 688128 to 917504  
[2020-04-01 22:19:24.348 985] Resizing "/FTL-strings" from 45056 to 49152  
[2020-04-01 22:19:24.353 985] Resizing "/FTL-queries" from 917504 to 1146880  
[2020-04-01 22:19:24.356 985] Resizing "/FTL-strings" from 49152 to 53248  
[2020-04-01 22:19:24.361 985] Resizing "/FTL-strings" from 53248 to 57344  
[2020-04-01 22:19:24.364 985] Resizing "/FTL-queries" from 1146880 to 1376256  
[2020-04-01 22:19:24.371 985] Resizing "/FTL-strings" from 57344 to 61440  
[2020-04-01 22:19:24.375 985] Resizing "/FTL-queries" from 1376256 to 1605632  
[2020-04-01 22:19:24.382 985] Resizing "/FTL-strings" from 61440 to 65536  
[2020-04-01 22:19:24.388 985] Resizing "/FTL-queries" from 1605632 to 1835008  
[2020-04-01 22:19:24.391 985] Imported 29570 queries from the long-term database
[2020-04-01 22:19:24.392 985]  -> Total DNS queries: 29570
[2020-04-01 22:19:24.392 985]  -> Cached DNS queries: 371
[2020-04-01 22:19:24.392 985]  -> Forwarded DNS queries: 13997
[2020-04-01 22:19:24.392 985]  -> Exactly blocked DNS queries: 15202
[2020-04-01 22:19:24.392 985]  -> Unknown DNS queries: 0
[2020-04-01 22:19:24.392 985]  -> Unique domains: 2016
[2020-04-01 22:19:24.392 985]  -> Unique clients: 4
[2020-04-01 22:19:24.392 985]  -> Known forward destinations: 2
[2020-04-01 22:19:24.392 985] Successfully accessed setupVars.conf
[2020-04-01 22:19:24.397 987] PID of FTL process: 987
[2020-04-01 22:19:24.397 987] Listening on port 4711 for incoming IPv4 telnet connections
[2020-04-01 22:19:24.397 987] Listening on port 4711 for incoming IPv6 telnet connections
[2020-04-01 22:19:24.397 987] Listening on Unix socket
[2020-04-01 22:19:24.397 987] Received SIGHUP, reloading cache
[2020-04-01 22:19:24.397 987] Blocking status is enabled
[2020-04-01 22:19:24.398 987] ERROR compiling regex on line 1: Invalid preceding regular expression (13)
[2020-04-01 22:19:24.398 987] Compiled 4 Regex filters and 62 whitelisted domains in 0.8 msec (0 errors)
[2020-04-01 22:19:24.399 987] /etc/pihole/black.list: parsed 19 domains (took 0.0 ms)
[2020-04-01 22:19:37.980 987] /etc/pihole/gravity.list: parsed 4429125 domains (took 13580.7 ms)
[2020-04-01 22:24:03.493 987] Resizing "/FTL-strings" from 65536 to 69632  

Laut Internet in den Settings => Privacy kann man das logging ein und ausschalten.

Steht bei mir auf:

unbenannt

Rufe ich pihole -t auf, so kommt das hier: (Query Logging is disabled)

root@s-v-pihole:~# pihole -t
  [✗] Warning: Query logging is disabled
  [i] Press Ctrl-C to exit
Apr  1 22:19:24 dnsmasq[987]: started, version pi-hole-2.80 cachesize 10000
Apr  1 22:19:24 dnsmasq[987]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC loop-detect inotify dumpfile
Apr  1 22:19:24 dnsmasq[987]: using local addresses only for domain use-application-dns.net
Apr  1 22:19:24 dnsmasq[987]: using nameserver 208.67.220.220#53
Apr  1 22:19:24 dnsmasq[987]: using nameserver 208.67.222.222#53
Apr  1 22:19:24 dnsmasq[987]: read /etc/hosts - 5 addresses
Apr  1 22:19:24 dnsmasq[987]: read /etc/pihole/local.list - 2 addresses
Apr  1 22:19:24 dnsmasq[987]: read /etc/pihole/black.list - 19 addresses
Apr  1 22:19:37 dnsmasq[987]: read /etc/pihole/gravity.list - 4429125 addresses

In der gui sehe ich unter Querylog alle Anfragen, aber das manuelle aktualisieren nervt.

Wie bekomme ich es nun hin, dass der pihole mir mit einem tail anzeigt, was er gerade macht ?


Grüße, Henere

Content-Key: 562381

Url: https://administrator.de/contentid/562381

Ausgedruckt am: 29.03.2024 um 15:03 Uhr

Mitglied: KowaKowalski
KowaKowalski 01.04.2020 um 23:52:03 Uhr
Goto Top
Hi Henere,

geh auf Settings > Reiter System > Danger Zone (unten)

Dann ist die logging Warnung wech und Du hast´n Durchblick.


mfg
und
jute Nacht
kowa
Mitglied: Henere
Henere 02.04.2020 aktualisiert um 00:52:07 Uhr
Goto Top
Sorry. Den sehe ich nicht ?

screenshot_20200402-004942_chrome

screenshot_20200402-005134_chrome
Mitglied: KowaKowalski
Lösung KowaKowalski 02.04.2020 aktualisiert um 02:12:09 Uhr
Goto Top
Jo, richtig.
gleich den ersten orangen Button "Disable query logging" hatte ich bei Dir in Grün vermutet.

Da stimmt was nicht.
Hast Du mal ein schnödes
sudo pihole logging off
sudo pihole logging on
probiert?
Vielleicht schmeißt er Dir da nen verwertbaren Fehler raus.

mfg
kowa
Mitglied: Henere
Henere 02.04.2020 um 11:09:14 Uhr
Goto Top
Zitat von @KowaKowalski:
sudo pihole logging off
> sudo pihole logging on
mfg
kowa

Ja, jetzt gehts. Danke Dir !

Henere