# /lib/x86\_64-linux-gnu/libc.so.6: version \`GLIBC\_2.28' not found

**URL:** https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506
**Category:** Help
**Created:** [September 2, 2022, 10:27pm UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506 "2022-09-02T22:27:34Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![tweiner](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/t/a4c791/32.png) [@tweiner](https://discourse.pi-hole.net/u/tweiner)
#### Post date: [September 2, 2022, 10:27pm UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/1 "2022-09-02T22:27:34Z")

</div>

I am running PI-hole in a VM under Truenas 13 - just upgraded from 12 to 13

proceeded to update pihole by logging in. Here is the messages for the execution of the upgrade.

```auto
tony@pihole01:~$ pihole -up
  [✓] Update local cache of available packages
  [i] Existing PHP installation detected : PHP version 7.2.24-0ubuntu0.18.04.12
  [✓] Checking for git
  [✓] Checking for iproute2
  [✓] Checking for dialog
  [✓] Checking for ca-certificates

  [i] Checking for updates...
  [i] Pi-hole Core: up to date
  [i] Web Interface: up to date
/usr/bin/pihole-FTL: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /usr/bin/pihole-FTL)
  [i] FTL: update available

  [i] FTL out of date, it will be updated by the installer.

  [✓] Root user check

```

---

<div class="post-metadata">

### Author: ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)
#### Post date: [September 2, 2022, 10:31pm UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/2 "2022-09-02T22:31:33Z")

</div>

Please upload a debug log and post **just the token URL** that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

```auto
pihole -d

```

or do it through the Web interface:

_ **Tools \> Generate Debug Log** _

---

<div class="post-metadata">

### Author: ![gboone](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/g/90ced4/32.png) [@gboone](https://discourse.pi-hole.net/u/gboone)
#### Post date: [September 3, 2022, 4:10am UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/3 "2022-09-03T04:10:30Z")

</div>

I am also getting this error about `/usr/bin/pihole-FTL: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.28 not found (required by /usr/bin/pihole-FTL)` after updating on Ubuntu 18.04. It causes the `pihole-FTL` service to fail and no DNS resolution.

```auto
~$ ldd --version
ldd (Ubuntu GLIBC 2.27-3ubuntu1.6) 2.27

```

I updated the VM first with recent OS updates.

Debug for the pi-hole setup BEFORE update with error: [https://tricorder.pi-hole.net/rlhTBXjR/](https://tricorder.pi-hole.net/rlhTBXjR/)

Thanks for having a look. I can provide more info later tomorrow if needed.

---

<div class="post-metadata">

### Author: ![Carlo\_D](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/carlo_d/32/32332_2.png) [@Carlo\_D](https://discourse.pi-hole.net/u/Carlo_D)
#### Post date: [September 3, 2022, 8:53am UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/6 "2022-09-03T08:53:16Z")

</div>

I have the same problem **pihole-FTL[7186]: /usr/bin/pihole-FTL: /lib/x86\_64-linux-gnu/libc.so.6: version `GLIBC\_2.28' not found (required by /usr/bin/pihole-FTL)**  
after upgrade pihole.

i updated the vm before updating pihole  
Debug pihole here: [https://tricorder.pi-hole.net/sN9EuPnr/](https://tricorder.pi-hole.net/sN9EuPnr/)

Thx

---

<div class="post-metadata">

### Author: ![yubiuser](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/yubiuser/32/12100_2.png) [@yubiuser](https://discourse.pi-hole.net/u/yubiuser)
#### Post date: [September 3, 2022, 9:26am UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/8 "2022-09-03T09:26:35Z")

</div>

> <https://github.com/pi-hole/FTL/issues/1420>
>
> \### Versions
> 
> \- Pi-hole: 5.12
> \- AdminLTE: 5.14.1
> \- FTL: 5.17
> 
> \### Platf…orm
> 
> \- OS and version: Ubuntu 18.04.6 LTS (GNU/Linux 4.15.0-122-generic x86\_64)
> 
> \- Platform: Intel NUC
> 
> \### 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:
> 
> 1. Attempt to start: \`sudo service pihole-FTL start\`
> 2. Check \`systemctl status pihole-FTL.service\`:
> 
> \`\`\`● pihole-FTL.service - LSB: pihole-FTL daemon
> Loaded: loaded (/etc/init.d/pihole-FTL; generated)
> Active: failed (Result: exit-code) since Sat 2022-09-03 08:42:31 UTC; 19s ago
> Docs: man:systemd-sysv-generator(8)
> Process: 3601 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=1/FAILURE)
> 
> Sep 03 08:42:31 nuc systemd\[1\]: Starting LSB: pihole-FTL daemon...
> Sep 03 08:42:31 nuc pihole-FTL\[3601\]: Not running
> Sep 03 08:42:31 nuc su\[3637\]: Successful su for pihole by root
> Sep 03 08:42:31 nuc su\[3637\]: + ??? root:pihole
> Sep 03 08:42:31 nuc su\[3637\]: pam\_unix(su:session): session opened for user pihole by (uid=0)
> Sep 03 08:42:31 nuc pihole-FTL\[3601\]: /usr/bin/pihole-FTL: /lib/x86\_64-linux-gnu/libc.so.6: version \`GLIBC\_2.28' not found (r
> Sep 03 08:42:31 nuc su\[3637\]: pam\_unix(su:session): session closed for user pihole
> Sep 03 08:42:31 nuc systemd\[1\]: pihole-FTL.service: Control process exited, code=exited status=1
> Sep 03 08:42:31 nuc systemd\[1\]: pihole-FTL.service: Failed with result 'exit-code'.
> Sep 03 08:42:31 nuc systemd\[1\]: Failed to start LSB: pihole-FTL daemon.
> \`\`\`
> 
> \## Debug Token
> 
> \- URL: https://tricorder.pi-hole.net/75lSJdql/
> 
> 
> 
> \### Additional context
> 
> It looks like the update to glibc 2.28 breaks compatibility with Ubuntu 18.04 LTS (EOL 2028).
> 
> \`ldd --version\`:
> 
> \`\`\`
> ldd (Ubuntu GLIBC 2.27-3ubuntu1.6) 2.27
> Copyright (C) 2018 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> Written by Roland McGrath and Ulrich Drepper.
> \`\`\`
> 
> 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.

---

<div class="post-metadata">

### Author: ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)
#### Post date: [September 3, 2022, 10:32am UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/10 "2022-09-03T10:32:38Z")

</div>

Please run

```auto
pihole checkout ftl v5.16.3

```

to get back to a working version ~~until we have found a permanent solution to this.~~ ( **edit** : see below)

When you see an error like

> [@Viald](#):
>
> ```auto
> pihole-FTL: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by pihole-FTL)
> 
> ```

please

> [@yubiuser](#):
>
> modify line 171 of `/opt/pihole/piholeCheckOut.sh` to read `oldbranch="$(pihole-FTL -b || echo master)`
> 
> and run the `checkout` command again.

* * *

**edit** We decided that supporting very old operating system releases (where there is _at least_ one stable newer version) can be too much at times. You can run your Pi-hole completely fine pinned to this version until you decide to upgrade the underlying system. At some point you will have to, anyway. I'm sorry to say this but we're a small team and all are volunteers (as in: other jobs pay our daily bread) and it seems better to make such a decision rather than trying to fit in everywhere and possibly not doing it right.

---

<div class="post-metadata">

### Author: ![Viald](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/v/b38774/32.png) [@Viald](https://discourse.pi-hole.net/u/Viald)
#### Post date: [September 3, 2022, 11:05am UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/17 "2022-09-03T11:05:10Z")

</div>

Not possible due to the same issue.

root@server:~# pihole checkout ftl v5.16.3  
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

pihole-FTL: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC\_2.28' not found (required by pihole-FTL)

---

<div class="post-metadata">

### Author: ![yubiuser](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/yubiuser/32/12100_2.png) [@yubiuser](https://discourse.pi-hole.net/u/yubiuser)
#### Post date: [September 3, 2022, 11:18am UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/18 "2022-09-03T11:18:35Z")

</div>

Please modify line 171 of `/opt/pihole/piholeCheckOut.sh` to read `oldbranch="$(pihole-FTL -b || echo master)`

and run the `checkout` command again.

---

<div class="post-metadata">

### Author: ![Viald](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/v/b38774/32.png) [@Viald](https://discourse.pi-hole.net/u/Viald)
#### Post date: [September 3, 2022, 11:19am UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/19 "2022-09-03T11:19:51Z")

</div>

Done.It works.  
Thank you.

---

<div class="post-metadata">

### Author: ![tweiner](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/t/a4c791/32.png) [@tweiner](https://discourse.pi-hole.net/u/tweiner)
#### Post date: [September 3, 2022, 4:21pm UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/21 "2022-09-03T16:21:29Z")

</div>

I have an interesting problem. This instance of Pi-hole is running as a VM on a Truenas server. Probably because I am a noob. I can not edit the file because I can not figure out the su pw.

I am also running a backup on a Pi but am not updating that until we know what is happening.

Thank you all for your help.

YFNN (your friendly neighborhood noob)

---

<div class="post-metadata">

### Author: ![Carlo\_D](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/carlo_d/32/32332_2.png) [@Carlo\_D](https://discourse.pi-hole.net/u/Carlo_D)
#### Post date: [September 3, 2022, 4:36pm UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/22 "2022-09-03T16:36:11Z")

</div>

Thanks for the solution, for the moment I have restored the VM from the backup until the final solution

---

<div class="post-metadata">

### Author: ![voytek](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/v/d26b3c/32.png) [@voytek](https://discourse.pi-hole.net/u/voytek)
#### Post date: [September 5, 2022, 1:49am UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/25 "2022-09-05T01:49:18Z")

</div>

thanks, I've got 'same' problem on Centos Linux 3.10.0-1160.76.1.el7.centos.plus.x86\_64 #1 SMP Tue Aug 16 14:59:44 UTC 2022 x86\_64 x86\_64 x86\_64 GNU/Linux

running above fixed it, thank you

```auto
# pihole checkout ftl v5.16.3
  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

pihole-FTL: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by pihole-FTL)
  [✓] Branch v5.16.3 exists
  [i] Switching to branch: "v5.16.3" from "master"
  [✓] Downloading and Installing FTL
  [✓] Restarting pihole-FTL service...
  [✓] Enabling pihole-FTL service to start on reboot...

```

now I have it running as follows:

- **Pi-hole** [v5.12](https://github.com/pi-hole/pi-hole/releases/v5.12)
- **FTL**
- **Web Interface** [v5.14.2](https://github.com/pi-hole/AdminLTE/releases/v5.14.2)

if you need any debug log or anything, pls let me know, thanks

---

<div class="post-metadata">

### Author: ![slm](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/slm/32/32383_2.png) [@slm](https://discourse.pi-hole.net/u/slm)
#### Post date: [September 5, 2022, 3:55pm UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/26 "2022-09-05T15:55:13Z")

</div>

Ran into the same issue.

OS: Linux pi-hole1 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux

Your debug token is: [https://tricorder.pi-hole.net/N4FrxejD/](https://tricorder.pi-hole.net/N4FrxejD/)

I too was able to work around this issue by editing this file:

```auto
root@pi-hole1:~ # cat --number /opt/pihole/piholeCheckout.sh | head -180 | tail +170
   170 path="${2}/${binary}"
   171 oldbranch="$(pihole-FTL -b || echo master)"
   172
   173 if check_download_exists "$path"; then
   174 echo " ${TICK} Branch ${2} exists"
   175 echo "${2}" > /etc/pihole/ftlbranch
   176 chmod 644 /etc/pihole/ftlbranch
   177 echo -e " ${INFO} Switching to branch: \"${2}\" from \"${oldbranch}\""
   178 FTLinstall "${binary}"
   179 restart_service pihole-FTL
   180 enable_service pihole-FTL
root@pi-hole1:~ #

```

Also notice the above mentions of the filename didn't match what I had on my box, my file is called `/opt/pihole/piholeCheckout.sh`.

---

<div class="post-metadata">

### Author: ![Lavarocker](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/l/41988e/32.png) [@Lavarocker](https://discourse.pi-hole.net/u/Lavarocker)
#### Post date: [September 7, 2022, 4:54pm UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/27 "2022-09-07T16:54:13Z")

</div>

The above instructions worked, thank you.

Since we are using a custom FTL now and won't receive notifications of an fixed new version, how/when will we know it's been fixed so we can undo the temp fix?

Thanks

---

<div class="post-metadata">

### Author: ![DanSchaper](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/danschaper/32/91_2.png) [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)
#### Post date: [September 7, 2022, 5:40pm UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/28 "2022-09-07T17:40:46Z")

</div>

> [@Lavarocker](#):
>
> won't receive notifications of an fixed new version

The fix is to update your OS. There won't be a new version of `FTL` that works.

---

<div class="post-metadata">

### Author: ![Skye20](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/s/94ad74/32.png) [@Skye20](https://discourse.pi-hole.net/u/Skye20)
#### Post date: [September 13, 2022, 12:15am UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/30 "2022-09-13T00:15:39Z")

</div>

Once we update our OS, what is the command to get back onto the main branch again?

Thanks

---

<div class="post-metadata">

### Author: ![yubiuser](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/yubiuser/32/12100_2.png) [@yubiuser](https://discourse.pi-hole.net/u/yubiuser)
#### Post date: [September 13, 2022, 4:34am UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/31 "2022-09-13T04:34:05Z")

</div>

`pihole checkout master`

---

<div class="post-metadata">

### Author: ![Carlo\_D](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/carlo_d/32/32332_2.png) [@Carlo\_D](https://discourse.pi-hole.net/u/Carlo_D)
#### Post date: [September 13, 2022, 1:03pm UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/32 "2022-09-13T13:03:57Z")

</div>

I upgraded the OS from ubuntu 18.04 to ubuntu 20.04.5 but nothing has changed it keeps giving error

---

<div class="post-metadata">

### Author: ![rdwebdesign](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/rdwebdesign/32/51363_2.png) [@rdwebdesign](https://discourse.pi-hole.net/u/rdwebdesign)
#### Post date: [September 24, 2022, 11:11pm UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/33 "2022-09-24T23:11:23Z")

</div>

Did you executed an in-place upgrade from 18.04 to 20.04 or you did a fresh install of ubuntu 20.04?

---

<div class="post-metadata">

### Author: ![Carlo\_D](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/carlo_d/32/32332_2.png) [@Carlo\_D](https://discourse.pi-hole.net/u/Carlo_D)
#### Post date: [September 25, 2022, 7:09am UTC](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506/34 "2022-09-25T07:09:02Z")

</div>

I did a full system upgrade, but nothing has changed. I did a clean install of ubuntu 22.04 and at that point I was able to put the new version

[Next page](https://discourse.pi-hole.net/t/lib-x86-64-linux-gnu-libc-so-6-version-glibc-2-28-not-found/57506.md?page=2)
