pihole-FTL can't execute (GLIBC_2.14 not found)

Help
1

Please follow the below template, it will help us to help you!

Expected Behaviour:

pihole-FTL started

Actual Behaviour:

pihole-FTL dont start and FTL is offline

Debug Token:

l7qiw5zq5f

More information

root:~# uname -a
Linux XXXX.ovh.net 2.6.32-042stab123.9 #1 SMP Thu Jun 29 13:01:59 MSK 2017 x86_64 GNU/Linux

root:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.11 (wheezy)
Release: 7.11
Codename: wheezy

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

[i] FTL out of date

[i] FTL Checks...
[✓] Detected x86_64 architecture
[i] Checking for existing FTL binary...
/usr/bin/pihole-FTL: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /usr/bin/pihole-FTL)
[✓] Downloading and Installing FTL

[i] Web Interface: up to date
/usr/bin/pihole-FTL: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /usr/bin/pihole-FTL)

root:~# ldd -v /usr/bin/pihole-FTL
/usr/bin/pihole-FTL: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /usr/bin/pihole-FTL)
linux-vdso.so.1 => (0x00007ffc4a0dc000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f66bf4f9000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f66bf16c000)
/lib64/ld-linux-x86-64.so.2 (0x00007f66bfa0d000)

    Version information:
    /usr/bin/pihole-FTL:
            libpthread.so.0 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libpthread.so.0
            libc.so.6 (GLIBC_2.3) => /lib/x86_64-linux-gnu/libc.so.6
            libc.so.6 (GLIBC_2.14) => not found
            libc.so.6 (GLIBC_2.8) => /lib/x86_64-linux-gnu/libc.so.6
            libc.so.6 (GLIBC_2.4) => /lib/x86_64-linux-gnu/libc.so.6
            libc.so.6 (GLIBC_2.3.4) => /lib/x86_64-linux-gnu/libc.so.6
            libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6
    /lib/x86_64-linux-gnu/libpthread.so.0:
            ld-linux-x86-64.so.2 (GLIBC_2.2.5) => /lib64/ld-linux-x86-64.so.2
            ld-linux-x86-64.so.2 (GLIBC_2.3) => /lib64/ld-linux-x86-64.so.2
            ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2
            libc.so.6 (GLIBC_2.3.2) => /lib/x86_64-linux-gnu/libc.so.6
            libc.so.6 (GLIBC_PRIVATE) => /lib/x86_64-linux-gnu/libc.so.6
            libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6
    /lib/x86_64-linux-gnu/libc.so.6:
            ld-linux-x86-64.so.2 (GLIBC_2.3) => /lib64/ld-linux-x86-64.so.2
            ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2

root:~# apt-get update;apt-get install libc6 libc6-dev
=> Nothing to update

2

We do not officially support Wheezy any longer.

Note that we have to abandon old operating systems at some point to be able to move forward and use new functionality.

Wheezy has been superseded by Jessie already in 2015, and Jessie has already been superseded by Stretch.

The kernel you are using 2.6.32 dates back to December 2009. You should consider upgrading soon, mainly also to be able continuously receive (critical) security updates for your system.

See also

apt-cache show libc6 | grep Version

Modern systems should at least run version 2.15 (my PC is running 2.23)

3

Ok I understand. Thanks for your quick reply!
My version is 2.13-38+deb7u12, you are right, it's too old :confused: