I have the same issue and the log says there would be no space left on the SD-card. But there is about 4 GB of free space! The issue suddenly appeared some days ago but I did not changed the setup of the Pi or copied large files.
How do you know this?
2021-05-17 07:11:46: (mod_accesslog.c.180) writing access log entry failed: /var/log/lighttpd/access.log No space left on device
What are the outputs of the following from the Pi terminal:
df -h
ls -lha /etc/pihole
ls -lha /var/log/pihole*
How do you know this?
Because of df -h and RPI-Monitor. The latter shows 4.71 GB free on / at the moment and df -h this:
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
/dev/root 59G 54G 2,3G 96% /
devtmpfs 236M 0 236M 0% /dev
tmpfs 241M 1,3M 239M 1% /dev/shm
tmpfs 241M 6,5M 234M 3% /run
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 241M 0 241M 0% /sys/fs/cgroup
/dev/mmcblk0p1 43M 23M 20M 53% /boot
/dev/sda1 7,5G 3,7G 3,9G 49% /media/extern
tmpfs 49M 0 49M 0% /run/user/1000
tmpfs 49M 0 49M 0% /run/user/998
In wonder why there is a discrepancy between both tools which was not the case when I once compared both. It was some weeks ago, though.
Just now, when I writing this, the Pihole ran fine since I posted the question this afternoon. I have just opened the section "Tools" in the web interface and it suddenly showed this "undefined%" message and deleted the graphs. Nothing is written in the "Pi-Hole diagnosis" section.
Not related to the problem but its generally advised/best practice to expand storage if more than 80% full.
This because file fragmentation will increase because there is no continuous diskspace available for larger files.
And some operations like for example defraging needs the extra fee space.
What's the output of
Below is disk usage by Pi-hole (approximatly):
pi@ph5b:~ $ du -chs /usr/bin/pihole-FTL /etc/pihole/ /opt/pihole/ /var/www/html/{admin,pihole} /var/log/pihole*
12M /usr/bin/pihole-FTL
42M /etc/pihole/
236K /opt/pihole/
13M /var/www/html/admin
32K /var/www/html/pihole
0 /var/log/pihole
0 /var/log/pihole-FTL.log
60K /var/log/pihole-FTL.log.1
4.0K /var/log/pihole-FTL.log.2.gz
8.0K /var/log/pihole-FTL.log.3.gz
856K /var/log/pihole.log
812K /var/log/pihole.log.1
28K /var/log/pihole.log.2.gz
68K /var/log/pihole.log.3.gz
76K /var/log/pihole.log.4.gz
52K /var/log/pihole.log.5.gz
4.0K /var/log/pihole_updateGravity.log
68M total
Below how you can inspect particular folders:
Here are the outputs. By the way, I opened the web interface for the first time today and it reports "Lost connection to api".
ls -lha /etc/pihole
insgesamt 482M
drwxrwxr-x 3 pihole pihole 4,0K Mai 19 22:42 .
drwxr-xr-x 115 root root 12K Mai 19 16:57 ..
-rw-r--r-- 1 root root 118 Jul 22 2020 adlists.list
-rw-r--r-- 1 root root 38 Mai 3 2020 black.list
-rw-r--r-- 1 root root 0 Dez 11 12:46 custom.list
-rw-r--r-- 1 pihole pihole 0 Mai 19 17:01 dhcp.leases
-rw-r--r-- 1 root root 618 Apr 23 21:00 dns-servers.conf
-rw-r--r-- 1 root root 18 Mai 19 19:21 GitHubVersions
-rw-rw-r-- 1 pihole pihole 31M Mai 19 22:42 gravity.db
-rw-r--r-- 1 root root 2,9M Mai 3 2020 gravity.list
-rw-r--r-- 1 root root 1,1K Apr 23 21:01 install.log
-rw-r--r-- 1 root root 1,6M Mai 19 22:39 list.1.raw.githubusercontent.com.domains
-rw-r--r-- 1 root root 95 Mai 19 22:39 list.1.raw.githubusercontent.com.domains.sha1
-rw-r--r-- 1 root root 403K Apr 23 21:02 list.3.sysctl.org.domains
-rw-r--r-- 1 root root 80 Apr 23 21:02 list.3.sysctl.org.domains.sha1
-rw-r--r-- 1 root root 521 Apr 23 21:02 list.5.s3.amazonaws.com.domains
-rw-r--r-- 1 root root 86 Apr 23 21:02 list.5.s3.amazonaws.com.domains.sha1
-rw-r--r-- 1 root root 43K Apr 23 21:02 list.6.s3.amazonaws.com.domains
-rw-r--r-- 1 root root 86 Apr 23 21:02 list.6.s3.amazonaws.com.domains.sha1
-rw-r--r-- 1 root root 8,4M Mai 19 22:39 list.8.www.github.developerdan.com.domains
-rw-r--r-- 1 root root 97 Mai 19 22:40 list.8.www.github.developerdan.com.domains.sha1
-rw-r--r-- 1 root root 688K Mai 19 22:40 list.9.www.github.developerdan.com.domains
-rw-r--r-- 1 root root 97 Mai 19 22:40 list.9.www.github.developerdan.com.domains.sha1
-rw-r--r-- 1 root root 20 Mai 20 15:30 localbranches
-rw-r--r-- 1 root root 45 Mai 19 22:41 local.list
-rw-r--r-- 1 root root 42 Mai 20 15:30 localversions
-rw-r--r-- 1 root root 234 Apr 23 21:00 logrotate
-rw-r--r-- 1 pihole pihole 2,6M Apr 23 21:00 macvendor.db
drwxr-xr-x 2 root root 4,0K Mai 11 2020 migration_backup
-rw-rw-r-- 1 pihole pihole 15 Apr 23 21:01 pihole-FTL.conf
-rw-r--r-- 1 pihole pihole 0 Mai 14 10:08 pihole-FTL.db
-rw-r--r-- 1 pihole pihole 434M Mai 14 00:50 pihole-FTL-old.db
-rw-r--r-- 1 root root 551 Mai 19 14:14 setupVars.conf
-rw-r--r-- 1 root root 564 Apr 23 21:00 setupVars.conf.update.bak
ls -lha /var/log/pihole*
-rw-r--r-- 1 root pihole 40K Mai 19 16:50 /var/log/pihole_debug.log
-rw-r--r-- 1 pihole pihole 346K Mai 20 10:18 /var/log/pihole-FTL.log
-rw-r--r-- 1 pihole pihole 869K Mai 20 00:00 /var/log/pihole-FTL.log.1
-rw-r--r-- 1 pihole pihole 42K Mai 19 00:00 /var/log/pihole-FTL.log.2.gz
-rw-r--r-- 1 pihole pihole 806K Mai 20 10:19 /var/log/pihole.log
-rw-r--r-- 1 pihole pihole 5,1M Mai 20 00:00 /var/log/pihole.log.1
-rw-r--r-- 1 pihole pihole 211K Mai 19 00:00 /var/log/pihole.log.2.gz
-rw-r--r-- 1 root root 2,5K Mai 16 04:49 /var/log/pihole_updateGravity.log
/var/log/pihole:
insgesamt 8,0K
drwxr-xr-x 2 pihole pihole 4,0K Mai 2 2019 .
drwxr-xr-x 7 root root 4,0K Mai 20 00:00 ..
What happend here? Did you modify your database?
[2021-05-19 16:48:27.382 25034/T25036] Client denied (at max capacity of 255): 527
[2021-05-19 16:48:27.383 25034/T25036] IPv4 telnet error: Success (0)
[2021-05-19 16:48:28.404 25034/T25036] Client denied (at max capacity of 255): 527
[2021-05-19 16:48:28.405 25034/T25036] IPv4 telnet error: Success (0)
[2021-05-19 16:48:29.425 25034/T25036] Client denied (at max capacity of 255): 527
[2021-05-19 16:48:29.426 25034/T25036] IPv4 telnet error: Success (0)
[2021-05-19 16:49:00.504 25034/T25039] SQLite3 message: no such table: network_addresses in "DELETE FROM network_addresses WHERE lastSeen < 1589899740;" (1)
[2021-05-19 16:49:00.507 25034/T25039] ERROR: SQL query "DELETE FROM network_addresses WHERE lastSeen < 1589899740;" failed: SQL logic error
[2021-05-19 16:49:00.510 25034/T25039] SQLite3 message: API call with invalid database connection pointer (21)
[2021-05-19 16:49:00.510 25034/T25039] SQLite3 message: misuse at line 165242 of [5d4c65779d] (21)
[2021-05-19 16:49:00.512 25034/T25039] Error while trying to close database: bad parameter or other API misuse
There are other issues in your debug log as well
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the enxb827eb04f4e7 interface:
192.168.100.100/24 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
PIHOLE_INTERFACE=enxb827eb04f4e7
IPV4_ADDRESS=192.168.0.100/24
I created a new database with the help of this post:
https://discourse.pi-hole.net/t/percentage-blocked-blinking-undefined/46792/8
I did not change anything else. I don't know what causes the issue with the IPv4 address.
So Pi-hole is occupying ~500M of space.
Compare this to:
Whatever consumes >50G of space on your file system isn't Pi-hole.
You probably should start looking at your other software.
Next to RPiMonitor, it seems you are running some kind of remote syncing software?
*** [ DIAGNOSING ]: Ports in use
*:51164 rslsync (IPv4)
*:51164 rslsync (IPv6)
*:8888 rslsync (IPv4)
*:8889 rpimonitor (IPv4)
Did you set a static IP address on your device hosting Pi-hole? Or made a DHCP reservation for this device on your router?
To correct for the changes IP address run pihole -r
and choose reconfiguration
.
I know what is occupying the space, it is Resilio Sync, but I don't know why Pihole reports there were too little disk space when there is enough. I have Pihole running for years and there were many situations where less disk space than 2 GB left. So, why does it not work anymore now?
*** [ DIAGNOSING ]: contents of /var/log/lighttpd
-rw-r--r-- 1 www-data www-data 20365 May 19 16:48 /var/log/lighttpd/error.log
-----head of error.log------
2021-05-17 07:11:40: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: Unknown: write failed: No space left on device (28)
Pi-hole or rather lighttpd
is just reporting what your OS returns: "No space left on device" indicates that the OS reported it cannot fulfill a write request.
There may be a multitude of reasons for that, e.g. because it run out of free blocks, or it exhausted its inode pool, or the mount you are writing to actually points to a smaller device, or it exceeded some quota, or...
The common solution would be removing unused files to free up disk space.
Because it's out of space.
This isn't going to help your free space issue. You have the old database (which will never change) at 434 MB, and now you are growing a new database that will eventually grow to about the same size.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.