guidol Posted June 16, 2018 Posted June 16, 2018 Today I would give my original Banana Pi (A20 / 1GB Ram) a new life/work and installed for testing armbian Bionic dev with kernel 4.17 (for not trashing my normal Pihole - a OPi PC2 with armbian stretch) After installing armbian bionic I did try to install Pihole via curl -sSL https://install.pi-hole.net | bash but it "crashes" while starting dnsmaq - because it seems to collide with resolved at Port 53 see as reference : https://github.com/pi-hole/pi-hole/issues/2179 After this reference I did edit /etc/systemd/resolved.conf and inserted DNSStubListener=no as a active line. Spoiler # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See resolved.conf(5) for details [Resolve] DNS=8.8.8.8 #FallbackDNS= #Domains= #LLMNR=no #MulticastDNS=no #DNSSEC=no #Cache=yes DNSStubListener=no (at the webpage above in some messages it says "DNSStubHandler=no" but doesnt work / isnt recognized) After that restart resolvd:sudo systemctl reload-or-restart systemd-resolved and check that they doesnt collide anymore at port 53 and do start successfully:sudo systemctl status dnsmasq.service systemd-resolved After they do start successfully restart the Pihole-installation with: pihole -r and the installation will complete: Spoiler Restarting services... [✓] Starting dnsmasq service [✓] Enabling dnsmasq service to start on reboot [✓] Starting lighttpd service [✓] Enabling lighttpd service to start on reboot [✓] Starting pihole-FTL service [✓] Enabling pihole-FTL service to start on reboot Preparing to run gravity.sh to refresh hosts... Running gravity.sh Neutrino emissions detected... [✓] Pulling blocklist source list into range Target: raw.githubusercontent.com (hosts) [✓] Status: Retrieval successful Target: mirror1.malwaredomains.com (justdomains) [✓] Status: Retrieval successful Target: sysctl.org (hosts) [✓] Status: Retrieval successful Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist) [✓] Status: Retrieval successful Target: s3.amazonaws.com (simple_tracking.txt) [✓] Status: Retrieval successful Target: s3.amazonaws.com (simple_ad.txt) [✓] Status: Retrieval successful Target: hosts-file.net (ad_servers.txt) [✓] Status: Retrieval successful [✓] Consolidating blocklists [✓] Extracting domains from blocklists Number of domains being pulled in by gravity: 149339 [✓] Removing duplicate domains Number of unique domains trapped in the Event Horizon: 126106 Number of whitelisted domains: 24 Number of blacklisted domains: 4 [✓] Parsing domains into hosts format [✓] Cleaning up stray matter [✓] Force-reloading DNS service [✓] DNS service is running [✓] Pi-hole blocking is Enabled The install log is located at: /etc/pihole/install.log Update Complete! At the end you could set a password for the WebUI with:pihole -a -p
guidol Posted June 17, 2018 Author Posted June 17, 2018 The Bionic update from today my Banana Pi was unbootable with this card (device 0 not found)... Dont know if it was the update. ext-filesystem or the card was clean as checked on another SBC.... The BPi is using a good 32GB SD-SanDisk Ultra Card.... Would be better to use Stretch as Pihole
Tido Posted June 17, 2018 Posted June 17, 2018 8 hours ago, guidol said: my Banana Pi was unbootable Hi Guido, I guess you are running armbian Beta ? I don't know if you followed that Thread, it would be great if you could test it with your pi-hole. A nice stress test :-)
guidol Posted June 18, 2018 Author Posted June 18, 2018 10 hours ago, Tido said: I don't know if you followed that Thread, it would be great if you could test it with your pi-hole. A nice stress test :-) Yes - I did fowwlow this thread - I did wrote there that I increased the log2ram value from 50 to 250MB because of the 1GB Ram of my OPi PC2 (or now original BPi) - so I didnt got a hanging system anymore with this bigger log2eram size - but this wouldnt help a SBC with only 256/512MB of Ram.
Tido Posted June 18, 2018 Posted June 18, 2018 Sorry, I didn't re-read, was a bit late ;-) However, Igor wrote today: Please pay attention to log rotation service. If that works properly. Starting with today update, current is broken. So it would be great you take the latest and greatest image or switch to Nightly in armbian-config sudo apt update && apt upgrade and try again with standard values for log2RAM
Recommended Posts