-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot install pihole image to SD card #66
Comments
Hi, Try changing the image size from 4000 to 2000 and re-deploy. Older devices may not be able to handle disk images greater than 2048MB. Alternatively, try formatting the SDcard EXT4. Sometimes it's easier to format it on another device. The CentOS image doesn't take much space, 1GB free should be plenty if you tighen-up log retention. |
I created a ext4 partition on the SD card, now the error is different: "Importing rootfs from tar.gz archive... fail". Full log: Edit: made log collapsible for easier navigation
|
It looks like you had better progress with your first attempt. Make sure auto-start at boot is disabled (for now) and reboot your device before you try to deploy. I've seen issues where deployment fails and subsequent attempts will always fail because resources in use from the previous deployment aren't properly released. |
That got the job done, thank you very much! |
Now I have a problem with Pi-hole itself, and its support redirected me back here. I have red "DNS service not running" on top and the error message "PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Unknown error) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:47 ". I have tried a few fixes: https://discourse.pi-hole.net/t/fixed-php-error-2-fsockopen-unable-to-connect-to-127-0-0-1-4711-connection-refused-in-var-www-html-admin-scripts-pi-hole-php-ftl-php-47/59325, https://www.reddit.com/r/HomeNetworking/comments/10odxwv/after_3_hours_i_fixed_php_error_2_fsockopen/ with no result. By the way, when I ssh into it it says "RTNETLINK answers: Invalid argument" but "pi-hole blocking enabled". Edit: made log collapsible for easier navigation
Edit: made log collapsible for easier navigation
|
The real issue is with the databse. Try re-initializing it:
Then check if the databses is accessible:
Output should be something like:
...and not an error. |
The output is exactly like this, yet the DNS service is still not running (when I click "Enable blocking" it changes to "Active" but whenever I reboot the dasboard page it shows again as "DNS service is not running"), the "There was a problem applying your settings. PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Unknown error) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:47 " error in the dashboard persists, and when I open the query log a pop-up says " Error, something went wrong! FTL is not running". |
Now there is a new problem: the phone dischanged, and after reboot the pihole does not respond at all! The dashboard does not open, and the SSH connection is refused. The IP is unchanged. How do I fix it? |
Sounds like filesystem corruption, redeploy the image. |
I got that over with, but the old problem persists. This part of the debug:
seems the most sus, so I've tried to attack it. When executing
Surely this can't be right. |
Probably using iptables given the device's age. |
This didn't solve the problem, and I've also found another one. From the debug log: Edit: made log collapsible for easier navigation
|
What's the output from: Your device is showing a load average of 24 which is very high. When you're SSH'd into the device, does it feel slow and is the device getting warm/hot? What version kernel is the device running? You may want to experiment with formatting the disk image as EXT3 or even EXT2. |
Tried ext2, the error did not go away.
16.0 11278 root sudo ps -eo pcpu,pid,user,args
Linux localhost 3.0.21-perf-g07d599d-00151-g0ff7ab2-dirty #1 SMP PREEMPT Fri Oct 12 13:14:26 CST 2012 armv7l armv7l armv7l GNU/Linux |
UPD: I reformatted to ext3 and updated pihole, the "readonly database" error is gone. The firewall error is not, and now there is a line in the log:
When ssh-ed into the device I can't ping 192.168.1.1:
And, seemingly as a result of this,
|
Try re-adding root, pihole, www-data and android user(s) back to these groups. If you are not using the default user (android) then add the one currently used as well:
|
usermod: user 'www-data' does not exist |
Name could be “lighttpd” I don’t recall what it is in CentOS 7. |
Edit: made log collapsible for easier navigation
Edit: made log collapsible for easier navigation``` *** [ INITIALIZING ] [i] 2023-08-20:22:14:24 debug log has been initialized. [i] System has been running for 1 days, 0 hours, 15 minutes*** [ INITIALIZING ] Sourcing setup variables *** [ DIAGNOSING ]: Core version *** [ DIAGNOSING ]: Web version *** [ DIAGNOSING ]: FTL version *** [ DIAGNOSING ]: lighttpd version *** [ DIAGNOSING ]: php version *** [ DIAGNOSING ]: Operating system *** [ DIAGNOSING ]: SELinux *** [ DIAGNOSING ]: FirewallD *** [ DIAGNOSING ]: Processor *** [ DIAGNOSING ]: Disk usage *** [ DIAGNOSING ]: Network interfaces and addresses *** [ DIAGNOSING ]: Network routing table *** [ DIAGNOSING ]: Networking [✓] IPv6 address(es) bound to the eth0 interface: [i] Default IPv4 gateway(s):
*** [ DIAGNOSING ]: Ports in use *** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain *** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain *** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds) WARN: Could not sendto() in send_dhcp_discover() (/tmp/tmp.VUwzCH0zQo/FTL/src/dhcp-discover.c:233): Network is unreachable *** [ DIAGNOSING ]: Pi-hole processes *** [ DIAGNOSING ]: Pi-hole-FTL full status *** [ DIAGNOSING ]: Lighttpd configuration test *** [ DIAGNOSING ]: Setup variables *** [ DIAGNOSING ]: Dashboard headers *** [ DIAGNOSING ]: Pi-hole FTL Query Database *** [ DIAGNOSING ]: Gravity Database *** [ DIAGNOSING ]: Info table version 15 ----- First 10 Gravity Domains ----- *** [ DIAGNOSING ]: Groups 0 1 Default 2022-01-17 02:20:54 2022-01-17 02:20:54 The default group *** [ DIAGNOSING ]: Domainlist (0/1 = exact white-/blacklist, 2/3 = regex white-/blacklist) *** [ DIAGNOSING ]: Clients *** [ DIAGNOSING ]: Adlists 1 1 0 https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts 2022-01-17 02:20:54 2022-01-17 02:20:54 Migrated from /etc/pihole/adlists.list *** [ DIAGNOSING ]: contents of /etc/pihole -rw-r--r-- 1 root root 44 Oct 6 2022 /etc/pihole/custom.list -rw-r--r-- 1 root root 65 Aug 20 03:06 /etc/pihole/local.list -rw-r--r-- 1 root root 241 Sep 8 2022 /etc/pihole/logrotate -rw-rw-r-- 1 pihole root 146 Aug 20 22:13 /etc/pihole/pihole-FTL.conf -rw-r--r-- 1 root root 431 Aug 20 14:21 /etc/pihole/versions *** [ DIAGNOSING ]: contents of /etc/dnsmasq.d -rw-r--r-- 1 root root 1.5K Aug 20 22:13 /etc/dnsmasq.d/01-pihole.conf -rw-r--r-- 1 root root 2.2K Aug 19 23:03 /etc/dnsmasq.d/06-rfc6761.conf *** [ DIAGNOSING ]: contents of /etc/lighttpd -rw-r--r-- 1 root root 0 Aug 19 23:01 /etc/lighttpd/external.conf -rw-r--r-- 1 root root 3.5K Aug 19 23:03 /etc/lighttpd/lighttpd.conf *** [ DIAGNOSING ]: contents of /etc/lighttpd/conf.d -rw-r--r-- 1 root root 4.1K Aug 19 22:29 /etc/lighttpd/conf.d/pihole-admin.conf *** [ DIAGNOSING ]: contents of /etc/lighttpd/conf-enabled *** [ DIAGNOSING ]: contents of /etc/cron.d -rw-r--r-- 1 root root 1.7K Aug 19 22:29 /etc/cron.d/pihole *** [ DIAGNOSING ]: contents of /var/log/lighttpd -rw-r--r-- 1 lighttpd lighttpd 604 Aug 20 21:33 /var/log/lighttpd/error-pihole.log -----tail of error-pihole.log------ *** [ DIAGNOSING ]: contents of /var/log/pihole -rw-r--r-- 1 pihole pihole 7.1K Aug 20 22:13 /var/log/pihole/FTL.log -----tail of FTL.log------ *** [ DIAGNOSING ]: contents of /dev/shm *** [ DIAGNOSING ]: contents of /etc -rw-r--r-- 1 root root 24 Aug 19 23:03 /etc/dnsmasq.conf -rw-r--r-- 1 root root 48 Aug 20 21:32 /etc/resolv.conf *** [ DIAGNOSING ]: Pi-hole diagnosis messages *** [ DIAGNOSING ]: Locale *** [ DIAGNOSING ]: Pi-hole log -----tail of pihole.log------ [✓] ** FINISHED DEBUGGING! **
|
Looks like you need to compile a newer pihole-FTL binary, or roll back to an older version of CORE and WEB
Check https://github.com/DesktopECHO/OTL to see if that helps. I have not tried compiling FTL under CentOS in a long time, no idea if this still works. |
Edit: made log collapsible for easier navigation
Which versions should I roll back to? |
This might be fixable with a newer assembler (yasm is in EPEL)
|
Rolled back to core 5.13 and web 5.16, now it seems to be working properly! Thank you for your support, that's been one hell of a ride! |
I think congratualtions are in order -- This is one of the lowest-end Android devices anyone has been able to get working with Pi-hole! |
FYI -- I updated the disk image of Pi-hole on CentOS 7 with the most recent version:
|
It seems that it doesn't have the right glibc version. |
How so? If you don't run 'p4a-install` then the versions pre-installed will work, which (at this time anyway) is the latest version of Pi-hole. |
p4a-install still gives the same
|
I have figured out the algorithm for the (re)-deployment (might be useful if the container corrupts when the host device is rebooted, or for new users):
Expected behavior: you can now delete the warning, but can't enable pi-hole yet.
Stop and restart the container. Expected behavior: now pi-hole works but cannot filter anything.
Set upstream DNS servers (DON'T FORGET THIS! BY DEFAULT NONE ARE SET). Set pi-hole's IP as your router's DNS server. Reboot the router.
|
Doesn't the new image work out-of-the-box before running Unbound is already configured to be upstream DNS as As far as your build error goes, you can try using GCC 10 to see if that gives a better result. Again, this compiled from source without issue on my ARMv7 device so I'm not sure what's going on.
|
No, there's the "read-only database" error and the glibc error (and you can't update glibc to the needed version with yum)
It doesn't work, not out of the box at least, when starting the container there's an error message about unbound: |
I want to deploy a Pihole on a Huawei U8950-1 with Android 4.0.4, which creates some limitations. Firstly, because of the Android version I have to use Linux Deploy 2.5.0. Secondly, because it only has about 1 GB of spare memory, I have to use an SD card (it's an 8GB card formatted to FAT32, if it matters). So I installed the source image to the root of the SD card (/mnt/sdcard2/p4a17.tgz) and set /mnt/sdcard2/linux.img as the installation path, image size is 4000 MB. When installing I get the error "mount: mounting /dev/block/loop0 on /data/local/mnt failed: Device or resource busy". Here is the full log (with debug and trace mode):
Edit: made log collapsible for easier navigation
The text was updated successfully, but these errors were encountered: