pihole-FTL refuses to start after upgrade - OSMC

I'm having a similar problem to others following the 3.0 upgrade, however despite spending an hour or two trawling threads on here and over on Reddit I'm not further forward so here goes...

My pihole is running/blocking ads, however FTL shows as offline via the admin interface and fails to start. Browser cache etc. has been cleared. Another notable issue is the footer that continuously advises me an FTL update is available.

I've tried pihole -r which runs without error, then a reboot to no avail.

I've tried pihole -up numerous times, the notable entries being these at the end of the install:

/opt/pihole/update.sh: line 80: /usr/bin/pihole-FTL: No such file or directory
::: FTL:            update available
:::
::: FTL out of date
:::
::: Downloading latest version of FTL...
:::  Detected ARM-hf architecture (armv6 or lower)
:::  Using ARM binary
:::  Installing FTL... transferred... done.
:::
::: Web Interface:  up to date
/opt/pihole/update.sh: line 209: /usr/bin/pihole-FTL: No such file or directory

I can try manually starting/restarting pihole-FTL again to no avail (no errors returned).

If I do sudo pihole-FTL running, I get:

sudo: unable to execute /usr/bin/pihole-FTL: No such file or directory

The file does seem to exist.

pihole -d gives a couple of entries of note:

:::  ---= Checking IPv4 Stack
:::       IPv4 addresses located on eth0
:::        Pinging default IPv4 gateway: Gateway did not respond.

:::  ---= Daemon Process Information
:::     Checking 4711 port for pihole-FTL listener.
:::  Failure: IPv4 Port not in use

My debug token is 2cd970sdx7.

Any help that can be offered would be very much appreciated.

To start, can you run a pihole -r and repair. It appears that you don't have a copy of the FTL binary installed on your system. And after you run the repair, check your /tmp directory and see if there are any FTL named binaries or hash files in there.

Thanks.

I've just run pihole -r again, which seemed to go without error. Lines pertaining to FTL as follows:

::: Downloading latest version of FTL...
:::  Detected ARM-hf architecture (armv6 or lower)
:::  Using ARM binary
:::  Installing FTL... transferred... done.

::: Starting pihole-FTL service... done.
:::
::: Enabling pihole-FTL service to start on reboot... done.
::: done.

Haven't rebooted yet but situation seems the same. The following binaries are in /tmp:

pihole-FTL-arm-linux-gnueabi
pihole-FTL-arm-linux-gnueabi.sha1

Aha same issue as on XBian.
Try below one:

sudo ln -s /lib/arm-linux-gnueabihf/ld-linux.so.3 /lib/ld-linux.so.3

Start here up with:

sudo /etc/init.d/pihole-FTL restart

If the symlinking fails because file not exist, search if you've already got it installed with:

sudo dpkg -S ld-linux.so.3

Use the location of the file displayed as replacement for the symlink command eg:

sudo ln -s /some/lib/location/ld-linux.so.3 /lib/ld-linux.so.3

Updated with the OS running on this install. OSMC.

I would suggest waiting a bit on the linking of libraries, that may cause other issues with process running on the device and would be better solved with a more intelligent detection system.

Roger :wink:

0987654321234567890

Thanks both, will hang fire on the symlinking and see how things pan out over the coming days/weeks. At least the ad-blocking's running in the interim.

Which SBC hardware are you running on? A Rasbperry or another kind?

The problem is not that pihole-FTL is not found, but the dynamic linker which is the part of an operating system that loads and links the shared libraries needed by an executable when it is executed. This happens because it is not located where pihole-FTL is expecting it.

It seems OSMC (as Xbian, too) places the interpreter in a non-standard place. Try identifying where your linker is. @deHakkelaar found it in /lib/arm-linux-gnueabihf/ld-linux.so.3 on Xbian. The path may be similar for you.

Once you found it, try something like

LD_LIBRARY_PATH=/lib/arm-linux-gnueabihf pihole-FTL test

Note that this is 100% untested but should not harm (it may just not work).

Yeah, Raspberry. It's a fairly archaic beast too, one of the original Model B's I think.

Same location:

$ dpkg -S ld-linux.so.3
libc6:armhf: /lib/arm-linux-gnueabihf/ld-linux.so.3

Assuming I'm entering that verbatim (Linux isn't my forté), then I'm getting:

/usr/bin/pihole-FTL: No such file or directory

Hmm on base Raspbian:

$ stat -c '%F : %N' /lib/ld-linux.so.3
symbolic link : ‘/lib/ld-linux.so.3’ -> ‘/lib/ld-linux-armhf.so.3’

$ stat -c '%F : %N' /lib/ld-linux-armhf.so.3
symbolic link : ‘/lib/ld-linux-armhf.so.3’ -> ‘arm-linux-gnueabihf/ld-2.19.so’

Could it be that "/lib/arm-linux-gnueabihf/ld-linux.so.3" is the newer version ?

EDIT: pew, at least it ends there:

$ stat -c '%F : %N' /lib/arm-linux-gnueabihf/ld-2.19.so
regular file : ‘/lib/arm-linux-gnueabihf/ld-2.19.so’

@bobpullen , have you tried symlinking ?
If doesnt work, its easy to remove:

sudo rm /lib/ld-linux.so.3

LOL , full circle:

$ stat -c '%F : %N' /lib/arm-linux-gnueabihf/ld-linux.so.3
symbolic link : ‘/lib/arm-linux-gnueabihf/ld-linux.so.3’ -> ‘ld-linux-armhf.so.3’

$ stat -c '%F : %N' /lib/arm-linux-gnueabihf/ld-linux-armhf.so.3
symbolic link : ‘/lib/arm-linux-gnueabihf/ld-linux-armhf.so.3’ -> ‘ld-2.19.so’

$ stat -c '%F : %N' /lib/arm-linux-gnueabihf/ld-2.19.so
regular file : ‘/lib/arm-linux-gnueabihf/ld-2.19.so’

I would choose the one indicated by apt:

$ sudo dpkg -S ld-linux.so.3
libc6:armhf: /lib/arm-linux-gnueabihf/ld-linux.so.3

Ps. Kodi+Pi-Hole bit heavy for a B+
How is OSMC faring ?
I have this watchdog running from one of my clients and it sometimes times out:

watch host pi.hole 10.0.0.100

So...

$ sudo ln -s /lib/arm-linux-gnueabihf/ld-linux.so.3 /lib/ld-linux.so.3
$ /usr/bin/pihole-FTL
FATAL: Opening of FTL log (/var/log/pihole-FTL.log) failed!
       Make sure it exists and is writeable by user osmc

Permissions as follows:

-rw-r--r-- 1 pihole pihole 0 May 3 21:51 pihole-FTL.log

So did:

$ sudo chown osmc:pihole /var/log/pihole-FTL.log
$ /usr/bin/pihole-FTL
FTL started!

Cleared browser cache, and loaded the dashboard. No update nag, all stats showing and everything's flying! :slight_smile:

Cheers :popcorn:

1234567890

It's not even a B+, I'm literally talking one of the first models off the shelf! :open_mouth:

OSMC does struggle, but I was only using it to stream from another device on the network, and now have Plex on a smart TV to do that job.

The pihole though is flawless, with ~25 devices on the LAN relying on it for resolution.

Thanks again for your help :+1:

Yeah am mistaken.
Mine is a plane B too.
The A was without net.
But reckon a Pi2 would have bit more beef.

Its looking like native OSMC support is going to need quite a few changes, new user, library locations, and a few other tweaks. Since it's not an officially supported OS, we can help out with tips as we come to them, but we may need to have some dialog with the OSMC maintainers to get a proper resolution. If an OSMC user wanted to post on their forums a few questions and see if they are open to discussions, it may make the process a bit smoother. The maintainer of that distro is quite a nice fellow from what I have read.

(I tried OSMC, but I run on Odroid for media and haven't had the time to sit down and figure out how to compile the source for my particular board.)

I think its Sam Nazarko (and appologies if I butchered the name, its from memory.)

Yeah Sam comes by the XBian chat regular for tea time :slight_smile:
If I see him again, i'll poke him :wink:

1 Like

I've seen him in the the Raspi Forums as well.