-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
glibc 2.28 requirement breaks compatibility with Ubuntu 18.04 LTS #1420
Comments
This issue has been mentioned on Pi-hole Userspace. There might be relevant details there: https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/8 |
Please run
until we have found a permanent solution. edit Updated the version, sorry for the typo. |
Hi, at least for me, that command gives the following output:
The problem is in the If I replace it with: the response will change to this:
|
@folti Sorry, I edited a missing |
@DL6ER Yes, now it works, thank you. |
This issue has been mentioned on Pi-hole Userspace. There might be relevant details there: https://discourse.pi-hole.net/t/psa-dropping-support-for-ubuntu-18-04/57523/1 |
I had the same problem, the steps I had to take were: Temporarily change system's DNS resolver in Change line 171 in Downgrade FTL with the command Change system's DNS resolver back to |
I first did this and later updated my machine to ubuntu 20. --- nvm... found it.. |
|
Can confirm running:
The fix mentioned above by @rar0ch works:
and re-running
works. I will disable automatic updates as I imagine that will pull back to master/latest update each time? |
This is a wise decision, as it is not recommended in any way to auto-update an essential network service without reading the release notes first. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days. |
The advise doesn't work. pihole checkout ftl v5.16.3 pihole-FTL: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.28' not found (required by pihole-FTL) Which makes sense.. pihole-FTL can't start due to missing GLIB .. And piholeCheckout.sh tries to run pihole-FTL to get some old-branch version. oldbranch="$(pihole-FTL -b)" actually needs to run the binary :) Just comment it out then it works. oldbranch="$(pihole-FTL -b) || echo master)" |
This is now completely broken and extremely difficult to fix with the given work around. The reason is because the files for all old versions previously hosted at ftl.pi-hole.net are now missing: I had to hack my way around it by downloading the files from https://github.com/pi-hole/FTL/releases/tag/v5.16.3 into my local web server, setup an SSL VirtualHost to spoof that domain locally, and then modify basic-install.sh so every curl to the hard-coded ftl.pi-hole-net site used the -k option to ignore the invalid certificate. In hindsight, I should have probably just changed basic-install.sh to look for the requested version in the github releases instead, but I didn't realize that until after I got it working this way. Don't forget to create /var/log/pihole and chown it to pihole:pihole. For some reason after installing the older version, that folder was gone and pihole-FTP was silently failing because it couldn't write to its log file. |
@ZizzyZizzy I've played with
|
As long as your are on x86, you could use the musl binary that is fully-static and completely independent of the installed glibc version. In the currently ongoing v6 development, we are looking at compiling the binaries for all of the major supported architectures batteries-included so glibc incompatibility should not happen again. |
I was able to swap out the download site from ftl.pihole.net to github by changing two lines in Full patch filediff --git a/automated install/basic-install.sh b/automated install/basic-install.sh
index 1f3002e..010661c 100755
--- a/automated install/basic-install.sh
+++ b/automated install/basic-install.sh
@@ -2090,7 +2090,7 @@ update_dialogs() {
}
check_download_exists() {
- status=$(curl --head --silent "https://ftl.pi-hole.net/${1}" | head -n 1)
+ status=$(curl --head --silent "https://github.com/pi-hole/FTL/releases/download/${1}" | head -n 1)
if grep -q "404" <<< "$status"; then
return 1
else
@@ -2230,7 +2230,7 @@ FTLinstall() {
if [[ "${ftlBranch}" == "master" ]];then
url="https://github.com/pi-hole/ftl/releases/latest/download"
else
- url="https://ftl.pi-hole.net/${ftlBranch}"
+ url="https://github.com/pi-hole/FTL/releases/download/${ftlBranch}"
fi
if curl -sSL --fail "${url}/${binary}" -o "${binary}"; then
|
Beginner question... How to I edit the piholeCheckout.sh? All things linux are new to me... |
Versions
Platform
Expected behavior
FTL loads.
Actual behavior / bug
FTL crashes on load:
pihole-FTL: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by pihole-FTL)
Steps to reproduce
Steps to reproduce the behavior:
sudo service pihole-FTL start
systemctl status pihole-FTL.service
:Debug Token
Additional context
It looks like the update to glibc 2.28 breaks compatibility with Ubuntu 18.04 LTS (EOL 2028).
ldd --version
:I have read that I need to do a full upgrade to fix this, but this may cause breaking changes with other services on this server.
The text was updated successfully, but these errors were encountered: