FTL offline after update [solved]

Help
1

Yesterday I updated the OS (Raspian) of my Rasp PI. Everything went smoothly with "apt update" and "apt upgrade". Because I also wanted to activate ipv6 support, I reconfigured pi-hole with "pihole -r".
Unfortunately FTL is now offline, this is shown in the web interface. Everything I've tried hasn't got FTL back online.

Here is an excerpt from pihole-FTL.log
[2018-03-18 08:29:21.884] ########## FTL started! ##########
[2018-03-18 08:29:21.885] FTL branch: v3.0
[2018-03-18 08:29:21.885] FTL version: v3.0
[2018-03-18 08:29:21.885] FTL commit: a1b2fa03f8f3e3713b57a26a4e9a062fec0573d7
[2018-03-18 08:29:21.885] FTL date: 2018-02-14 12:45:47 -0800
[2018-03-18 08:29:21.885] FTL user: pihole
[2018-03-18 08:29:21.885] Notice: Found no readable FTL config file
[2018-03-18 08:29:21.886] Using default settings
[2018-03-18 08:29:21.886] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2018-03-18 08:29:21.886] SOCKET_LISTENING: only local
[2018-03-18 08:29:21.886] QUERY_DISPLAY: Show queries
[2018-03-18 08:29:21.886] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2018-03-18 08:29:21.886] MAXDBDAYS: max age for stored queries is 365 days
[2018-03-18 08:29:21.886] RESOLVE_IPV6: Resolve IPv6 addresses
[2018-03-18 08:29:21.886] RESOLVE_IPV4: Resolve IPv4 addresses
[2018-03-18 08:29:21.886] DBINTERVAL: saving to DB file every minute
[2018-03-18 08:29:21.887] DBFILE: Using /etc/pihole/pihole-FTL.db
[2018-03-18 08:29:21.887] MAXLOGAGE: Importing up to 24.0 hours of log data
[2018-03-18 08:29:21.887] Finished config file parsing
[2018-03-18 08:29:21.903] Found no other running pihole-FTL process
[2018-03-18 08:29:21.905] PID of FTL process: 4451
[2018-03-18 08:29:22.350] Gravity list entries: 121707
[2018-03-18 08:29:22.350] No blacklist present
[2018-03-18 08:29:22.350] Notice: Increasing wildcards struct size from 0 to 1 (120.00 B)
[2018-03-18 08:29:22.350] Notice: Increasing wildcards struct size from 1 to 2 (136.00 B)
[2018-03-18 08:29:22.350] Notice: Increasing wildcards struct size from 2 to 3 (151.00 B)
[2018-03-18 08:29:22.351] Wildcard blocking list entries: 3
[2018-03-18 08:29:22.352] Database initialized
[2018-03-18 08:29:22.354] Notice: Increasing queries struct size from 0 to 10000 (440.17 KB)
[2018-03-18 08:29:22.354] Notice: Increasing domains struct size from 0 to 1000 (460.17 KB)
[2018-03-18 08:29:22.354] Notice: Increasing clients struct size from 0 to 10 (460.33 KB)
[2018-03-18 08:29:22.361] New client: 192.168.178.1 (0/10)
[2018-03-18 08:29:22.361] Notice: Increasing forwarded struct size from 0 to 4 (460.44 KB)
[2018-03-18 08:29:22.406] New forward server: 85.214.20.141 h1768020.stratoserver.net (0/4)
[2018-03-18 08:29:22.407] Notice: Increasing overTime struct size from 0 to 100 (464.48 KB)
[2018-03-18 08:29:22.437] New forward server: 213.73.91.35 dnscache.berlin.ccc.de (1/4)
[2018-03-18 08:29:22.438] New client: localhost localhost (1/10)
[2018-03-18 08:29:22.573] Notice: Increasing overTime struct size from 100 to 200 (487.24 KB)
[2018-03-18 08:29:22.612] DB warn: TYPE should be either 1 or 2 but not 0
[2018-03-18 08:29:22.612] DB warn: TYPE should be either 1 or 2 but not 0
[2018-03-18 08:29:22.612] DB warn: TYPE should be either 1 or 2 but not 0
[2018-03-18 08:29:22.612] DB warn: TYPE should be either 1 or 2 but not 0
[2018-03-18 08:29:22.614] Imported 4034 queries from the long-term database
[2018-03-18 08:29:22.614] Starting initial log file parsing
[2018-03-18 08:29:22.614] Reading from /var/log/pihole.log (rw-r--r--)
[2018-03-18 08:29:22.708] Finished initial log file parsing
[2018-03-18 08:29:22.708] -> Total DNS queries: 4034
[2018-03-18 08:29:22.708] -> Cached DNS queries: 467
[2018-03-18 08:29:22.709] -> Forwarded DNS queries: 2685
[2018-03-18 08:29:22.709] -> Exactly blocked DNS queries: 882
[2018-03-18 08:29:22.709] -> Wildcard blocked DNS queries: 0
[2018-03-18 08:29:22.709] -> Unknown DNS queries: 0
[2018-03-18 08:29:22.709] -> Unique domains: 873
[2018-03-18 08:29:22.709] -> Unique clients: 2
[2018-03-18 08:29:22.709] -> Known forward destinations: 2
[2018-03-18 08:29:22.709] Successfully accessed setupVars.conf
[2018-03-18 08:29:22.710] Listening on port 4711 for incoming IPv4 telnet connections
[2018-03-18 08:29:22.710] Listening on port 4711 for incoming IPv6 telnet connections
[2018-03-18 08:29:22.711] Error on binding on Unix socket /var/run/pihole/FTL.sock: No such file or directory (2)

There is also no process with PID 4451, just a process with such a name:
pi@voyager:/var/log $ ps -aef | grep 4451
pi 4765 4149 0 08:43 pts/0 00:00:00 grep --color=auto 4451

So, what to do to get FTL back running?

Debug Token:

83xhvmaa85

2

Does sudo service pihole-FTL restart help?

If not:

  • Does the directory /var/run/pihole/ exist? (If not: Create it)
  • Is this directory owned by user pihole? (If not: Change it)
  • Then try again to start FTL.
1 Like
3

You did it!!!
/var/run/pihole has been deleted. Restoring this folder, changing the owner and restarting FTL have solved the problem.

Thank you, DL6ER.

1 Like
4

Reconfiguration is the scapegoat. After I have executed "pihole -r" again and selected "Reconfiguration", the order /var/run/pihole has disappeared again.

5

3 posts were split to a new topic: FTL issues as well and it’s disconnecting or not allowing me to look at my query log

6

Does the file /etc/init.d/pihole-FTL match this file exactly? https://github.com/pi-hole/pi-hole/blob/master/advanced/pihole-FTL.service

If not, then this PR might fix this:

7

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