-rw-r--r-- 1 root root 1.1K Jan 22 22:13 /etc/pihole/install.log
[✓] 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
[i] 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] Backing up /etc/dnsmasq.conf to /etc/dnsmasq.conf.old
[✓] man pages installed and database updated
This moves FTL to the release 5.0 branch, and it is expected that there is no output from the command. This is a method of minimizing the number of branches to download, since this will download with one of the subsequent commands.
This is a problem. What does df -ah show for disk space?
I don't know. I would have to look at the code or have one of the devs answer this.
This file is not where the blocklists are being stored. They are in /etc/pihole/gravity.db
What is the output of the following:
This was the problem. The disk mounted at /data was full. Now 18%
When the second disk (/data) was full the 'Disk space check' passed and 'Restarting FTL service' failed.
Probably because pihole-FTL.db is on the disk that had no free space.
[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] Web Interface: up to date
[i] FTL: up to date
[i] Warning: You are using FTL from a custom branch (release/v5.0) and might be missing future releases.
[✓] Everything is up to date!
Pi-hole version is v4.3.2-386-g29f06a4 (Latest: v4.3.2)
AdminLTE version is v4.3.2-357-g3cac308e (Latest: v4.3.2)
FTL version is vDev-021cd83 (Latest: v4.3.1)
Yes, you are up to date. The version numbers show that you are on a version that is 386 commits greater than 4.3.2. The version number is based on git tags and that isn't set stable during a beta test. I know that is kind of confusing but it's a limitation of how we currently distribute the software.