Hello.
I have used pihole for a couple of years now and have nothing but good things to say about it.
But there is a constant problem that I can't seem to be resolved.
My logs get full all the time.
I have disabled logs and changed the FTL log behaviour to rotate and keep only 1 day. Yet I still get this annoying error.
Could someone please help me change my settings so I won't get bugged by this message?
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
pihole -d
or do it through the Web interface:
Tools > Generate Debug Log
Also, please post the output of the following command from the Pi terminal:
ls -lha /etc/pihole
ls -lha /var/log/pihole
Hello jfb.
I had already done the normal cleanup that I do when this happens but please find below the results you asked for:
https://tricorder.pi-hole.net/5py7ygM6/
Results for ls -lha /etc/pihole
Blockquote~# ls -lha /etc/pihole
total 213M
drwxrwxr-x 3 pihole pihole 4.0K Sep 11 05:00 .
drwxr-xr-x 109 root root 4.0K Sep 9 12:42 ..
-rw-r--r-- 1 root root 65 May 24 22:48 adlists.list
-rw-r--r-- 1 pihole pihole 65 Jul 14 2022 adlists.list.old
-rw-r--r-- 1 pihole pihole 0 May 19 2022 custom.list
-rw-r--r-- 1 pihole pihole 1.7K Sep 11 04:55 dhcp.leases
-rw-r--r-- 1 pihole pihole 651 Aug 2 03:41 dns-servers.conf
-rw-rw-r-- 1 pihole pihole 11M Sep 8 03:25 gravity.db
-rw-rw-r-- 1 pihole pihole 11M Sep 1 03:25 gravity_old.db
-rw-r--r-- 1 pihole pihole 824 Aug 2 03:42 install.log
-rw-r--r-- 1 root root 3.6M Sep 8 03:25 list.1.raw.githubusercontent.com.domains
-rw-r--r-- 1 root root 95 Sep 8 03:25 list.1.raw.githubusercontent.com.domains.sha1
-rw-r--r-- 1 root root 136K Aug 2 03:42 list.2.adaway.org.domains
-rw-r--r-- 1 root root 80 Aug 2 03:42 list.2.adaway.org.domains.sha1
-rw-r--r-- 1 pihole pihole 65 Sep 8 03:25 local.list
-rw-r--r-- 1 pihole pihole 240 Sep 3 06:54 logrotate
-rw-r--r-- 1 pihole pihole 237 May 19 2022 logrotate-custom
-rw-r--r-- 1 pihole pihole 3.0M May 24 22:12 macvendor.db
drwxr-xr-x 2 pihole pihole 4.0K May 19 2022 migration_backup
-rw-rw-r-- 1 pihole pihole 159 Aug 22 10:29 pihole-FTL.conf
-rw-r--r-- 1 root root 158 Sep 3 06:23 pihole-FTL.config
-rw-rw-r-- 1 pihole pihole 186M Sep 11 05:00 pihole-FTL.db
-rw-r--r-- 1 pihole pihole 593 Sep 5 08:57 setupVars.conf
-rw-r--r-- 1 pihole pihole 560 Jul 9 2022 setupVars.conf.update.bak
-rw-r--r-- 1 pihole pihole 325 Sep 10 13:50 versions
Results for ls -lha /var/log/pihole
Blockquote total 52K
drwxr-xr-x 2 pihole pihole 4.0K Sep 11 04:59 .
drwxr-xr-x 14 root root 4.0K Sep 9 12:42 ..
-rw-r--r-- 1 pihole pihole 1.9K Sep 11 05:00 FTL.log
-rw-r----- 1 root pihole 39K Sep 11 04:59 pihole_debug.log
My normal routine when this happens if to run the following commands:
cd /var/log/
rm *.log
cd /var/log/pihole/
rm *.log
journalctl --vacuum-size=1M
Your debug log shows that you are using zram to mount /var/log, and have assigned just 49M of RAM for its storage:
*** [ DIAGNOSING ]: Disk usage
Filesystem Size Used Avail Use% Mounted on
udev 421M 0 421M 0% /dev
tmpfs 99M 856K 98M 1% /run
/dev/mmcblk1p1 29G 1.9G 27G 7% /
tmpfs 493M 5.4M 487M 2% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 493M 4.0K 493M 1% /tmp
/dev/zram1 49M 28M 18M 62% /var/log
log2ram 128M 93M 36M 73% /var/log.hdd
28M of that are already used, and according to your ls output, Pi-hole is merely taking up some 41K of it.
When your log space is full, it's quite kely that Pi-hole is just reporting storage exhaustion, not necessarily because Pi-hole's logs themselves would contribute substantially.
You should either increase your zram storage, or mount /var/log on your sd card.
Hello Bucking Horn.
Thank you for having a look.
Would you be able to tell me how to mount /var/log to the SD card instead of on Zram?
Actually. I tried increasing the size of Zram following a guide online.
Could you please have a look at the new debug file to see if it looks better to you?
https://tricorder.pi-hole.net/D9u0dlPg/
Thank you.
Not in detail, as I do not know by which means you setup your zram storage.
In general, you'd have to edit your /etc/fstab and possibly revert the manual zram changes you've applied there. But if you'd enabled zram logging via some UI tool, you may want to use that to reconfigure it.
Your most recent debug log shows that your /var/log space increased to some ~240MBs:
*** [ DIAGNOSING ]: Disk usage
Filesystem Size Used Avail Use% Mounted on
udev 421M 0 421M 0% /dev
tmpfs 99M 868K 98M 1% /run
/dev/mmcblk1p1 29G 1.9G 27G 7% /
tmpfs 493M 736K 492M 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 493M 4.0K 493M 1% /tmp
/dev/zram1 242M 18M 207M 8% /var/log
log2ram 128M 17M 112M 13% /var/log.hdd
tmpfs 99M 0 99M 0% /run/user/0
I can't tell if this would be sufficient for your ordinary daily usage, so you may want to monitor this. Also, your system may yet run into extraordinary conditions exhausting even that enlarged space.
In any case, note that by logging to ram, you'll be using all log information upon reboot.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.