Start and report without lighttpd on BeagleBoard-xM (Ubuntu 18.04.1 LTS)
FTL seems to be offline
networking seems to be cause trouble with the network-tab
logging seems to be offline as well
https://tricorder.pi-hole.net/re3p2hpvx2
Hello together,
yesterday I installed the pi-hole v4.3-0-g1d43c0a but did not install lighttpd as well. There is an nginx running.
The pi-hole seems to work but there are a few things not going well:
FTL seems to be offline
networking seems to be cause trouble with the network-tab
logging seems to be offline as well
I checked a few things with the logging and found sqlite3 installed and ready. I studied the debug-log from the web-interface and hat no idea what is going wrong with networking.
Can anybody tell me where to look or what to change to get a completely working pi-hole on my beagleboard?
Many thanks
Max
BeagleBoard-xM
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
uname -r
4.19.8-armv7-x11
nginx -v
nginx version: nginx/1.14.0 (Ubuntu)
sqlite3 --version
3.22.0 2018-01-22 18:45:57
*** [ DIAGNOSING ]: Ports in use
[127.0.0.1:53] is in use by pihole-FTL
[[::1]:53] is in use by pihole-FTL
*:22 sshd (IPv4)
*:22 sshd (IPv6)
[*:80] is in use by lighttpd
[*:80] is in use by lighttpd
[*:80] is in use by lighttpd
[*:80] is in use by lighttpd
From above debug snippet, it appears lighttpd is running and listening on the default http port 80 TCP.nginx.
And it appears pihole-FTL is listening on the loopback interface (127.0.0.1 and ::1) but not on any IP's assigned to the physical interfaces.netstat should look like with default lighttpd installed (if "Local Address" is 0.0.0.0:.. or :::.. , it means listen on all IP's):
pi@noads:~ $ sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471[1-8] '
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 654/pihole-FTL
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 654/pihole-FTL
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 27433/lighttpd
tcp6 0 0 :::53 :::* LISTEN 654/pihole-FTL
tcp6 0 0 ::1:4711 :::* LISTEN 654/pihole-FTL
tcp6 0 0 :::80 :::* LISTEN 27433/lighttpd
udp 0 0 0.0.0.0:53 0.0.0.0:* 654/pihole-FTL
udp 0 0 0.0.0.0:67 0.0.0.0:* 654/pihole-FTL
udp6 0 0 :::53 :::* 654/pihole-FTL
Check for alien config files not belonging to Pi-hole and post here:
sudo grep -v '#\|^$' -R /etc/dnsmasq.* | sort
Many thanks for your reply!
sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471[1-8]'
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 434/connmand
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 5693/nginx: master
tcp6 0 0 ::1:53 :::* LISTEN 434/connmand
tcp6 0 0 :::80 :::* LISTEN 5693/nginx: master
udp 0 0 127.0.0.1:53 0.0.0.0:* 434/connmand
udp6 0 0 ::1:53 :::* 434/connmand
sudo grep -v '#\|^$' -R /etc/dnsmasq.* | sort
/etc/dnsmasq.conf:conf-dir=/etc/dnsmasq.d
/etc/dnsmasq.conf.old:conf-dir=/etc/dnsmasq.d
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/black.list
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/gravity.list
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/local.list
/etc/dnsmasq.d/01-pihole.conf:cache-size=10000
/etc/dnsmasq.d/01-pihole.conf:dhcp-ignore-names=tag:wpad-ignore
/etc/dnsmasq.d/01-pihole.conf:dhcp-name-match=set:wpad-ignore,wpad
/etc/dnsmasq.d/01-pihole.conf:interface=eth0
/etc/dnsmasq.d/01-pihole.conf:localise-queries
/etc/dnsmasq.d/01-pihole.conf:local-ttl=2
/etc/dnsmasq.d/01-pihole.conf:log-async
/etc/dnsmasq.d/01-pihole.conf:log-facility=/var/log/pihole.log
/etc/dnsmasq.d/01-pihole.conf:log-queries
/etc/dnsmasq.d/01-pihole.conf:no-resolv
/etc/dnsmasq.d/01-pihole.conf:server=208.67.220.220
/etc/dnsmasq.d/01-pihole.conf:server=208.67.222.222
As far as I get it, lighttpd does not run. And does pihole-FTL hide behind the 434/connmand?
jfb
June 22, 2019, 8:22pm
4
No. Pi-Hole should be shown as a separate process. Connmand is keeping FTL off the required ports.
If pihole-FTL is missing: can I start it seperately?
Switching off connman made FTL start. Great, thanks!
There is a small detail left: The Network-Tab
starts with an error. The Settings-Tab looks much better now:
So my remaining question is: Does the log (token
https://tricorder.pi-hole.net/shovzhkc5n , without email here this time)
pihole_debug.txt (16.4 KB)
show an easy way to get rid of this web-front-end-failure?
1 Like
Find out your PHP version:
pi@noads:~ $ php-cgi -v
PHP 7.0.33-0+deb9u3 (cgi-fcgi) (built: Mar 8 2019 10:01:24)
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies
with Zend OPcache v7.0.33-0+deb9u3, Copyright (c) 1999-2017, by Zend Technologies
Check if below two PHP mods are installed (might need to replace the 7.0 bit with your version of PHP):
pi@noads:~ $ apt policy php7.0-json php7.0-sqlite3
php7.0-json:
Installed: 7.0.33-0+deb9u3
Candidate: 7.0.33-0+deb9u3
Version table:
*** 7.0.33-0+deb9u3 500
500 http://raspbian.raspberrypi.org/raspbian stretch/main armhf Packages
100 /var/lib/dpkg/status
php7.0-sqlite3:
Installed: 7.0.33-0+deb9u3
Candidate: 7.0.33-0+deb9u3
Version table:
*** 7.0.33-0+deb9u3 500
500 http://raspbian.raspberrypi.org/raspbian stretch/main armhf Packages
100 /var/lib/dpkg/status
And check if enabled:
pi@noads:~ $ php-cgi -m
[PHP Modules]
[..]
json
sqlite3
If not installed:
sudo apt install php7.0-json php7.0-sqlite3
And check if enabled again with php-cgi -m .
pi@noads:~ $ sudo phpenmod json sqlite3
pi@noads:~ $
And check again with php-cgi -m .nginx to apply:
sudo service nginx restart
Did you switch off connmand entirely or just the DNS-proxy part like described in the Archlinux wiki link ?
Thank you, thank you, thank you! Following your suggestions step by step the Pi-hole works for my little network. Extremely cool!
I disabeled connmand entirely. Still BeagleBoard comes up asking DHCP for an IP (not optimal) but without connmand pihole-FTL works. So I try not to reboot the board
1 Like
Did you try the wiki steps ?
No, googeling arroud showed systemctl-related post I followed and applied to my problem (connmand).
There are just too many network managers/manglers around that do stuff their own way./etc/network/interfaces
system
July 14, 2019, 6:35pm
14
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
