I am running Debian jessie in android using Linux Deploy app with containerization method as chroot, architecture as armhf.
After installing Pi-hole, The admin page shows me red in DNS, FTL-Offline, Load 12.54 8.7 6.98
Debug Token:
95icuri0f2
This is certainly one of the more exotic setups we've seen 
Are you sure you can open ports in that setup? FTL fails with this message:
[2017-08-17 18:10:46.544] Error opening socket
Share the output of these commands:
sudo service lighttpd status
sudo service dnsmasq status
After uninstalling and reinstalling Pi-hole, DNS is showing active but FTL is offline.
I ran those commands which reports
[ ok ] lighttpd is running
[ ok ] Checking DNS forwarder and DHCP Server: dnsmasq[....]] (running).
Run pihole -d for another debug token.
I tried 'service pihole-FTL restart', it says FTL started but it is not
#Debug token
bcqapieg3l
FTL did start, but it crashed. It's still unable to open a port (4711):
[2017-08-18 00:19:18.862] Error opening socket
is there a way to fix it.
What is the output from:
netstat -tulpn |grep -i ftl
'service pihole-FTL status' returns
/etc/init.d/pihole-FTL: line 69: status: command not found
I have opened pihole-FTL in /etc/init.d, I see that status() function is not written in it.
Whats you init system (systemv/systemd/upstart) ?
stat /sbin/init
/sbin/init --version
root@localhost:~# stat /sbin/init
File: '/sbin/init'
Size: 198832 Blocks: 400 IO Block: 4096 regular file
Device: 702h/1794d Inode: 42164 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2017-08-20 19:17:05.000000000 +0530
Modify: 2014-12-04 06:30:04.000000000 +0530
Change: 2017-08-20 19:17:05.748132853 +0530
Birth: -
root@localhost:~# /sbin/init --version
SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.29: No such file or directory
init (upstart 1.11)
Copyright (C) 2006-2013 Canonical Ltd., 2011 Scott James Remnant
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
##After unistalling upstart package
root@localhost:~# stat /sbin/init
File: '/sbin/init' -> '/lib/systemd/systemd'
Size: 20 Blocks: 0 IO Block: 4096 symbolic link
Device: 702h/1794d Inode: 40980 Links: 1
Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2017-08-20 19:51:26.000000000 +0530
Modify: 2017-04-09 03:15:22.000000000 +0530
Change: 2017-08-20 19:51:26.698816446 +0530
Birth: -
root@localhost:~# /sbin/init --version
Couldn't find an alternative telinit implementation to spawn.
there are options in init system 1. sysv 2. run-parts
, currently init selected is sysv, level is set to 3, init user is root, Async(Run the processes asynchronously) enabled.
Bit confusing the version command mentions "upstart" while settings display "sysv".
What if you disable SELinux before running the version command (user root) ?
setenforce 0
/sbin/init --version
To enable SELinux again:
setenforce 1
Also it could be that the "pihole-FTL" binary wont run on your arm architecture.
What is diaplayed with below one ?
uname -mr
Can you run the binary manually as user root ?
/usr/bin/pihole-FTL
To kill it again:
kill $(pidof pihole-FTL)
root@localhost:~# setenforce 0
setenforce: SELinux is disabled
root@localhost:~# /sbin/init --version
Couldn't find an alternative telinit implementation to spawn.
root@localhost:~# uname -mr
3.4.0-perf-gbccb33a armv7l
after using /usr/bin/pihole-FTL, FTL started but they show only loading symbol
root@localhost:~# netstat -tulpn |grep -i ftl
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 31440/pihole-FTL
new debug token is mw600y0brv
Regardless if your running upstart or sysv, you can have the "pihole-FTL" daemon start at boot with below one (run as user root):
update-rc.d pihole-FTL defaults
And check if she is listening with below one after a reboot:
netstat -nltup | grep 'Proto\|lighttpd\|dnsmasq\|pihole-FTL'
Not sure if Pi-hole needs some data in the log files first before displaying the graphs.
Have you checked the log files after browsing to a site on PC ... ?
less /var/log/pihole.log
less /var/log/pihole-FTL.log
yes after some browsing also they are still refreshing
root@localhost:~# less /var/log/pihole.log
Aug 21 09:05:37 dnsmasq[9924]: started, version 2.72 cachesize 10000
Aug 21 09:05:37 dnsmasq[9924]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect
Aug 21 09:05:37 dnsmasq[9924]: using nameserver 8.8.4.4#53
Aug 21 09:05:37 dnsmasq[9924]: using nameserver 8.8.8.8#53
Aug 21 09:05:37 dnsmasq[9924]: read /etc/hosts - 4 addresses
Aug 21 09:05:37 dnsmasq[9924]: failed to load names from /etc/pihole/black.list: No such file or directory
Aug 21 09:05:37 dnsmasq[9924]: read /etc/pihole/local.list - 2 addresses
Aug 21 09:05:40 dnsmasq[9924]: read /etc/pihole/gravity.list - 116855 addresses
Aug 21 09:05:40 dnsmasq[9924]: query[A] dns.msftncsi.com from 192.168.2.1
Aug 21 09:05:40 dnsmasq[9924]: forwarded dns.msftncsi.com to 8.8.4.4
Aug 21 09:05:40 dnsmasq[9924]: forwarded dns.msftncsi.com to 8.8.8.8
Aug 21 09:05:43 dnsmasq[9924]: reply dns.msftncsi.com is 131.107.255.255
Aug 21 09:05:43 dnsmasq[9924]: query[A] dns.msftncsi.com from 192.168.2.1
Aug 21 09:05:43 dnsmasq[9924]: cached dns.msftncsi.com is 131.107.255.255
Aug 21 09:05:48 dnsmasq[9924]: query[A] dns.msftncsi.com from 192.168.2.1
Aug 21 09:05:48 dnsmasq[9924]: cached dns.msftncsi.com is 131.107.255.255
Aug 21 09:05:48 dnsmasq[9924]: query[PTR] 22.2.168.192.in-addr.arpa from 127.0.0.1
Aug 21 09:05:48 dnsmasq[9924]: config 192.168.2.22 is NXDOMAIN
Aug 21 09:05:53 dnsmasq[9924]: query[A] dns.msftncsi.com from 192.168.2.1
Aug 21 09:05:53 dnsmasq[9924]: cached dns.msftncsi.com is 131.107.255.255
Aug 21 09:05:58 dnsmasq[9924]: query[A] dns.msftncsi.com from 192.168.2.1
Aug 21 09:05:58 dnsmasq[9924]: forwarded dns.msftncsi.com to 8.8.4.4
root@localhost:~# less /var/log/pihole-FTL.log
[2017-08-21 08:45:43.848] ########## FTL started! ##########
[2017-08-21 08:45:43.848] FTL branch: (no branch)
[2017-08-21 08:45:43.849] FTL hash: v2.10
[2017-08-21 08:45:43.849] FTL date: 2017-08-05 09:46:38 +0200
[2017-08-21 08:45:43.849] FTL user: pihole
[2017-08-21 08:45:43.849] Notice: Found no readable FTL config file
[2017-08-21 08:45:43.849] Using default settings
[2017-08-21 08:45:43.849] Starting config file parsing
[2017-08-21 08:45:43.849] SOCKET_LISTENING: only local
[2017-08-21 08:45:43.849] TIMEFRAME: Rolling 24h
[2017-08-21 08:45:43.850] QUERY_DISPLAY: Show queries
[2017-08-21 08:45:43.850] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2017-08-21 08:45:43.850] MAXDBDAYS: max age for stored queries is 365 days
[2017-08-21 08:45:43.850] Finished config file parsing
[2017-08-21 08:45:43.881] Found no other running pihole-FTL process
[2017-08-21 08:45:43.885] PID of FTL process: 26421
[2017-08-21 08:45:44.413] Gravity list entries: 116855
[2017-08-21 08:45:44.414] No blacklist present
[2017-08-21 08:45:44.414] No wildcard blocking list present
[2017-08-21 08:45:44.415] db_init() - Cannot open database (14): unable to open database file
[2017-08-21 08:45:44.416] Creating new (empty) database
[2017-08-21 08:45:44.431] Database initialized
[2017-08-21 08:45:44.431] Starting initial log file parsing
I found this in debug
::: ---= Daemon Process Information
::: Checking http port for lighttpd listener.
lsof: no pwd entry for UID 10202
lsof: no pwd entry for UID 10254
lsof: no pwd entry for UID 10254
lsof: no pwd entry for UID 10202
lsof: no pwd entry for UID 10254
lsof: no pwd entry for UID 10254
::: Correctly configured.
Try disabling SELinux for diagnosing:
setenforce 0
Ps. I corrected the netstat command typo.
same result even after disabling selinux
::: —= Daemon Process Information
::: Checking http port for lighttpd listener.
lsof: no pwd entry for UID 10202
lsof: no pwd entry for UID 10254
lsof: no pwd entry for UID 10254
lsof: no pwd entry for UID 10202
lsof: no pwd entry for UID 10254
lsof: no pwd entry for UID 10254
::: Correctly configured.