Hallo,
so, ich habe nun alles platt gemacht und von vorn begonnen.
Verwendet habe ich dieses Mal das aktuelle Debian IOT-Image (Debian 9.5 2018-10-07 4GB SD IoT).
Das Image wurde, im Unterschied zu vorher, nicht auf dem internen Speicher installiert, sondern läuft auf der SD-Karte. Die beim ersten Versuch erhaltenen Fehler habe ich allerdings nun nicht mehr gesehen.
Weil Nodejs den Port 80 blockiert, habe ich Nodejs und vorher c9-core-installer deinstalliert:
sudo apt remove c9-core-installer-core-installer
sudo apt remove nodejs
Danach ein Reboot: poweroff --reboot
lsof +M -nPi :53: nur connmand aktiv
lsof +M -nPi :80: Port 80 frei, d.h. keine Ausgabe
Danach Installation aktualisiert:
sudo apt-get update
sudo apt-get upgrade
Die Robotics-Erweiterungen wurden nicht installiert.
Nun die Installation von pi-hole:
git clone --depth 1 https://github.com/pi-hole/pi-hole.git pi-hole
sudo bash pi-hole/automated\ install/basic-install.sh
Ausgabe der Installation:
root@beaglebone:~# sudo bash pi-hole/automated\ install/basic-install.sh
[✓] Root user check
.;;,. .ccccc:,. :cccclll:. ..,, :ccccclll. ;ooodc 'ccll:;ll .oooodc .;cll.;;looo:. .. ','. .',,,,,,'. .',,,,,,,,,,. .',,,,,,,,,,,,.... ....''',,,,,,,'....... ......... .... ......... .......... .......... .......... .......... ......... .... ......... ........,,,,,,,'...... ....',,,,,,,,,,,,. .',,,,,,,,,'. .',,,,,,'. ..'''.[✓] Disk space check
[✓] Update local cache of available packages
[✓] Checking apt-get for upgraded packages... up to date!
[i] Installer Dependency checks...
[✓] Checking for apt-utils
[i] Checking for dialog (will be installed)
[✓] Checking for debconf
[i] Checking for dhcpcd5 (will be installed)
[✓] Checking for git
[✓] Checking for iproute2
[✓] Checking for whiptail
[i] Using interface: eth0
[i] Using Google DNS servers
[✓] Set IP address to 192.168.178.31
You may need to restart after the install is complete
[i] Found IPv6 ULA address, using it for blocking IPv6 ads
[i] IPv4 address: 192.168.178.31/24
[i] IPv6 address: fd00::9259:afff:fe56:9701
[i] Web Interface On
[i] Web Server On
[i] Logging On.
[✗] Check for existing repository in /etc/.pihole
[✓] Clone GitHub - pi-hole/pi-hole: A black hole for Internet advertisements into /etc/.pihole[✗] Check for existing repository in /var/www/html/admin
[✓] Clone GitHub - pi-hole/web: Pi-hole Dashboard for stats and more into /var/www/html/admin[i] Main Dependency checks...
[✓] Checking for bc
[✓] Checking for cron
[✓] Checking for curl
[i] Checking for dnsutils (will be installed)
[✓] Checking for iputils-ping
[✓] Checking for lsof
[i] Checking for netcat (will be installed)
[i] Checking for psmisc (will be installed)
[✓] Checking for sudo
[✓] Checking for unzip
[✓] Checking for wget
[i] Checking for idn2 (will be installed)
[i] Checking for sqlite3 (will be installed)
[i] Checking for libcap2-bin (will be installed)
[i] Checking for dns-root-data (will be installed)
[i] Checking for resolvconf (will be installed)
[i] Checking for lighttpd (will be installed)
[i] Checking for php-common (will be installed)
[i] Checking for php-cgi (will be installed)
[i] Checking for php-sqlite3 (will be installed)
[✓] Enabling lighttpd service to start on reboot
[✓] Installing scripts from /etc/.pihole[i] Installing configs from /etc/.pihole...
[i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
[✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf[i] Installing blocking page...
[✓] Creating directory for blocking page, and copying files
[✓] Backing up index.lighttpd.html[✓] Installing sudoer file
[✓] Installing latest Cron script
[✓] Installing latest logrotate script
[i] FTL Checks...
[✓] Detected ARM-hf architecture (armv7+)
[i] Checking for existing FTL binary...
[✓] Downloading and Installing FTL[i] Skipping firewall configuration
[i] man not installed
[i] Systemd-resolved is not enabled
[✓] Starting lighttpd service
[✓] Enabling lighttpd service to start on reboot
[i] Restarting services...
[✓] Starting pihole-FTL service
[✓] Enabling pihole-FTL service to start on reboot
[✓] Deleting existing list cache
[i] Neutrino emissions detected...
[✓] Pulling blocklist source list into range[i] Target: raw.githubusercontent.com (hosts)
[✗] Status: Connection Refused
[✗] List download failed: no cached list available[i] Target: mirror1.malwaredomains.com (justdomains)
[✗] Status: Connection Refused
[✗] List download failed: no cached list available[i] Target: sysctl.org (hosts)
[✗] Status: Connection Refused
[✗] List download failed: no cached list available[i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
[✗] Status: Connection Refused
[✗] List download failed: no cached list available[i] Target: s3.amazonaws.com (simple_tracking.txt)
[✗] Status: Connection Refused
[✗] List download failed: no cached list available[i] Target: s3.amazonaws.com (simple_ad.txt)
[✗] Status: Connection Refused
[✗] List download failed: no cached list available[i] Target: hosts-file.net (ad_servers.txt)
[✗] Status: Connection Refused
[✗] List download failed: no cached list available[✓] Consolidating blocklists
[✓] Extracting domains from blocklists
[i] Number of domains being pulled in by gravity: 0
[✓] Removing duplicate domains
[i] Number of unique domains trapped in the Event Horizon: 0
[i] Nothing to whitelist!
[i] Number of regex filters: 0
[✓] Parsing domains into hosts format
[✓] Cleaning up stray matter
[✓] Starting DNS service[✓] DNS service is running
[✓] Pi-hole blocking is Enabled
[i] Web Interface password: UdHiUYSd
[i] This can be changed using 'pihole -a -p'[i] View the web interface at http://pi.hole/admin or http://192.168.178.31/admin
[i] You may now configure your devices to use the Pi-hole as their DNS server
[i] Pi-hole DNS (IPv4): 192.168.178.31
[i] Pi-hole DNS (IPv6): fd00::9259:afff:fe56:9701
[i] If you set a new IP address, please restart the server running the Pi-hole[i] The install log is located at: /etc/pihole/install.log
Installation Complete!
Danach sudo service pihole-FTL status:
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Sat 2018-10-27 16:11:02 UTC; 2min 8s ago
Docs: man:systemd-sysv-generator(8)
Process: 1010 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/pihole-FTL.serviceOct 27 16:10:55 beaglebone systemd[1]: Starting LSB: pihole-FTL daemon...
Oct 27 16:10:56 beaglebone pihole-FTL[1010]: Not running
Oct 27 16:10:57 beaglebone pihole-FTL[1010]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
Oct 27 16:10:59 beaglebone pihole-FTL[1010]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf not a symbolic link to /etc/resolvconf/run/resolv.conf
Oct 27 16:11:00 beaglebone su[1221]: Successful su for pihole by root
Oct 27 16:11:00 beaglebone su[1221]: + ??? root:pihole
Oct 27 16:11:00 beaglebone su[1221]: pam_unix(su:session): session opened for user pihole by (uid=0)
Oct 27 16:11:02 beaglebone pihole-FTL[1010]: dnsmasq: illegal repeated keyword at line 8 of /etc/dnsmasq.d/SoftAp0
Oct 27 16:11:02 beaglebone systemd[1]: Started LSB: pihole-FTL daemon.
Daraufhin habe ich die Datei SoftAp0 umbenannt:
sudo mv SoftAp0 SoftAp0_xxx
Allerdings habe ich gesehen, dass die Datei SoftAp0 bei jedem Neustart neu erstellt wird.
Nun sah die Ausgabe von sudo service pihole-FTL status so aus:
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Sat 2018-10-27 16:17:54 UTC; 1h 41min ago
Docs: man:systemd-sysv-generator(8)
Process: 1039 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/pihole-FTL.serviceOct 27 16:17:47 beaglebone systemd[1]: Starting LSB: pihole-FTL daemon...
Oct 27 16:17:48 beaglebone pihole-FTL[1039]: Not running
Oct 27 16:17:49 beaglebone pihole-FTL[1039]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
Oct 27 16:17:51 beaglebone pihole-FTL[1039]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/
Oct 27 16:17:51 beaglebone su[1267]: Successful su for pihole by root
Oct 27 16:17:51 beaglebone su[1267]: + ??? root:pihole
Oct 27 16:17:51 beaglebone su[1267]: pam_unix(su:session): session opened for user pihole by (uid=0)
Oct 27 16:17:53 beaglebone pihole-FTL[1039]: dnsmasq: illegal repeated keyword at line 35 of /etc/dnsmasq.d/01-pihole.conf
Oct 27 16:17:54 beaglebone systemd[1]: Started LSB: pihole-FTL daemon.
Die Zeile 35 in /etc/dnsmasq.d/01-pihole.conf hat den Eintrag : cache-size=10000
Den Wert 10000 hab eich ersetzt durch 500000 lt. https://discourse.pi-hole.net/t/setting-dns-cache-limit-with-ftldns/8455/2
Danach Hardwarereset.
Nun wieder sudo service pihole-FTL status. Hier die Ausgabe:
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Sat 2018-10-27 18:12:15 UTC; 10min ago
Docs: man:systemd-sysv-generator(8)
Process: 1078 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/pihole-FTL.serviceOct 27 18:12:08 beaglebone systemd[1]: Starting LSB: pihole-FTL daemon...
Oct 27 18:12:09 beaglebone pihole-FTL[1078]: Not running
Oct 27 18:12:10 beaglebone pihole-FTL[1078]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
Oct 27 18:12:12 beaglebone pihole-FTL[1078]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf
Oct 27 18:12:14 beaglebone pihole-FTL[1078]: dnsmasq: illegal repeated keyword at line 35 of /etc/dnsmasq.d/01-pihole.conf
Oct 27 18:12:15 beaglebone systemd[1]: Started LSB: pihole-FTL daemon.
Die Datei /etc/pihole/dhcp.leases existiert tatsächlich nicht.
Der Fehler in /etc/dnsmasq.d/01-pihole.conf ist immer noch da.
Im Webinterface steht momentan 'Lost connection to API'.
Was kann ich nun noch tun?
VG
Tomas