# Pi-hole funktioniert nicht

**URL:** <https://discourse.pi-hole.net/t/pi-hole-funktioniert-nicht/6451>\
**Category:** Deutschsprachige Hilfe\
**Created:** [January 9, 2018, 9:11pm UTC](https://discourse.pi-hole.net/t/pi-hole-funktioniert-nicht/6451 "2018-01-09T21:11:41Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![kunja](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/k/d2c977/32.png) [@kunja](https://discourse.pi-hole.net/u/kunja)\
**Post date:** [January 21, 2018, 4:08pm UTC](https://discourse.pi-hole.net/t/pi-hole-funktioniert-nicht/6451/13 "2018-01-21T16:08:19Z")

</div>

Hier noch die debug Infos:

This process collects information from your Pi-hole, and optionally uploads it t o 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 smal l 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 c an access your data via the given token. We have taken these extra steps to secu re your data and will work to further reduce any personal information gathered.

\*\*\* [INITIALIZING]  
[i] 2018-01-21:17:02:18 debug log has been initiated.

\*\*\* [INITIALIZING] Sourcing setup variables  
[i] Sourcing /etc/pihole/setupVars.conf...

\*\*\* [DIAGNOSING]: Core version  
[i] Core: v3.2.1 ([How do I update Pi-hole?](https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249))  
[i] Branch: master  
[i] Commit: v3.2.1-0-ge602008

\*\*\* [DIAGNOSING]: Web version  
[i] Web: v3.2.1 ([How do I update Pi-hole?](https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249))  
[i] Branch: master  
[i] Commit: v3.2.1-0-g31dddd8

\*\*\* [DIAGNOSING]: FTL version  
[✓] FTL: v2.13.2

\*\*\* [DIAGNOSING]: dnsmasq version  
[i] 2.75

\*\*\* [DIAGNOSING]: lighttpd version  
[i] 1.4.35

\*\*\* [DIAGNOSING]: php version  
[i] 7.0.22

\*\*\* [DIAGNOSING]: Operating system  
[✓] Ubuntu 16.04.3 LTS

\*\*\* [DIAGNOSING]: SELinux  
[i] SELinux not detected

\*\*\* [DIAGNOSING]: Processor  
[i] x86\_64

\*\*\* [DIAGNOSING]: Networking  
[✓] IPv4 address(es) bound to the ens160 interface:  
192.168.1.18/24 matches the IP found in /etc/pihole/setupVars.conf

[✓] IPv6 address(es) bound to the ens160 interface:  
fe80::20c:29ff:fef7:9e2d does not match the IP found in /etc/pihole/setupVars .conf ([Use IPv6 ULA addresses for Pi-hole](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/setupV ars.conf, there is no need for concern.

The link to the FAQ is for an issue that sometimes occurs when the IPv6 addre ss changes, which is why we check for it.

[i] Default IPv4 gateway: 192.168.1.2

- Pinging 192.168.1.2...  
[✓] Gateway responded.

\*\*\* [DIAGNOSING]: Ports in use  
 is in use by  
[22] is in use by sshd  
[53] is in use by dnsmasq  
[80] is in use by lighttpd  
[4711] is in use by pihole-FTL  
[953] is in use by named

\*\*\* [DIAGNOSING]: Name resolution (IPv4) using a random blocked domain and a k nown ad-serving domain  
[✓] bs.serving-sys.com.20540.9120.302br.net is 69.172.216.56 via localhost (127. 0.0.1)  
[✓] bs.serving-sys.com.20540.9120.302br.net is 69.172.216.56 via Pi-hole (192.16 8.1.18)  
[✓] doubleclick.com is 216.58.205.110 via a remote, public DNS server (8.8.8.8)

\*\*\* [DIAGNOSING]: Pi-hole processes  
[✓] dnsmasq daemon is active  
[✓] lighttpd daemon is active  
[✓] pihole-FTL daemon is active

\*\*\* [DIAGNOSING]: Setup variables  
PIHOLE\_INTERFACE=ens160  
IPV4\_ADDRESS=192.168.1.18/24  
IPV6\_ADDRESS=  
PIHOLE\_DNS\_1=192.168.1.2  
PIHOLE\_DNS\_2=  
QUERY\_LOGGING=true  
INSTALL\_WEB=true  
LIGHTTPD\_ENABLED=1

\*\*\* [DIAGNOSING]: Dashboard and block page  
[✓] X-Pi-hole: A black hole for Internet advertisements.  
[✓] X-Pi-hole: The Pi-hole Web interface is working!

\*\*\* [DIAGNOSING]: Gravity list  
-rw-r--r-- 1 root root 3928716 Jan 21 16:33 /etc/pihole/gravity.list  
-----head of gravity.list------  
192.168.1.18 0.0.0.0  
192.168.1.18 0000mps.webpreview.dsl.net  
192.168.1.18 0001.2waky.com  
192.168.1.18 000dom.revenuedirect.com

-----tail of gravity.list------  
192.168.1.18 zzsyw.com  
192.168.1.18 zztxdown.com  
192.168.1.18 zzz.clickbank.net  
192.168.1.18 zz.zeroredirect1.com

\*\*\* [DIAGNOSING]: contents of /etc/pihole

-rw-r--r-- 1 root root 633 Jan 21 16:27 /etc/pihole/adlists.list  
[https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts](https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts)  
[https://mirror1.malwaredomains.com/files/justdomains](https://mirror1.malwaredomains.com/files/justdomains)  
[http://sysctl.org/cameleon/hosts](http://sysctl.org/cameleon/hosts)  
[https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist](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_tracking.txt)  
[https://s3.amazonaws.com/lists.disconnect.me/simple\_ad.txt](https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt)  
[https://hosts-file.net/ad\_servers.txt](https://hosts-file.net/ad_servers.txt)

-rw-r--r-- 1 root root 49 Jan 21 16:33 /etc/pihole/local.list  
192.168.1.18 ubuntuserver01  
192.168.1.18 pi.hole

-rw-r--r-- 1 root root 238 Jan 21 16:29 /etc/pihole/logrotate  
/var/log/pihole.log {  
su root syslog  
daily  
copytruncate  
rotate 5  
compress  
delaycompress  
notifempty  
nomail  
}  
/var/log/pihole-FTL.log {  
su root syslog  
weekly  
copytruncate  
rotate 3  
compress  
delaycompress  
notifempty  
nomail  
}

-rw-r--r-- 1 root root 117 Jan 21 16:27 /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 1493 Jan 21 16:29 /etc/dnsmasq.d/01-pihole.conf  
addn-hosts=/etc/pihole/gravity.list  
addn-hosts=/etc/pihole/black.list  
addn-hosts=/etc/pihole/local.list  
localise-queries  
no-resolv  
cache-size=10000  
log-queries  
log-facility=/var/log/pihole.log  
local-ttl=2  
log-async  
server=192.168.1.2  
interface=ens160

\*\*\* [DIAGNOSING]: contents of /etc/lighttpd

-rw-r--r-- 1 root root 3027 Jan 21 16:29 /etc/lighttpd/lighttpd.conf  
server.modules = (  
"mod\_access",  
"mod\_accesslog",  
"mod\_auth",  
"mod\_expire",  
"mod\_compress",  
"mod\_redirect",  
"mod\_setenv",  
"mod\_rewrite"  
)  
server.document-root = "/var/www/html"  
server.error-handler-404 = "pihole/index.php"  
server.upload-dirs = ( "/var/cache/lighttpd/uploads" )  
server.errorlog = "/var/log/lighttpd/error.log"  
server.pid-file = "/var/run/lighttpd.pid"  
server.username = "www-data"  
server.groupname = "www-data"  
server.port = 80  
accesslog.filename = "/var/log/lighttpd/access.log"  
accesslog.format = "%{%s}t|%V|%r|%s|%b"  
index-file.names = ( "index.php", "index.html", "index.lighttpd.ht ml" )  
url.access-deny = ( "~", ".inc", ".md", ".yml", ".ini" )  
static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )  
compress.cache-dir = "/var/cache/lighttpd/compress/"  
compress.filetype = ( "application/javascript", "text/css", "text/h tml", "text/plain" )  
include\_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port  
include\_shell "/usr/share/lighttpd/create-mime.assign.pl"  
include\_shell "find /etc/lighttpd/conf-enabled -name '\*.conf' -a ! -name 'let sencrypt.conf' -printf 'include "%p"  
' 2\>/dev/null"  
$HTTP["url"] =~ "^/admin/" {

```
   setenv.add-response-header = (
       "X-Pi-hole" => "The Pi-hole Web interface is working!",
       "X-Frame-Options" => "DENY"
   )
   $HTTP["url"] =~ ".ttf$" {

       setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
   }

```

}  
$HTTP["url"] =~ "^/admin/.(.\*)" {  
url.access-deny = ("")  
}  
include\_shell "cat external.conf 2\>/dev/null"

\*\*\* [DIAGNOSING]: contents of /etc/cron.d

-rw-r--r-- 1 root root 1630 Jan 21 16:29 /etc/cron.d/pihole  
28 3 \* \* 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity  
00 00 \* \* \* root PATH="$PATH:/usr/local/bin/" pihole flush once quiet  
@reboot root /usr/sbin/logrotate /etc/pihole/logrotate  
\*/10 \* \* \* \* root PATH="$PATH:/usr/local/bin/" pihole updatechecker loc al  
38 18 \* \* \* root PATH="$PATH:/usr/local/bin/" pihole updatechecker remo te  
@reboot root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote rebo ot

\*\*\* [DIAGNOSING]: contents of /var/log/lighttpd

-rw-r--r-- 1 www-data www-data 412 Jan 21 16:46 /var/log/lighttpd/error.log  
2018-01-21 15:53:33: (log.c.164) server started  
2018-01-21 15:54:56: (server.c.1558) server stopped by UID = 0 PID = 1  
2018-01-21 15:55:13: (log.c.164) server started  
2018-01-21 16:29:24: (server.c.1558) server stopped by UID = 0 PID = 1  
2018-01-21 16:29:24: (log.c.164) server started  
2018-01-21 16:46:23: (server.c.1558) server stopped by UID = 0 PID = 1  
2018-01-21 16:46:39: (log.c.164) server started

\*\*\* [DIAGNOSING]: contents of /var/log

-rw-r--r-- 1 pihole pihole 5420 Jan 21 16:46 /var/log/pihole-FTL.log  
[2018-01-21 16:29:25.314]  
[2018-01-21 16:29:25.314] FTL branch: v2.13.2  
[2018-01-21 16:29:25.314] FTL version: v2.13.2  
[2018-01-21 16:29:25.314] FTL commit: 1de2b99c8a812d4d2dbe6b1e4644e20a4b14bb1 e  
[2018-01-21 16:29:25.314] FTL date: 2018-01-07 17:34:24 -0800  
[2018-01-21 16:29:25.314] FTL user: pihole  
[2018-01-21 16:29:25.314] Notice: Found no readable FTL config file  
[2018-01-21 16:29:25.314] Using default settings  
[2018-01-21 16:29:25.314] Starting config file parsing (/etc/pihole/pihole-FT L.conf)  
[2018-01-21 16:29:25.314] SOCKET\_LISTENING: only local  
[2018-01-21 16:29:25.314] TIMEFRAME: Rolling 24h  
[2018-01-21 16:29:25.314] QUERY\_DISPLAY: Show queries  
[2018-01-21 16:29:25.314] AAAA\_QUERY\_ANALYSIS: Show AAAA queries  
[2018-01-21 16:29:25.314] MAXDBDAYS: max age for stored queries is 365 day s  
[2018-01-21 16:29:25.314] RESOLVE\_IPV6: Resolve IPv6 addresses  
[2018-01-21 16:29:25.314] RESOLVE\_IPV4: Resolve IPv4 addresses  
[2018-01-21 16:29:25.314] DBINTERVAL: saving to DB file every minute  
[2018-01-21 16:29:25.314] DBFILE: Using /etc/pihole/pihole-FTL.db  
[2018-01-21 16:29:25.314] Finished config file parsing  
[2018-01-21 16:29:25.315] Found no other running pihole-FTL process  
[2018-01-21 16:29:25.323] PID of FTL process: 3209  
[2018-01-21 16:29:25.370] Gravity list entries: 109694  
[2018-01-21 16:29:25.372] No blacklist present  
[2018-01-21 16:29:25.372] No wildcard blocking list present  
[2018-01-21 16:29:25.372] db\_init() - Cannot open database (14): unable to op en database file

\*\*\* [DIAGNOSING]: Pi-hole log  
-rw-r--r-- 1 dnsmasq root 3806 Jan 21 16:46 /var/log/pihole.log  
-----head of pihole.log------  
Jan 21 15:55:09 dnsmasq[1105]: gestartet, Version 2.75, Cachegröße 10000  
Jan 21 15:55:09 dnsmasq[1105]: Übersetzungsoptionen: IPv6 GNU-getopt DBus i18 n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify  
Jan 21 15:55:09 dnsmasq[1105]: Warnung: Ignoriere "resolv-file", weil "no-res olv" aktiv ist  
Jan 21 15:55:09 dnsmasq[1105]: Benutze Namensserver 192.168.1.2#53  
Jan 21 15:55:09 dnsmasq[1105]: /etc/hosts gelesen - 5 Adressen  
Jan 21 15:55:09 dnsmasq[1105]: Fehler beim Laden der Namen von /etc/pihole/lo cal.list: Datei oder Verzeichnis nicht gefunden  
Jan 21 15:55:09 dnsmasq[1105]: Fehler beim Laden der Namen von /etc/pihole/bl ack.list: Datei oder Verzeichnis nicht gefunden  
Jan 21 15:55:09 dnsmasq[1105]: Fehler beim Laden der Namen von /etc/pihole/gr avity.list: Datei oder Verzeichnis nicht gefunden  
Jan 21 16:27:22 dnsmasq[1105]: /etc/hosts gelesen - 5 Adressen  
Jan 21 16:27:22 dnsmasq[1105]: /etc/pihole/local.list gelesen - 2 Adressen  
Jan 21 16:27:22 dnsmasq[1105]: Fehler beim Laden der Namen von /etc/pihole/bl ack.list: Datei oder Verzeichnis nicht gefunden  
Jan 21 16:27:23 dnsmasq[1105]: /etc/pihole/gravity.list gelesen - 109694 Adre ssen  
Jan 21 16:27:23 dnsmasq[1105]: /etc/hosts gelesen - 5 Adressen  
Jan 21 16:27:23 dnsmasq[1105]: /etc/pihole/local.list gelesen - 2 Adressen  
Jan 21 16:27:23 dnsmasq[1105]: Fehler beim Laden der Namen von /etc/pihole/bl ack.list: Datei oder Verzeichnis nicht gefunden  
Jan 21 16:27:23 dnsmasq[1105]: /etc/pihole/gravity.list gelesen - 109694 Adre ssen  
Jan 21 16:29:23 dnsmasq[1105]: beende nach Empfang von SIGTERM  
Jan 21 16:29:23 dnsmasq[3012]: gestartet, Version 2.75, Cachegröße 10000  
Jan 21 16:29:23 dnsmasq[3012]: Übersetzungsoptionen: IPv6 GNU-getopt DBus i18 n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify  
Jan 21 16:29:23 dnsmasq[3012]: Warnung: Ignoriere "resolv-file", weil "no-res olv" aktiv ist

* * *

* * *

[✓] \*\* FINISHED DEBUGGING! \*\*

```
* The debug log can be uploaded to tricorder.pi-hole.net for sharing with de velopers only.
* For more information, see: https://pi-hole.net/2016/11/07/crack-our-medica l-tricorder-win-a-raspberry-pi-3/
* If available, we'll use openssl to upload the log, otherwise it will fall back to netcat.

```

---

_[View the full topic](https://discourse.pi-hole.net/t/pi-hole-funktioniert-nicht/6451)._
