Huge discrepancy in log file size, can't start log2ram
Hi - I am trying to use log2ram, but even though I have made the ram drive as large as 400M (ten+ times what I should need, it's a RPi with debian and recently put together), it crashes with the complaint that there isn't enough space for /var/hdd.log.
Running du -sh on /var/log gives me a total of 649M (!!) Running ls -sSh, however, only 13M (see below, and the directories below /var/log are all very small as well). I deleted old logs (.2+, .gz, etc) - nothing helps. Why that gigantic difference? Ideas what to look for? TIA! Code:
total 13M |
Something somewhere thinks it has a file open when it's orphaned. Try rebooting the Pi and see if that helps. It's possible something tried to delete or modify a file that was opened by something else and there's rogue file handles floating around.
|
Thanks. I thought I did try that and it didn't change. But tried again - still no good. du -sh /var/log still gets me 50ish times the directory size I get with ls -sSh /var/log. I am baffled ...
|
Try the following:
Code:
cd /var/log |
Ah. The journals directory had all that in it. I deleted them all and almost immediately one file came back at 17M and has since grown to 25M. Now I have to figure out who is so verbose. On first glance journalctl -n 50 shows nothing in the recent additions to the journal ….
|
All times are GMT -5. The time now is 04:24 PM. |