Error when starting FTLDNS

Hi, I just ran the commands to activate FTLDNS. The blocking seems to work but at the Query Log it only shows "processing" but no data. There is an error meassage within after the command to see if it works:

root@DietPi:~# sudo systemctl status pihole-FTL
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (running) since Tue 2018-04-03 20:57:30 BST; 4min 31s ago
Docs: man:systemd-sysv-generator(8)
Process: 287 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/pihole-FTL.service
└─555 /usr/bin/pihole-FTL

Apr 03 20:57:27 DietPi systemd[1]: Starting LSB: pihole-FTL daemon...
Apr 03 20:57:28 DietPi pihole-FTL[287]: Not running
Apr 03 20:57:28 DietPi pihole-FTL[287]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
Apr 03 20:57:28 DietPi su[427]: Successful su for pihole by root
Apr 03 20:57:28 DietPi su[427]: + ??? root:pihole
Apr 03 20:57:28 DietPi su[427]: pam_env(su:session): Unable to open env file: /etc/environment: No such file or directory
Apr 03 20:57:28 DietPi su[427]: pam_unix(su:session): session opened for user pihole by (uid=0)
Apr 03 20:57:30 DietPi pihole-FTL[287]: FTL started!
Apr 03 20:57:30 DietPi su[427]: pam_unix(su:session): session closed for user pihole
Apr 03 20:57:30 DietPi systemd[1]: Started LSB: pihole-FTL daemon.

I have to say that also the following update command did not work:
dietpi-update = Run now to update DietPi (from v6.1 to v6.6).

can someone help? Thanks, Michl

Run pihole -d for a debug token.

Hi have a nearly similar problem, i uploaded my token : 28n8vxvbko

I ran the command :slight_smile:

echo "FTLDNS" | sudo tee /etc/pihole/ftlbranch
pihole checkout core FTLDNS
pihole checkout web FTLDNS

Then when i check the status of dnsmasq it still running e.g. Active(running)
And pihole-FTL is Active (exited) :

pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Wed 2018-04-04 04:25:32 CEST; 29min ago
Docs: man:systemd-sysv-generator(8)
CGroup: /system.slice/pihole-FTL.service

avril 04 04:25:32 PiHoleX systemd[1]: Starting LSB: pihole-FTL daemon...
avril 04 04:25:32 PiHoleX pihole-FTL[3583]: Not running
avril 04 04:25:32 PiHoleX pihole-FTL[3583]: rm: impossible de supprimer '/var/run/pihole/FTL.sock': Aucun fichier ou dossier de ce type
avril 04 04:25:32 PiHoleX su[3597]: Successful su for pihole by root
avril 04 04:25:32 PiHoleX su[3597]: + ??? root:pihole
avril 04 04:25:32 PiHoleX su[3597]: pam_unix(su:session): session opened for user pihole by (uid=0)
avril 04 04:25:32 PiHoleX pihole-FTL[3583]: FTL started!
avril 04 04:25:32 PiHoleX systemd[1]: Started LSB: pihole-FTL daemon.

Could somebody knows what happen ?
Thanks

Your debug token is: fv3ozvplxy

Can you confirm that this means something like "No such file or directory"? If so, then this is not a critical error and maybe actually to be expected on the first run of FTL.

From your debug log it seems like pihole-FTL is running perfectly fine for you! What is the issue? Have you tried Ctrl+F5 (force refresh) in the browser?

FTLDNS is your new resolver, i.e. if name resolution works, the daemon works as well. Have you tried a force refresh in your browser (Ctrl+F5)?

Thanks for the hint. Now I tried Android Firefox and it worked perfectly. In Android Crome still the same issue "processing" in Query Log. Ctrl + F5 did not help. Closing of the Browser and new loging neither. I am happy with using Firefox but if someone has another idea I will check it.

Yes, the Chrome browser is buggy at the moment. We see this lag since mid-January and yet there doesn't seem to be a solution from Google :confused:

See also

Thank you. For me the problem is solved now as it is outside Pi-Holes influence. The only strange thing is that Crome works well without FTLDNS. I swiched several times back and forth with and without FTLDNS and had always the same issue.
THANK YOU FOR YOUR HELP!

1 Like

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