New installation fails

It uploaded without an issue, you wouldn't have received a token had it not completed the debug.

   [2018-07-26 19:45:00.849] Wildcard blocking list entries: 24
   [2018-07-26 19:45:00.849]  -> Total DNS queries: 4491
   [2018-07-26 19:45:00.849]  -> Cached DNS queries: 690
   [2018-07-26 19:45:00.849]  -> Forwarded DNS queries: 3423
   [2018-07-26 19:45:00.849]  -> Exactly blocked DNS queries: 378
   [2018-07-26 19:45:00.849]  -> Wildcard blocked DNS queries: 0
   [2018-07-26 19:45:00.849]  -> Unknown DNS queries: 0
   [2018-07-26 19:45:00.849]  -> Unique domains: 718
   [2018-07-26 19:45:00.849]  -> Unique clients: 21
   [2018-07-26 19:45:00.849]  -> Known forward destinations: 2
   [2018-07-26 21:00:56.073] FATAL: FTL received SIGTERM from PID/UID 2601/0, exiting gracefully
   [2018-07-26 21:00:56.073] Shutting down...
   [2018-07-26 21:00:56.387] Finished final database update
   [2018-07-26 21:00:56.387] ########## FTL terminated after 314.3 ms! ##########

There's a process on your system that is killing FTL. Can you run sudo ps -aux | grep 2601 and we'll see if we can find the process that is causing the kill -TERM to happen.

ZBOX ~ # ps -aux | grep 2601
root      5841  0.0  0.0  15752  1008 pts/0    S+   21:35   0:00 grep --color=auto 2601

No idea what I should kill

Okay, it's not a resident process. @DL6ER do you remember any possible resolutions to SIGKILL conditions? It looks like a root process so there's not really much we can do to guard against it, but I can't think of any way offhand to identify the process that sent the kill -9?

I guess you mean SIGTERM ? Whenever we have seen this before, it was almost always* systemd who was sending SIGTERM as someone (or something!) called service pihole-FTL stop.

sudo journalctl --unit=pihole-FTL

might be able to provide some further information.

Another possibility is

grep "pihole-FTL" /var/log/syslog

We cannot (actually nothing can) catch and/or du anything against SIGKILL.

*) "almost always" = we never found out what was the reason in some cases

Thanks, and yes kill -9 is the short for kill -SIGTERM. Nuclear option.

@MaDa, try those commands that DL listed and let's see if there are any clues to what is killing the process.

ZBOX ~ # journalctl --unit=pihole-FTL
-- Logs begin at Thu 2018-07-26 17:34:41 CEST, end at Fri 2018-07-27 08:03:14 CEST. --
Jul 26 17:40:42 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 17:40:42 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 17:40:42 ZBOX pihole-FTL[15472]: Not running
Jul 26 17:40:42 ZBOX pihole-FTL[15472]: rm: cannot remove '/var/run/pihole/FTL.sock': No su
Jul 26 17:40:42 ZBOX su[15486]: Successful su for pihole by root
Jul 26 17:40:42 ZBOX su[15486]: + ??? root:pihole
Jul 26 17:40:42 ZBOX su[15486]: pam_unix(su:session): session opened for user pihole by (ui
Jul 26 17:40:42 ZBOX pihole-FTL[15472]: FTL started!
Jul 26 17:40:42 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 26 17:44:49 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 26 17:44:50 ZBOX pihole-FTL[16219]: .
Jul 26 17:44:50 ZBOX pihole-FTL[16219]: Stopped
Jul 26 17:44:50 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 17:44:50 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 17:44:50 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: Not running
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: rm: cannot remove '/var/run/pihole/FTL.sock': No su
Jul 26 17:44:50 ZBOX su[16262]: Successful su for pihole by root
Jul 26 17:44:50 ZBOX su[16262]: + ??? root:pihole
Jul 26 17:44:50 ZBOX su[16262]: pam_unix(su:session): session opened for user pihole by (ui
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: FTL started!
Jul 26 17:44:50 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 26 21:00:56 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 26 21:00:57 ZBOX pihole-FTL[2601]: .
Jul 26 21:00:57 ZBOX pihole-FTL[2601]: Stopped
Jul 26 21:00:57 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 21:57:03 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 21:57:03 ZBOX pihole-FTL[6478]: Not running
Jul 26 21:57:03 ZBOX pihole-FTL[6478]: chown: cannot access '/etc/pihole/dhcp.leases': No s
Jul 26 21:57:13 ZBOX su[6543]: Successful su for pihole by root
Jul 26 21:57:13 ZBOX su[6543]: + ??? root:pihole
Jul 26 21:57:13 ZBOX su[6543]: pam_unix(su:session): session opened for user pihole by (uid
Jul 26 21:57:13 ZBOX pihole-FTL[6478]: FTL started!
Jul 26 21:57:13 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 26 21:57:34 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 26 21:57:35 ZBOX pihole-FTL[6627]: .
Jul 26 21:57:35 ZBOX pihole-FTL[6627]: Stopped
Jul 26 21:57:35 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 21:57:35 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 21:57:35 ZBOX pihole-FTL[6696]: Not running
Jul 26 21:57:35 ZBOX pihole-FTL[6696]: chown: cannot access '/etc/pihole/dhcp.leases': No s
Jul 26 21:57:45 ZBOX su[6758]: Successful su for pihole by root
Jul 26 21:57:45 ZBOX su[6758]: + ??? root:pihole
Jul 26 21:57:45 ZBOX su[6758]: pam_unix(su:session): session opened for user pihole by (uid
Jul 26 21:57:46 ZBOX pihole-FTL[6696]: FTL started!
Jul 26 21:57:46 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 27 08:02:13 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 27 08:02:14 ZBOX pihole-FTL[18758]: .
Jul 27 08:02:14 ZBOX pihole-FTL[18758]: Stopped
Jul 27 08:02:14 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 27 08:02:14 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 27 08:02:14 ZBOX pihole-FTL[18827]: Not running
Jul 27 08:02:14 ZBOX pihole-FTL[18827]: chown: cannot access '/etc/pihole/dhcp.leases': No
Jul 27 08:02:24 ZBOX su[18888]: Successful su for pihole by root
Jul 27 08:02:24 ZBOX su[18888]: + ??? root:pihole
Jul 27 08:02:24 ZBOX su[18888]: pam_unix(su:session): session opened for user pihole by (ui
Jul 27 08:02:25 ZBOX pihole-FTL[18827]: FTL started!
Jul 27 08:02:25 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
lines 15-59/59 (END)
Jul 26 17:44:50 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 17:44:50 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: Not running
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: rm: cannot remove '/var/run/pihole/FTL.sock': No such file or dire
Jul 26 17:44:50 ZBOX su[16262]: Successful su for pihole by root
Jul 26 17:44:50 ZBOX su[16262]: + ??? root:pihole
Jul 26 17:44:50 ZBOX su[16262]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: FTL started!
Jul 26 17:44:50 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 26 21:00:56 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 26 21:00:57 ZBOX pihole-FTL[2601]: .
Jul 26 21:00:57 ZBOX pihole-FTL[2601]: Stopped
Jul 26 21:00:57 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 21:57:03 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 21:57:03 ZBOX pihole-FTL[6478]: Not running
Jul 26 21:57:03 ZBOX pihole-FTL[6478]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or dir
Jul 26 21:57:13 ZBOX su[6543]: Successful su for pihole by root
Jul 26 21:57:13 ZBOX su[6543]: + ??? root:pihole
Jul 26 21:57:13 ZBOX su[6543]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 21:57:13 ZBOX pihole-FTL[6478]: FTL started!
Jul 26 21:57:13 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 26 21:57:34 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 26 21:57:35 ZBOX pihole-FTL[6627]: .
Jul 26 21:57:35 ZBOX pihole-FTL[6627]: Stopped
Jul 26 21:57:35 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 21:57:35 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 21:57:35 ZBOX pihole-FTL[6696]: Not running
Jul 26 21:57:35 ZBOX pihole-FTL[6696]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or dir
Jul 26 21:57:45 ZBOX su[6758]: Successful su for pihole by root
Jul 26 21:57:45 ZBOX su[6758]: + ??? root:pihole
Jul 26 21:57:45 ZBOX su[6758]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 21:57:46 ZBOX pihole-FTL[6696]: FTL started!
Jul 26 21:57:46 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
lines 15-47/59 80%
Jul 26 17:44:50 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 17:44:50 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: Not running
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: rm: cannot remove '/var/run/pihole/FTL.sock': No such file or dire
Jul 26 17:44:50 ZBOX su[16262]: Successful su for pihole by root
Jul 26 17:44:50 ZBOX su[16262]: + ??? root:pihole
Jul 26 17:44:50 ZBOX su[16262]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: FTL started!
Jul 26 17:44:50 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 26 21:00:56 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 26 21:00:57 ZBOX pihole-FTL[2601]: .
Jul 26 21:00:57 ZBOX pihole-FTL[2601]: Stopped
Jul 26 21:00:57 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 21:57:03 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 21:57:03 ZBOX pihole-FTL[6478]: Not running
Jul 26 21:57:03 ZBOX pihole-FTL[6478]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or dir
Jul 26 21:57:13 ZBOX su[6543]: Successful su for pihole by root
Jul 26 21:57:13 ZBOX su[6543]: + ??? root:pihole
Jul 26 21:57:13 ZBOX su[6543]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 21:57:13 ZBOX pihole-FTL[6478]: FTL started!
Jul 26 21:57:13 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 26 21:57:34 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 26 21:57:35 ZBOX pihole-FTL[6627]: .
Jul 26 21:57:35 ZBOX pihole-FTL[6627]: Stopped
Jul 26 21:57:35 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 21:57:35 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 21:57:35 ZBOX pihole-FTL[6696]: Not running
Jul 26 21:57:35 ZBOX pihole-FTL[6696]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or dir
Jul 26 21:57:45 ZBOX su[6758]: Successful su for pihole by root
Jul 26 21:57:45 ZBOX su[6758]: + ??? root:pihole
Jul 26 21:57:45 ZBOX su[6758]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 21:57:46 ZBOX pihole-FTL[6696]: FTL started!
Jul 26 21:57:46 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 27 08:02:13 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
lines 15-48/59 82%
Jul 26 17:44:50 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 17:44:50 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: Not running
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: rm: cannot remove '/var/run/pihole/FTL.sock': No such file or dire
Jul 26 17:44:50 ZBOX su[16262]: Successful su for pihole by root
Jul 26 17:44:50 ZBOX su[16262]: + ??? root:pihole
Jul 26 17:44:50 ZBOX su[16262]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: FTL started!
Jul 26 17:44:50 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 26 21:00:56 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 26 21:00:57 ZBOX pihole-FTL[2601]: .
Jul 26 21:00:57 ZBOX pihole-FTL[2601]: Stopped
Jul 26 21:00:57 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 21:57:03 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 21:57:03 ZBOX pihole-FTL[6478]: Not running
Jul 26 21:57:03 ZBOX pihole-FTL[6478]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or dir
Jul 26 21:57:13 ZBOX su[6543]: Successful su for pihole by root
Jul 26 21:57:13 ZBOX su[6543]: + ??? root:pihole
Jul 26 21:57:13 ZBOX su[6543]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 21:57:13 ZBOX pihole-FTL[6478]: FTL started!
Jul 26 21:57:13 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 26 21:57:34 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 26 21:57:35 ZBOX pihole-FTL[6627]: .
Jul 26 21:57:35 ZBOX pihole-FTL[6627]: Stopped
Jul 26 21:57:35 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 21:57:35 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 21:57:35 ZBOX pihole-FTL[6696]: Not running
Jul 26 21:57:35 ZBOX pihole-FTL[6696]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or dir
Jul 26 21:57:45 ZBOX su[6758]: Successful su for pihole by root
Jul 26 21:57:45 ZBOX su[6758]: + ??? root:pihole
Jul 26 21:57:45 ZBOX su[6758]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 21:57:46 ZBOX pihole-FTL[6696]: FTL started!
Jul 26 21:57:46 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 27 08:02:13 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 27 08:02:14 ZBOX pihole-FTL[18758]: .
Jul 27 08:02:14 ZBOX pihole-FTL[18758]: Stopped
Jul 27 08:02:14 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
lines 15-51/59 86%
Jul 26 17:44:50 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 17:44:50 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: Not running
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: rm: cannot remove '/var/run/pihole/FTL.sock': No such file or dire
Jul 26 17:44:50 ZBOX su[16262]: Successful su for pihole by root
Jul 26 17:44:50 ZBOX su[16262]: + ??? root:pihole
Jul 26 17:44:50 ZBOX su[16262]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: FTL started!
Jul 26 17:44:50 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 26 21:00:56 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 26 21:00:57 ZBOX pihole-FTL[2601]: .
Jul 26 21:00:57 ZBOX pihole-FTL[2601]: Stopped
Jul 26 21:00:57 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 21:57:03 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 21:57:03 ZBOX pihole-FTL[6478]: Not running
Jul 26 21:57:03 ZBOX pihole-FTL[6478]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or dir
Jul 26 21:57:13 ZBOX su[6543]: Successful su for pihole by root
Jul 26 21:57:13 ZBOX su[6543]: + ??? root:pihole
Jul 26 21:57:13 ZBOX su[6543]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 21:57:13 ZBOX pihole-FTL[6478]: FTL started!
Jul 26 21:57:13 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 26 21:57:34 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 26 21:57:35 ZBOX pihole-FTL[6627]: .
Jul 26 21:57:35 ZBOX pihole-FTL[6627]: Stopped
Jul 26 21:57:35 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 21:57:35 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 21:57:35 ZBOX pihole-FTL[6696]: Not running
Jul 26 21:57:35 ZBOX pihole-FTL[6696]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or dir
Jul 26 21:57:45 ZBOX su[6758]: Successful su for pihole by root
Jul 26 21:57:45 ZBOX su[6758]: + ??? root:pihole
Jul 26 21:57:45 ZBOX su[6758]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 21:57:46 ZBOX pihole-FTL[6696]: FTL started!
Jul 26 21:57:46 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 27 08:02:13 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 27 08:02:14 ZBOX pihole-FTL[18758]: .
Jul 27 08:02:14 ZBOX pihole-FTL[18758]: Stopped
Jul 27 08:02:14 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 27 08:02:14 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 27 08:02:14 ZBOX pihole-FTL[18827]: Not running
lines 15-53/59 89%
Jul 26 17:44:50 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 17:44:50 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: Not running
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: rm: cannot remove '/var/run/pihole/FTL.sock': No such file or dire
Jul 26 17:44:50 ZBOX su[16262]: Successful su for pihole by root
Jul 26 17:44:50 ZBOX su[16262]: + ??? root:pihole
Jul 26 17:44:50 ZBOX su[16262]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 17:44:50 ZBOX pihole-FTL[16248]: FTL started!
Jul 26 17:44:50 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 26 21:00:56 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 26 21:00:57 ZBOX pihole-FTL[2601]: .
Jul 26 21:00:57 ZBOX pihole-FTL[2601]: Stopped
Jul 26 21:00:57 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 21:57:03 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 21:57:03 ZBOX pihole-FTL[6478]: Not running
Jul 26 21:57:03 ZBOX pihole-FTL[6478]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or dir
Jul 26 21:57:13 ZBOX su[6543]: Successful su for pihole by root
Jul 26 21:57:13 ZBOX su[6543]: + ??? root:pihole
Jul 26 21:57:13 ZBOX su[6543]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 21:57:13 ZBOX pihole-FTL[6478]: FTL started!
Jul 26 21:57:13 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 26 21:57:34 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 26 21:57:35 ZBOX pihole-FTL[6627]: .
Jul 26 21:57:35 ZBOX pihole-FTL[6627]: Stopped
Jul 26 21:57:35 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 26 21:57:35 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 26 21:57:35 ZBOX pihole-FTL[6696]: Not running
Jul 26 21:57:35 ZBOX pihole-FTL[6696]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or dir
Jul 26 21:57:45 ZBOX su[6758]: Successful su for pihole by root
Jul 26 21:57:45 ZBOX su[6758]: + ??? root:pihole
Jul 26 21:57:45 ZBOX su[6758]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 26 21:57:46 ZBOX pihole-FTL[6696]: FTL started!
Jul 26 21:57:46 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.
Jul 27 08:02:13 ZBOX systemd[1]: Stopping LSB: pihole-FTL daemon...
Jul 27 08:02:14 ZBOX pihole-FTL[18758]: .
Jul 27 08:02:14 ZBOX pihole-FTL[18758]: Stopped
Jul 27 08:02:14 ZBOX systemd[1]: Stopped LSB: pihole-FTL daemon.
Jul 27 08:02:14 ZBOX systemd[1]: Starting LSB: pihole-FTL daemon...
Jul 27 08:02:14 ZBOX pihole-FTL[18827]: Not running
Jul 27 08:02:14 ZBOX pihole-FTL[18827]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or di
Jul 27 08:02:24 ZBOX su[18888]: Successful su for pihole by root
Jul 27 08:02:24 ZBOX su[18888]: + ??? root:pihole
Jul 27 08:02:24 ZBOX su[18888]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jul 27 08:02:25 ZBOX pihole-FTL[18827]: FTL started!
Jul 27 08:02:25 ZBOX systemd[1]: Started LSB: pihole-FTL daemon.

ZBOX ~ # grep "pihole-FTL" /var/log/syslog
Binary file /var/log/syslog matches

There is something that is causing systemd to terminate the pihole-FTL daemon. It's unknown to us what that may be, I'm not sure how we can help further with finding the solution to this problem.

I also have no explanation for this, as I have had no problems installing or operating the beta or dev version on the same system for the last few months.
The current master version also runs without grumbling.

One difference exists: I don't use the buildt in DHCP-Server and so don't exist any DHCP-leases.

No, I don't have.

new day, new game

BOX ~ # echo release/v4.0 | sudo tee /etc/pihole/ftlbranch
release/v4.0
ZBOX ~ # pihole checkout core release/v4.0 -x
  Please note that changing branches severely alters your Pi-hole subsystems
  Features that work on the master branch, may not on a development branch
  This feature is NOT supported unless a Pi-hole developer explicitly asks!
  Have you read and understood this? [y/N] y

  [✓] Fetching branches from https://github.com/pi-hole/pi-hole.git
  [i] 31 branches available for Pi-hole Core

  [✓] Switching to branch: 'release/v4.0' from 'refs/heads/master'
  [i] Already up-to-date.
  [i] Running installer to upgrade your installation

  [✓] Root user check

        .;;,.
        .ccccc:,.
         :cccclll:.      ..,,
          :ccccclll.   ;ooodc
           'ccll:;ll .oooodc
             .;cll.;;looo:.
                 .. ','.
                .',,,,,,'.
              .',,,,,,,,,,.
            .',,,,,,,,,,,,....
          ....''',,,,,,,'.......
        .........  ....  .........
        ..........      ..........
        ..........      ..........
        .........  ....  .........
          ........,,,,,,,'......
            ....',,,,,,,,,,,,.
               .',,,,,,,,,'.
                .',,,,,,'.
                  ..'''.

  [i] Existing PHP installation detected : PHP version 7.0.30-0ubuntu0.16.04.1
  [i] Performing unattended setup, no whiptail dialogs will be displayed
  [✓] Disk space check

  [✓] Update local cache of available packages

  [✓] Checking apt-get for upgraded packages... up to date!

  [i] Installer Dependency checks...
  [✓] Checking for apt-utils
  [✓] Checking for dialog
  [✓] Checking for debconf
  [✓] Checking for dhcpcd5
  [✓] Checking for git
  [✓] Checking for iproute2
  [✓] Checking for whiptail

  [✓] Check for existing repository in /etc/.pihole
  [✓] Update repo in /etc/.pihole

  [✓] Check for existing repository in /var/www/html/admin
  [✓] Update repo in /var/www/html/admin

  [i] Main Dependency checks...
  [✓] Checking for bc
  [✓] Checking for cron
  [✓] Checking for curl
  [✓] Checking for dnsutils
  [✓] Checking for iputils-ping
  [✓] Checking for lsof
  [✓] Checking for netcat
  [✓] Checking for psmisc
  [✓] Checking for sudo
  [✓] Checking for unzip
  [✓] Checking for wget
  [✓] Checking for idn2
  [✓] Checking for sqlite3
  [✓] Checking for libcap2-bin
  [✓] Checking for dns-root-data
  [✓] Checking for resolvconf
  [✓] Checking for lighttpd
  [✓] Checking for php7.0-common
  [✓] Checking for php7.0-cgi
  [✓] Checking for php7.0-sqlite3

  [✓] Enabling lighttpd service to start on reboot
  [✓] Installing scripts from /etc/.pihole

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf

  [i] Installing blocking page...
  [✓] Creating directory for blocking page, and copying files
  [✗] Backing up index.lighttpd.html
        No default index.lighttpd.html file found... not backing up

  [✓] Installing sudoer file

  [✓] Installing latest Cron script

  [✓] Installing latest logrotate script

  [i] FTL Checks...
  [✓] Detected x86_64 architecture
  [i] Checking for existing FTL binary...
  [✓] Downloading and Installing FTL
  [i] FTL can now resolve DNS Queries without dnsmasq running separately
  [✓] Stopping dnsmasq service...
  [✓] Disabling dnsmasq service

  [✓] man pages installed and database updated
  [i] Systemd-resolved is not enabled
  [✓] Starting lighttpd service
  [✓] Enabling lighttpd service to start on reboot
  [i] Restarting services...
  [✓] Starting pihole-FTL service
  [✓] Enabling pihole-FTL service to start on reboot
  [✓] Deleting existing list cache
  [✗] DNS resolution is currently unavailable
  [✓] DNS resolution is now available

  [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: Retrieval successful

  [i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_tracking.txt)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_ad.txt)
  [✓] Status: Retrieval successful

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

  [i] Target: v.firebog.net (Kowabit.txt)
  [✓] Status: Retrieval successful

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

  [i] Target: github.com (pi_blocklist_porn_all.list)
  [✓] Status: Retrieval successful

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

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

  [i] Target: raw.githubusercontent.com (malicious-sites.txt)
  [✓] Status: Retrieval successful

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

  [i] Target: v.firebog.net (AdguardDNS.txt)
  [✓] Status: Retrieval successful

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

  [i] Target: v.firebog.net (Easylist.txt)
  [✓] Status: Retrieval successful

  [i] Target: v.firebog.net (Easyprivacy.txt)
  [✓] Status: Retrieval successful

  [i] Target: v.firebog.net (Shalla-mal.txt)
  [✓] Status: Retrieval successful

  [i] Target: easylist-downloads.adblockplus.org (easylistgermany.txt)
  [✓] Status: Retrieval successful
  [i] Format: Adblockcomm: file 1 is not in sorted order
  [✓] Format: Adblock

  [i] Target: easylist-downloads.adblockplus.org (fanboy-annoyance.txt)
  [✓] Status: Retrieval successful
  [i] Format: Adblockcomm: file 1 is not in sorted order
  [✓] Format: Adblock

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

  [i] Target: dehakkelaar.nl (cryptojacking_campaign.list.txt)
  [✓] Status: Retrieval successful

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

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

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

  [✓] Consolidating blocklists
  [✓] Extracting domains from blocklists
  [i] Number of domains being pulled in by gravity: 2092734
  [✓] Removing duplicate domains
  [i] Number of unique domains trapped in the Event Horizon: 1953246
  [i] Number of whitelisted domains: 46
  [i] Number of blacklisted domains: 36
  [i] Number of regex filters: 0
  [✓] Parsing domains into hosts format
  [✓] Cleaning up stray matter

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

  [i] The install log is located at: /etc/pihole/install.log
    Update Complete!

  Current Pi-hole version is v3.3-409-ga44096a
  Current AdminLTE version is v3.3
  Current FTL version is vDev-8e56b61
ZBOX ~ # pihole checkout web release/v4.0
  Please note that changing branches severely alters your Pi-hole subsystems
  Features that work on the master branch, may not on a development branch
  This feature is NOT supported unless a Pi-hole developer explicitly asks!
  Have you read and understood this? [y/N] y

  [✗] Fetching branches from https://github.com/pi-hole/AdminLTE.git

The core is on v4.0, are you able to use that to browse sites? (Is the DNS working?)

yes, works fine. Did you change anything? I don't understand why it works today...

Now only one problem: [✗] Fetching branches from https://github.com/pi-hole/AdminLTE.git

new debug key: js9se36gd1

The devs have been working hard the last few days fixing these issues, and you're seeing the results.

You are now at Release 4.0 on core and FTL, but still at master on web version, which is consistent with the error you were seeing. Doing a little checking with devs for the next step to get you to web Release 4.

** [ DIAGNOSING ]: Core version
[i] Core: v3.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: release/v4.0 (https://discourse.pi-hole.net/t/the-pihole-command-with-examples/738#checkout)
[i] Commit: v3.3-409-ga44096a

*** [ DIAGNOSING ]: Web version
[i] Web: v3.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v3.3-0-ge48aa29

*** [ DIAGNOSING ]: FTL version
[✓] FTL: vDev-8e56b61 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)

congratulations!

One additional issue: resolving of local DNS/ host names don't work.
I use the Fritzbox as DHCP-Server. Thatswhy as DNS-forwarder in pihole too.

Your debug log shows that DNS is resolving properly on Pi-Hole. With your NULL blocking, for both IPV4 and IPV6 it is returning NULL for the blocked site. What are you seeing that isn't working properly?

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] marjoriex.com is 0.0.0.0 via localhost (127.0.0.1)
[✓] marjoriex.com is 0.0.0.0 via Pi-hole (192.168.1.60)
[✓] doubleclick.com is 172.217.18.14 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] kissesnstuff.blogspot.hu is :: via localhost (::1)
[✓] kissesnstuff.blogspot.hu is :: via Pi-hole (fd00::d9a:5ac:1286:4d3d)
[✓] doubleclick.com is 2a00:1450:4001:820::200e via a remote, public DNS server (2001:4860:4860::8888)

it's not possible to resolve local domain names, managed and provided by the Fritzbox DHCP-Server.

My Architecture:

Fritz.box = 192.168.1.1 and fd00::cece:1eff:fea4:4ca0

  • DHCP IPv4 and IPv6
  • local DNS = 192.168.1.60 and fd00::d9a:5ac:1286:4d3d
  • DNS-Upstream-Server: Cloudflare v4 and v6

Pihole = 192.168.1.60 and fd00::d9a:5ac:1286:4d3d

  • DNS-Upstrem = 192.168.1.1 and fd00::cece:1eff:fea4:4ca0
  • DHCP-Server deactivated
  • Never forward non-FQDNs = deaktivated
  • Never forward reverse lookups for private IP ranges = deaktivated

In my opinion, local names are not forwarded to and resolved from the Fritzbox.
This is indicated by the fact that only IP addresses are reported in the dashboard and not local host names.

This worked in the master branch version.

for example:

MacBook-Pro  ~ # ping diskstation                      
ping: cannot resolve diskstation: Unknown host

MacBook-Pro  ~ # dig diskstation                        

; <<>> DiG 9.12.1 <<>> diskstation
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 61319
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;diskstation.			IN	A

;; Query time: 4 msec
;; SERVER: 192.168.1.60#53(192.168.1.60)
;; WHEN: Fri Jul 27 19:22:14 CEST 2018
;; MSG SIZE  rcvd: 29

MacBook-Pro  ~ # dig diskstation @192.168.1.1              

; <<>> DiG 9.12.1 <<>> diskstation @192.168.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53773
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;diskstation.			IN	A

;; ANSWER SECTION:
diskstation.		9	IN	A	192.168.1.2

;; Query time: 1 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Fri Jul 27 19:23:35 CEST 2018
;; MSG SIZE  rcvd: 45

In the meantime I have gained one insight: The name resolution is done via forwarding to the Fritzbox exclusively via IPv6

I would have the Fritz!box using the DNS of Pihole and would from thst go to the upstream server outside.

So 192.168.1.1 using DNS 192.168.1.60
And 192.168.1.60 go the up stream Cloud flare.

This is not my use case, but not the place to discuss here.

Also look if your Pihole has a fe80:: available instead of a fd00:: address. fd00:: Are normally used by routers/modems.

That's not right.
fd00-Addresses are unique local addresses for devices behind a router, not routable. They are unindependent from prefix of your internet provider. ULA was designed for internal networks that never need to (or should ever) talk to the global Internet. https://youtu.be/v26BAlfWBm8
fd80-addresses are link local addresses and only addressable by specifying the corresponding network link.

But also not the place to discuss here.
https://www.computernetworkingnotes.com/networking-tutorials/ipv6-address-types-format-explained-with-examples.html

@jfb , @DanSchaper , @technicalpyro, @RamSet
Hi guys, any news? any hints?.

I reverted back to master.

best regards.