Installing on Ubuntu 18.04 upgraded from 16.04

Help
1

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

Expected Behaviour:

Running the installer should start Pihole

Actual Behaviour:

Pihole FTL and DNS resolver fail to start resolve, instead all DNS is passed onto my secondary DNS. After digging in syslogs I found this output.

Feb 17 16:52:05 gonzo pihole-FTL[8082]: Not running
Feb 17 16:52:05 gonzo su[8126]: Successful su for pihole by root
Feb 17 16:52:05 gonzo su[8126]: + ??? root:pihole
Feb 17 16:52:05 gonzo su[8126]: pam_unix(su:session): session opened for user pihole by (uid=0)
Feb 17 16:52:05 gonzo pihole-FTL[8082]: dnsmasq: failed to create listening socket for 192.168.7.117: Address already in use
Feb 17 16:52:05 gonzo su[8126]: pam_unix(su:session): session closed for user pihole
Feb 17 16:52:05 gonzo systemd[1]: Started LSB: pihole-FTL daemon.

the contents of /var/logs/pihole is empty

Debug Token:

https://tricorder.pi-hole.net/6baurunyql

Some other notes

This specific server runs an nginx proxy that responds on :8443 & :8080 from my googling and digging through docs there should be no port conflicts.

The static IP address is assigned at the router, not on the machine itself.

Thanks for any help

2

What does sudo lsof -iTCP:53 -sTCP:LISTEN -P -n +c 10 show for the daemon on port 53?

4 
austinbv@gonzo:~$ sudo lsof -iTCP:53 -sTCP:LISTEN -P -n +c 10
[sudo] password for austinbv:
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
named   1020 bind   21u  IPv6  26012      0t0  TCP *:53 (LISTEN)
named   1020 bind   22u  IPv4  26016      0t0  TCP 127.0.0.1:53 (LISTEN)
named   1020 bind   25u  IPv4  28800      0t0  TCP 192.168.7.117:53 (LISTEN)
named   1020 bind   26u  IPv4  31239      0t0  TCP 172.25.0.1:53 (LISTEN)
named   1020 bind   27u  IPv4  32611      0t0  TCP 172.17.0.1:53 (LISTEN)
named   1020 bind   28u  IPv4  31313      0t0  TCP 172.18.0.1:53 (LISTEN)
named   1020 bind   29u  IPv4  67140      0t0  TCP 172.19.0.1:53 (LISTEN)
named   1020 bind   30u  IPv4  77328      0t0  TCP 169.254.241.0:53 (LISTEN)
named   1020 bind   31u  IPv4  79249      0t0  TCP 169.254.175.89:53 (LISTEN)
named   1020 bind   32u  IPv4  79412      0t0  TCP 169.254.108.89:53 (LISTEN)
named   1020 bind   33u  IPv4  79979      0t0  TCP 169.254.114.40:53 (LISTEN)
named   1020 bind   34u  IPv4  79991      0t0  TCP 169.254.175.163:53 (LISTEN)
6

bind is installed on your system and is competing with Pi-hole for port 53. You'll need to remove bind or keep it from starting and taking control of port 53.

9

Awesome

Bind is uninstalled and I run a repair and continue to get this error

Feb 17 17:49:10 gonzo systemd[1]: Starting LSB: pihole-FTL daemon...
Feb 17 17:49:10 gonzo pihole-FTL[6513]: Not running
Feb 17 17:49:10 gonzo su[6556]: Successful su for pihole by root
Feb 17 17:49:10 gonzo su[6556]: + ??? root:pihole
Feb 17 17:49:10 gonzo su[6556]: pam_unix(su:session): session opened for user pihole by (uid=0)
Feb 17 17:49:10 gonzo pihole-FTL[6513]: dnsmasq: failed to create listening socket for 127.0.0.1: Address already in use
Feb 17 17:49:10 gonzo su[6556]: pam_unix(su:session): session closed for user pihole
Feb 17 17:49:10 gonzo systemd[1]: Started LSB: pihole-FTL daemon.
10

Run that command again to see what is on that port now.

11

Got it. Needed to purge bind9 and bind9-host

1 Like
12

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.