Load main page and see multiple graphs.
See spinning icons, nothing loads. The device has been offline for more than 31 days. Possible problem with it populating empty graphs? Attempted a reinstall issue is still there on multiple browsers.
uqgoglo5cz
Here is one FAQ to read that may have a solution for you.
You can also flush the PiHole log with pihole -f or from the web admin screen on the [settings - system] page. Disable query logging and flush logs, then re-enable query logging.
If no success, we can try some more steps.
pihole -f gave some errors, no room left on device.
df -h shows
Filesystem Size Used Avail Use% Mounted on
udev 85M 0 85M 0% /dev
tmpfs 25M 4.1M 20M 17% /run
/dev/mmcblk0p1 117G 1.2G 115G 1% /
tmpfs 120M 0 120M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 120M 0 120M 0% /sys/fs/cgroup
tmpfs 120M 0 120M 0% /tmp
**log2ram 50M 50M 0 100% /var/log**
tmpfs 25M 0 25M 0% /run/user/0
tmpfs 25M 0 25M 0% /run/user/999
Im guessing I can manually purge some of these pihole logs in there?
What was the output from pihole -f
sed: can't read /etc/pihole/pihole-FTL.conf: No such file or directory
[i] Flushing /var/log/pihole.log ...error: destination /var/log/pihole.log.1.gz already exists, renaming to /var/log/pihole.log.1.gz-2018072601.backup
gzip: stdout: No space left on device
error: failed to compress log /var/log/pihole.log.1
error: destination /var/log/pihole-FTL.log.1.gz already exists, renaming to /var/log/pihole-FTL.log.1.gz-2018072601.backup
gzip: stdout: No space left on device
error: failed to compress log /var/log/pihole-FTL.log.1
error: destination /var/log/pihole.log.1.gz already exists, renaming to /var/log/pihole.log.1.gz-2018072601.backup
gzip: stdout: No space left on device
error: failed to compress log /var/log/pihole.log.1
error: destination /var/log/pihole-FTL.log.1.gz already exists, renaming to /var/log/pihole-FTL.log.1.gz-2018072601.backup
gzip: stdout: No space left on device
error: failed to compress log /var/log/pihole-FTL.log.1
[✓] Flushed /var/log/pihole.log
[✓] Deleted 0 queries from database
Your log to ram partition is too small to rotate logs. Try removing some of the old logs (the .gz ones) and try again.
I have the same issue on Fedora 28 on VirtualBox. It works blocking ads but get spinning graph.
Has this issue being resolved ?.
[ralph@linux ~]$ pihole -f
[sudo] password for ralph:
sed: can't read /etc/pihole/pihole-FTL.conf: No such file or directory
[✓] Flushed /var/log/pihole.log
[✓] Deleted queries from database
sed: can't read /etc/pihole/pihole-FTL.conf: No such file or directory
[✓] Flushed /var/log/pihole.log
[✓] Deleted 18 queries from database
This is the output from pihole -f
After performing the flush command I rebooted the device and the graphs work again.
I know its not a piehole questions but expanding the logs dir how would one go about that. Or decreasing the logs that pihole keeps so I can logrotate?
The size of the ramlog filesystem is set in the file /etc/default/ramlog
If there is a line which reads TMPFS_RAMFS_SIZE=50m, you can change it to the size you require. If there is no such line, you can add one using the above format.
After rebooting you can check the size the same way you did above, with
df -h
/etc/default/ramlog was empty so I added the command
TMPFS_RAMFS_SIZE=50m and rebooted. Did not resolve the issue.
Ran df -h and got the following reply.
[ralph@localhost ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 984M 0 984M 0% /dev
tmpfs 997M 0 997M 0% /dev/shm
tmpfs 997M 1.1M 996M 1% /run
tmpfs 997M 0 997M 0% /sys/fs/cgroup
/dev/mapper/fedora_localhost--live-root 29G 6.2G 21G 23% /
tmpfs 997M 12K 997M 1% /tmp
/dev/sda1 976M 183M 727M 21% /boot
tmpfs 200M 0 200M 0% /run/user/977
tmpfs 200M 36K 200M 1% /run/user/1000
/dev/sr0 56M 56M 0 100% /run/media/ralph/VBox_GAs_5.2.16
You already had a 50MB log2ram mount that was/is too small so whats the use of setting "TMPFS_RAMFS_SIZE=50m" ?
Better increase "SIZE":
https://github.com/azlux/log2ram#customize
Ohw. Ps. since df isnt showing the ram2log log2ram mount anymore, you probably killed it and need to remove previouse change in the "/etc/default/ramlog" file to get it to work again.
My problem is resolved. Ralph_Osle please make your own thread you are confusing people ( deHakkelaar ) who are trying to help you when they compare my logs with your issue.
Oops sorry for that.
How did you solve if I might ask ?
-Cleaned up log directory of all pihole logs so there was free space.
-After performing the flush command it still did not work, restarting FTL made no difference.
-I rebooted the device and the graphs work again.
Issues was low disk space for logrotate, and rebooting. Im sure retsarting all of piholes services would have been fine as well after the clean and flush.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.