This seems to work (not sure if this is ok):
- goto
/var/www/html/admin git pull- goto
/etc/.pihole git pull- run
pihole updatechecker
You can use
pihole checkout core development-v6
and
pihole checkout web development-v6
This should also pull updates.
Sorry, I thought there was an issue with the compile. I'm an amateur at this and have probably missed something obvious. Here's what happens after compiling and when going from 5 to 6.
root@Pogo:~# echo "development-v6" | sudo tee /etc/pihole/ftlbranch
development-v6
root@PogoplugPro2:~# pihole checkout core development-v6
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
[✓] Fetching branches from https://github.com/pi-hole/pi-hole.git
[i] 17 branches available for Pi-hole Core
[✓] Switching to branch: 'development-v6' from 'refs/heads/master'
[i] Already up to date.
[i] Running installer to upgrade your installation
[✓] Root user check
.;;,.
.ccccc:,.
:cccclll:. ..,,
:ccccclll. ;ooodc
'ccll:;ll .oooodc
.;cll.;;looo:.
.. ','.
.',,,,,,'.
.',,,,,,,,,,.
.',,,,,,,,,,,,....
....''',,,,,,,'.......
......... .... .........
.......... ..........
.......... ..........
......... .... .........
........,,,,,,,'......
....',,,,,,,,,,,,.
.',,,,,,,,,'.
.',,,,,,'.
..'''.
[i] SELinux not detected
[✓] Update local cache of available packages
[✓] Checking apt-get for upgraded packages... up to date!
[i] Checking for / installing Required dependencies for OS Check...
[✓] Checking for grep
[✓] Checking for dnsutils
[✓] Checking for binutils
[✓] Supported OS detected
[i] Checking for / installing Required dependencies for this install script...
[✓] Checking for git
[✓] Checking for iproute2
[✓] Checking for dialog
[✓] Checking for ca-certificates
[i] Performing unattended setup, no dialogs will be displayed
[✓] Check for existing repository in /etc/.pihole
[✓] Update repo in /etc/.pihole
[✓] Check for existing repository in /var/www/html/admin
[i] Update repo in /var/www/html/admin...HEAD is now at be05b0f v5.21 (#2860)
[✓] Update repo in /var/www/html/admin
[i] Checking for / installing Required dependencies for Pi-hole software...
[✓] Checking for cron
[✓] Checking for curl
[✓] Checking for iputils-ping
[✓] Checking for psmisc
[✓] Checking for sudo
[✓] Checking for unzip
[✓] Checking for libcap2-bin
[✓] Checking for dns-root-data
[✓] Checking for libcap2
[✓] Checking for netcat-openbsd
[✓] Checking for procps
[✓] Checking for jq
[i] Checking for lshw (will be installed)
[i] Checking for bash-completion (will be installed)
[i] Waiting for package manager to finish (up to 30 seconds)
[i] Processing apt-get install(s) for: lshw bash-completion, please wait...
----------------------------------------------------------------------
Selecting previously unselected package bash-completion.
(Reading database ... 30216 files and directories currently installed.)
Preparing to unpack .../bash-completion_1%3a2.11-6_all.deb ...
Unpacking bash-completion (1:2.11-6) ...
Selecting previously unselected package lshw.
Preparing to unpack .../lshw_02.19.git.2021.06.19.996aaad9c7-2+b1_armel.deb ...
Unpacking lshw (02.19.git.2021.06.19.996aaad9c7-2+b1) ...
Setting up lshw (02.19.git.2021.06.19.996aaad9c7-2+b1) ...
Setting up bash-completion (1:2.11-6) ...
Processing triggers for man-db (2.11.2-2) ...
----------------------------------------------------------------------
[✓] Checking for user 'pihole'
[i] FTL Checks...
[✗] This processor architecture is not supported by Pi-hole (v5TE) [✗] Unable to download from ftl.pi-hole.net. Please check your Internet connection and try again later.
[✓] Installing scripts from /etc/.pihole
[i] Installing configs from /etc/.pihole...
[✓] Installing latest Cron script
[i] Installing latest logrotate script...
[i] Existing logrotate file found. No changes made.
[✓] man pages installed and database updated
[i] Testing if systemd-resolved is enabled
[i] Systemd-resolved is not enabled
Gravity temporary directory does not exist or is not a writeable directory, falling back to /tmp.
[i] Restarting services...
[✓] Enabling pihole-FTL service to start on reboot...
[✓] Restarting pihole-FTL service...
Gravity temporary directory does not exist or is not a writeable directory, falling back to /tmp.
[i] Creating new gravity database
Error: unable to open database "pihole-FTL: invalid option -- '--config'
Command: 'pihole-FTL --config -q files.gravity'
Try 'pihole-FTL --help' for more information": unable to open database file
[✗] Unable to create pihole-FTL: invalid option -- '--config'
Command: 'pihole-FTL --config -q files.gravity'
Try 'pihole-FTL --help' for more information
[✗] Error creating new gravity database. Please contact support.
[✗] Unable to migrate to database. Please contact support.
Error: Unable to complete update, please contact support
Probably best to ask how @kennywest got it fully working.
And I agree @yubiuser's way is better until we have a supported way of including a self-complicated FTL binary on your own.
@bluzfanmr1 those errors are normal since there are no binaries available for the pogoplug's CPU architecture.
What you need to do after these errors is just install the binaries you compiled yourself using make install.
After that you should be able to restart the service using service pihole-FTL restart.
1 Like
I knew it had to be something simple I was missing and I got it, thank you very much for the guidance!
I had trouble finding the dashboard at first and had to go to <Pi-Hole IP>:8080/admin/ to find it. I have always used <Pi-Hole IP>/admin previously but that wasn't working.
Note to myself here for future reference...no more lighttpd so if it's installed coming from 5 to 6 it will change the port:
https://discourse.pi-hole.net/t/pi-hole-v6-using-http-instead-of-https/67098/6?u
Indeed, the sqlite code is the cullprit. I also transferred my installation from USB-disk to internal SSD storage (pogoplugs don't have this, but they do have an internal SATA port and if you're handy with a soldering iron, you can install an internal SSD -> Adding a SATA SSD to a PogoPlug Pro).
Anyway, when I repeat the process on internal SSD and build the FTL binary locally, it (only) takes 2 hours or so ... which is better than larger part of the day on USB-disk 
You'll notice that future compilations will take much less time as we've specifically tailored the build process to use the already compiled SQLite3 library from build cache in the future. Unless, of course, when there is an update to SQLite3 itself but this didn't really happen very often (3-5 times a year, approximately).
1 Like