Mon serveur YunoHost
*Matériel: Raspberry Pi à la maison
**Version de tYunoHost 3.8.4.8 (stable)
J’ai accès à mon serveur : En SSH | Par la webadmin
Êtes-vous dans un contexte particulier ou avez-vous effectué des modificiations particulières sur votre instance ? : non
J’ai l’impression que mon pihole ne fonctionne pas correctement, le service est " exited" et de plus, dans la page d’administration de pihole il est indiqué qu’il n’y a aucun client qui s’est connecté ( et pourtant j’ai declaré pihole conne DNS primaire pour un ipad et mes appareils android + un PC )
voila les logs:
https://paste.yunohost.org/ugaqiwugif
et mon pihole -d
admin@olitask:~ $ pihole -d
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 ]
[i] 2020-06-08:13:55:06 debug log has been initialized.
*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...
*** [ DIAGNOSING ]: Core version
fatal: No names found, cannot describe anything.
[✓] Core:
[i] Branch: master
[i] Commit: 70992e8-dirty
*** [ DIAGNOSING ]: Web version
*** [ DIAGNOSING ]: FTL version
[✓] FTL: vDev- (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
*** [ DIAGNOSING ]: dnsmasq version
[i] 2.76
*** [ DIAGNOSING ]: lighttpd version
[i] opt
*** [ DIAGNOSING ]: php version
[i] 7.0.33
*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 9 (stretch)
*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected
*** [ DIAGNOSING ]: Processor
/opt/pihole/piholeDebug.sh: line 474: $'[\E[32m✓\E[0m] \E[32marmv7l\E[0m': command not found
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.1.72/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)
[✓] IPv6 address(es) bound to the eth0 interface:
fe80::c267:ab23:8891:dcd1 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.
[i] Default IPv4 gateway: 192.168.1.1
* Pinging 192.168.1.1...
[✓] Gateway responded.
*** [ DIAGNOSING ]: Ports in use
[] is in use by
[] is in use by
[] is in use by
[] is in use by
[] is in use by
[139] is in use by smbd
[143] is in use by dovecot
[] is in use by
[1883] is in use by mosquitto
[22] is in use by sshd
[25] is in use by master
[3306] is in use by mysqld
[34101] is in use by java
[4040] is in use by java
[4190] is in use by dovecot
[443] is in use by nginx
[445] is in use by smbd
[51413] is in use by transmiss
[5222] is in use by lua5.1
[5269] is in use by lua5.1
[53] is in use by dnsmasq
[587] is in use by master
[6144] is in use by domoticz
[636] is in use by slapd
[8080] is in use by domoticz
[80] is in use by lighttpd
[9412] is in use by java
[993] is in use by dovecot
[46657] is in use by java
[10001] is in use by postsrsd
[10002] is in use by postsrsd
[11332] is in use by rspamd
[11333] is in use by rspamd
[11334] is in use by rspamd
[389] is in use by slapd
[4711] is in use by pihole-FTL
[5290] is in use by lua5.1
[61209] is in use by glances
[6379] is in use by redis-ser
[6787] is in use by yunohost-
[9091] is in use by transmiss
[34619] is in use by java
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] warterfoods.pl is 127.0.0.1 via localhost (127.0.0.1)
[✓] warterfoods.pl is 127.0.0.1 via Pi-hole (127.0.0.1)
[✓] doubleclick.com is 216.58.208.110 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] bs.serving-sys.com.46993.9349.302br.net is ::1 via localhost (::1)
[✓] bs.serving-sys.com.46993.9349.302br.net is ::1 via Pi-hole (::1)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)
*** [ DIAGNOSING ]: Pi-hole processes
[✓] dnsmasq daemon is active
[✗] lighttpd daemon is inactive
[✓] pihole-FTL daemon is active
*** [ DIAGNOSING ]: Setup variables
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=127.0.0.1
IPV6_ADDRESS=::1
PIHOLE_DNS_1=
PIHOLE_DNS_2=
QUERY_LOGGING=false
INSTALL_WEB=true
*** [ DIAGNOSING ]: Dashboard and block page
[✗] X-Header does not match or could not be retrieved.
HTTP/1.1 302 Moved Temporarily
Server: nginx
Date: Mon, 08 Jun 2020 11:55:19 GMT
Content-Type: text/html
Content-Length: 154
Connection: keep-alive
Location: https://localhost/yunohost/admin
[✗] X-Header does not match or could not be retrieved.
HTTP/1.1 302 Moved Temporarily
Server: nginx
Date: Mon, 08 Jun 2020 11:55:19 GMT
Content-Type: text/html
Content-Length: 154
Connection: keep-alive
Location: https://localhost/yunohost/admin
*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 7882864 Jun 7 01:59 /etc/pihole/gravity.list
-----head of gravity.list------
127.0.0.1 0.0.0.0
::1 0.0.0.0
127.0.0.1 0.0.0.0.beeglivesex.com
::1 0.0.0.0.beeglivesex.com
-----tail of gravity.list------
127.0.0.1 zzzpooeaz-france.com
::1 zzzpooeaz-france.com
127.0.0.1 zzzrtrcm2.com
::1 zzzrtrcm2.com
*** [ DIAGNOSING ]: contents of /etc/pihole
-rw-r--r-- 1 root root 633 Dec 14 14:47 /etc/pihole/adlists.list
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
http://sysctl.org/cameleon/hosts
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_ad.txt
https://hosts-file.net/ad_servers.txt
-rw-r--r-- 1 root root 86 Jun 7 01:59 /etc/pihole/local.list
127.0.0.1 olitask.changeip.com
::1 olitask.changeip.com
127.0.0.1 pi.hole
::1 pi.hole
-rw-r--r-- 1 root root 206 Apr 10 11:52 /etc/pihole/logrotate
/var/log/pihole.log {
daily
copytruncate
rotate 5
compress
delaycompress
notifempty
nomail
}
/var/log/pihole-FTL.log {
weekly
copytruncate
rotate 3
compress
delaycompress
notifempty
nomail
}
*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
-rw-r--r-- 1 root root 1515 Dec 14 14:46 /etc/dnsmasq.d/01-pihole.conf
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
domain-needed
localise-queries
bogus-priv
server=
server=
interface=eth0
cache-size=10000
log-facility=/var/log/pihole.log
local-ttl=2
log-async
*** [ DIAGNOSING ]: contents of /etc/lighttpd
*** [ DIAGNOSING ]: contents of /etc/cron.d
-rw-r--r-- 1 root root 1500 Apr 10 11:53 /etc/cron.d/pihole
59 1 * * 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
*** [ DIAGNOSING ]: contents of /var/log/lighttpd
/var/log/lighttpd does not exist.
ls: cannot access '/var/log/lighttpd': No such file or directory
*** [ DIAGNOSING ]: contents of /var/log
-rw-r--r-- 1 pihole pihole 2726 Jun 8 13:52 /var/log/pihole-FTL.log
[2020-06-08 00:00:02.117] NOTICE: pihole.log has been flushed
[2020-06-08 00:00:02.118] Resetting internal data structure
[2020-06-08 00:00:02.118] Queries in memory before flushing: 0
[2020-06-08 00:00:02.626] Gravity list entries: 131340
[2020-06-08 00:00:02.627] No blacklist present
[2020-06-08 00:00:02.627] No wildcard blocking list present
[2020-06-08 00:00:02.627] Reading from /var/log/pihole.log.1 (rw-r--r--)
[2020-06-08 00:00:02.627] Reading from /var/log/pihole.log (rw-r--r--)
[2020-06-08 13:52:33.865] FATAL: FTL received SIGTERM from PID/UID 3613/0, scheduled to exit gracefully
[2020-06-08 13:52:33.865] Shutting down...
[2020-06-08 13:52:33.869]
[2020-06-08 13:52:34.580]
[2020-06-08 13:52:34.580] FTL branch:
[2020-06-08 13:52:34.580] FTL version:
[2020-06-08 13:52:34.580] FTL commit:
[2020-06-08 13:52:34.580] FTL date:
[2020-06-08 13:52:34.580] FTL user: pihole
[2020-06-08 13:52:34.581] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2020-06-08 13:52:34.581] SOCKET_LISTENING: only local
[2020-06-08 13:52:34.581] TIMEFRAME: Rolling 24h
[2020-06-08 13:52:34.581] QUERY_DISPLAY: Show queries
[2020-06-08 13:52:34.581] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2020-06-08 13:52:34.581] MAXDBDAYS: max age for stored queries is 365 days
[2020-06-08 13:52:34.581] RESOLVE_IPV6: Resolve IPv6 addresses
[2020-06-08 13:52:34.582] RESOLVE_IPV4: Resolve IPv4 addresses
*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 dnsmasq root 5383 Jun 8 13:52 /var/log/pihole.log
-----head of pihole.log------
Jun 8 10:25:30 dnsmasq[828]: Lecture de /etc/resolv.dnsmasq.conf
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom nameserver#0
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom nameserver#0
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 89.233.43.71#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 2a01:3a0:53:53::#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 80.67.190.200#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 2001:1608:10:25::1c04:b12f#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 91.239.100.100#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 2a00:5884:8218::1#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 194.150.168.168#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 195.160.173.53#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 2a0c:e300::101#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 2a0c:e300::100#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 80.67.169.40#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 84.200.69.80#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 2001:910:800::40#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 89.234.141.66#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 185.233.100.101#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 2001:67c:28a4::#53
Jun 8 10:25:30 dnsmasq[828]: utilise le serveur de nom 185.233.100.100#53
********************************************
********************************************
[✓] ** FINISHED DEBUGGING! **
* The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
* For more information, see: https://pi-hole.net/2016/11/07/crack-our-medical-tricorder-win-a-raspberry-pi-3/
* If available, we'll use openssl to upload the log, otherwise it will fall back to netcat.
[?] Would you like to upload the log? [y/N] y
* Using openssl for transmission.
/opt/pihole/piholeDebug.sh: line 1079: warning: command substitution: ignored null byte in input
***********************************
***********************************
[✓] Your debug token is: https://tricorder.pi-hole.net/6sxxcaqpic
***********************************
***********************************
* Provide the token above to the Pi-hole team for assistance at
* https://discourse.pi-hole.net
* Your log will self-destruct on our server after 48 hours.
* A local copy of the debug log can be found at: /var/log/pihole_debug-sanitized.log
et je viens de voir que mon resolv.conf contient nameserver 8.8.8.8 (que devrait-il contenir ?)
Du coup ca fonctionne ou pas ??
Olivier