Failed to restart pihole-FTL.service

Yes I am; however, I had to change the port to 8080 to avoid a conflict.

Ah, I think the asynchronous script calls expect the API to be always on port 80, I'm not sure if they can handle a non-standard scenario like yours. Maybe @Mcat12 can confirm this.

edit: I just changed my lighttpd installation to port 8080 and restarted the server. I can successfully open the dashboard on http://pi.hole:8080/admin and can also use all functionality, including "Find Ad Domain In Lists"

Can you make a new debug token? (they expire after 48 hours).

Sorry about that... I'll do it when I get home tonight.

Here is the new debug token:

Your debug token is: wdwqntbe4d

What are the contents of this file (if it exists): /var/log/pihole-FTL.log

Unfortunately, there is no pihole-FTL.log

If you're on Stretch (not Jessie), then try updating to Pi-hole 3.3.

Uninstalled old install and installed v3.3, changed the port to 8080, still getting:

[ERROR] There are no domain lists generated lists within /etc/pihole/! Please update gravity by running pihole -g, or repair Pi-hole using pihole -r.

I am now seeing this as well:

[✗] Job for dnsmasq.service failed. See 'systemctl status dnsmasq.service' and 'journalctl -xn' for details.
pihole-FTL: no process found

Pi-hole version is v3.3 (Latest: v3.3)
AdminLTE version is v3.3 (Latest: v3.3)
FTL version is v3.0 (Latest: v3.0)

Run pihole -d for a debug token and share the output of:

sudo service dnsmasq status
sudo service pihole-FTL status

sudo service dnsmasq status

  • dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
    Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled)
    Drop-In: /run/systemd/generator/dnsmasq.service.d
    `-50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
    Active: failed (Result: exit-code) since Wed 2018-02-21 17:54:23 CST; 22h ago
    Process: 5750 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=1/FAILURE)

sudo service pihole-FTL status

  • pihole-FTL.service - LSB: pihole-FTL daemon
    Loaded: loaded (/etc/init.d/pihole-FTL)
    Active: inactive (dead)

[✓] Your debug token is: kndt5slv66

Sorry, I've been busy for the last few days. Can you make a new debug token?
What is the output of pihole -g?

Sorry for the delay.

Your debug token is: hyy3i9y4m3

pihole -g

[i] Neutrino emissions detected...
[✓] Pulling blocklist source list into range

[i] Target: raw.githubusercontent.com (hosts)
[✓] Status: Retrieval successful

[i] Target: mirror1.malwaredomains.com (justdomains)
[✓] Status: Retrieval successful

[i] Target: sysctl.org (hosts)
[✓] Status: No changes detected

[i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
[✓] Status: No changes detected

[i] Target: s3.amazonaws.com (simple_tracking.txt)
[✓] Status: No changes detected

[i] Target: s3.amazonaws.com (simple_ad.txt)
[✓] Status: No changes detected

[i] Target: hosts-file.net (ad_servers.txt)
[✓] Status: Retrieval successful

[✓] Consolidating blocklists
[✓] Extracting domains from blocklists
[i] Number of domains being pulled in by gravity: 146697
[✓] Removing duplicate domains
[i] Number of unique domains trapped in the Event Horizon: 123564

[i] Number of blocklist source domains being added to the whitelist: 6
[i] Number of whitelisted domains: 6
[✓] Parsing domains into hosts format
[✓] Cleaning up stray matter
[✗] Job for dnsmasq.service failed. See 'systemctl status dnsmasq.service' and 'journalctl -xn' for details.
pihole-FTL: no process found

[✓] DNS service is running
[✓] Pi-hole blocking is Enabled

You're on Jessie with an out of date dnsmasq version, see:

1 Like

A post was split to a new topic: I am getting pihole-FTL “active (exited)” and Web GUI is non resposive

For the next person searching for a solution. My pihole FTL was broken. /r (repair) fixed it.