Oops, I didn't notice that. 
FTL is running from this now. Checking....
ran pihole -up again, branch fix/negative_forwardIDs, got another update.
pihole version
Pi-hole version is v4.3.2-397-g0a70bbd (Latest: v4.3.2)
AdminLTE version is v4.3.2-393-g843e46d (Latest: v4.3.2)
FTL version is vDev-acdd225 (Latest: v4.3.1)
result:
[2020-02-11 12:04:46.914 14292] Using log file /var/log/pihole-FTL.log
[2020-02-11 12:04:46.914 14292] ########## FTL started! ##########
[2020-02-11 12:04:46.914 14292] FTL branch: fix/negative_forwardIDs
[2020-02-11 12:04:46.914 14292] FTL version: vDev-acdd225
[2020-02-11 12:04:46.914 14292] FTL commit: acdd225
[2020-02-11 12:04:46.914 14292] FTL date: 2020-02-11 09:53:22 +0100
[2020-02-11 12:04:46.914 14292] FTL user: pihole
[2020-02-11 12:04:46.914 14292] Compiled for armhf (compiled on CI) using arm-linux-gnueabihf-gcc (Debian 6.3.0-18) 6.3.0 20170516
[2020-02-11 12:04:46.914 14292] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2020-02-11 12:04:46.914 14292] SOCKET_LISTENING: only local
[2020-02-11 12:04:46.914 14292] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2020-02-11 12:04:46.914 14292] MAXDBDAYS: max age for stored queries is 3 days
[2020-02-11 12:04:46.914 14292] RESOLVE_IPV6: Resolve IPv6 addresses
[2020-02-11 12:04:46.914 14292] RESOLVE_IPV4: Resolve IPv4 addresses
[2020-02-11 12:04:46.914 14292] DBINTERVAL: saving to DB file every 120 seconds
[2020-02-11 12:04:46.914 14292] DBFILE: Using /etc/pihole/pihole-FTL.db
[2020-02-11 12:04:46.915 14292] MAXLOGAGE: Importing up to 24.0 hours of log data
[2020-02-11 12:04:46.915 14292] PRIVACYLEVEL: Set to 0
[2020-02-11 12:04:46.915 14292] IGNORE_LOCALHOST: Show queries from localhost
[2020-02-11 12:04:46.915 14292] BLOCKINGMODE: Null IPs for blocked domains
[2020-02-11 12:04:46.915 14292] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
[2020-02-11 12:04:46.915 14292] DBIMPORT: Importing history from database
[2020-02-11 12:04:46.915 14292] PIDFILE: Using /var/run/pihole-FTL.pid
[2020-02-11 12:04:46.915 14292] PORTFILE: Using /var/run/pihole-FTL.port
[2020-02-11 12:04:46.915 14292] SOCKETFILE: Using /var/run/pihole/FTL.sock
[2020-02-11 12:04:46.915 14292] SETUPVARSFILE: Using /etc/pihole/setupVars.conf
[2020-02-11 12:04:46.915 14292] MACVENDORDB: Using /etc/pihole/macvendor.db
[2020-02-11 12:04:46.915 14292] GRAVITYDB: Using /etc/pihole/gravity.db
[2020-02-11 12:04:46.915 14292] PARSE_ARP_CACHE: Active
[2020-02-11 12:04:46.915 14292] REGEX_IGNORECASE: Disabled. Regex is case sensitive
[2020-02-11 12:04:46.915 14292] CNAME_DEEP_INSPECT: Active
[2020-02-11 12:04:46.915 14292] Finished config file parsing
[2020-02-11 12:04:46.917 14292] Database version is 5
[2020-02-11 12:04:46.917 14292] Database successfully initialized
[2020-02-11 12:04:46.918 14292] New upstream server: fdaa:bbcc:ddee:2::5552 (0/1024)
[2020-02-11 12:04:46.918 14292] New upstream server: 127.10.10.2 (1/1024)
[2020-02-11 12:04:46.930 14292] Imported 1324 queries from the long-term database
[2020-02-11 12:04:46.931 14292] -> Total DNS queries: 1324
[2020-02-11 12:04:46.931 14292] -> Cached DNS queries: 86
[2020-02-11 12:04:46.931 14292] -> Forwarded DNS queries: 1026
[2020-02-11 12:04:46.931 14292] -> Blocked DNS queries: 212
[2020-02-11 12:04:46.931 14292] -> Unknown DNS queries: 0
[2020-02-11 12:04:46.931 14292] -> Unique domains: 181
[2020-02-11 12:04:46.931 14292] -> Unique clients: 4
[2020-02-11 12:04:46.931 14292] -> Known forward destinations: 2
[2020-02-11 12:04:46.931 14292] Successfully accessed setupVars.conf
[2020-02-11 12:04:46.937 14294] PID of FTL process: 14294
[2020-02-11 12:04:46.937 14294] Listening on port 4711 for incoming IPv4 telnet connections
[2020-02-11 12:04:46.937 14294] Listening on port 4711 for incoming IPv6 telnet connections
[2020-02-11 12:04:46.938 14294] Listening on Unix socket
[2020-02-11 12:04:46.939 14294] Reloading DNS cache
[2020-02-11 12:04:46.939 14294] Blocking status is enabled
[2020-02-11 12:04:46.948 14294] INFO: No regex whitelist entries found
[2020-02-11 12:04:46.952 14294] Compiled 0 whitelist and 19 blacklist regex filters in 6.8 msec
[2020-02-11 12:05:00.455 14294] Resizing "/FTL-strings" from 4096 to 8192
[2020-02-11 12:08:27.637 14294] Reloading DNS cache
[2020-02-11 12:08:27.637 14294] Blocking status is enabled
[2020-02-11 12:08:27.639 14294] SQLite3 message: file unlinked while open: /etc/pihole/gravity.db (28)
[2020-02-11 12:08:27.793 14294] INFO: No regex whitelist entries found
[2020-02-11 12:08:27.796 14294] Compiled 0 whitelist and 19 blacklist regex filters in 5.7 msec
noticed the following entry, what does this mean?
SQLite3 message: file unlinked while open: /etc/pihole/gravity.db (28)
Same problem here after latest update.
It means that gravity.db was unlinked while it was still open. This is expected and happens during swapping of the databases after the gravity run. This is not an issue.
On Linux, you do not really delete files, you unlink them. If the unlinked file pointer /etc/pihole/gravity.db was the last link to a file (this is the case) but any process (such as pihole-FTL) still has the file open the file will remain in existence until the last file descriptor referring to it is closed. Only then, the file is deleted and the space it was using is made available for reuse. However, this is not something triggered by the user but automatically done by the system for you.
The point where this is logged is where we close the existing handle to the old gravity.db and open the handle to the new (= updated) gravity.db.
To all: The bugfix has been merged into the beta code. Please go back on track with
pihole checkout ftl release/v5.0
Note that the CI is currently still building the binaries, they should be available latest in 10 minutes from now. All binaries have been built.
4 Likes
No more crash for me, use to crash after about 10 - 15 mins.