root partition full [Solved]

[Stevo]

Yes, go ahead and get rid of them.

But they'll come back and start growing like crazy again, so a separate thread will be about what's making them so big (spamming them).

[whbr]

I took from your previous post that I could remove them so ran the rm command from the terminal and it certainly had the desired effect of freeing up a lot of space on root. I am curious as to how this came to pass, if there is anything else I should be looking out for. I leave this out there for a while to see if anyone else have any thoughts they'd like to share. But so far, thanks a million for your prompt assistance and kind suggestions.

[whbr]

I missed your reply Stevo. I'll keep and eye on this for a while and see about a new thread.

[j2mcgreg]

@whbr wrote:

I am curious as to how this came to pass, if there is anything else I should be looking out for

You may never find what's causing the logging function to run amok, but on your next install you can restrict the logs' size by creating a separate partition: /var/log and setting its size to about two GiB.

[Stuart_M]

Here are two MX Linux threads that are related to the issue of the /var/log/syslog and /var/log/kern.log getting excessively large. The first Bullet-Point link has a two solutions (Post #43 is one and Post #30 is the other, which just gives a link to another forum and solution). The second Bullet-Point link is not really a "fix" but more accurately a work-around or "Band-Aid fix" because it does not identify the root cause of the problem. It shows how to limit the size of the log files.

• viewtopic.php?p=676749#p676749 "Var log disk space issue" is a March 2022 Post #43 that contains the solution (the problem was the USB wi-fi adapter was turned off and a PCI wi-fi adapter was turned on).
  
  Post #25 said the errors stopped after changing the wi-fi module.
  
  Post #30 linked to a thread on the proxmox.com forum that had the same problem and solved by replacing a NIC (Network Interface Card) as shown here https://forum.proxmox.com/threads/solve ... ost-228396.

• viewtopic.php?p=759430#p759430 "System continues to grow up, MX-23" is a January 2024 Post #9 that shows how to limit the maximum size of the log, further amplified in "Charlie Brown's" Post #18 that said:

  (... So, what we do is: Limit the size, and say when it exceeds 1M it'll create a second (new) file to go on... however the number of files are also limited (to 4 by default, which we can change), that means: it'll be cleaning all the time "by itself" as a result (removing the oldest file and creating anew)

  Post #20 gives additional information on how to limit the size.

[whbr]

I've been watching the /var/log files and as suggested by Stevo they are slowly ballooning. I think if one of the admins wanted to mark this solved that would be good. I know what the problem is and that was the purpose of the original post. I'll putter with this as I have time and if I come up with anything useful will start a new thread, as recommended. Thanks for all your attention to my problem.

[richb]

@whbr
You as the original poster mark the post that solves your issue by clicking on the check mark at the top of that post.

[fehlix]

I know what the problem is and that was the purpose of the original post.

Mind you telling us, what the issue was and what you changed to fix it. Potential some kernel-bootparameter to avoid spamming the log-files.
OTOH, ok ignoring the original issue and just keep the logfiles small by removing, e.g with logrotate is a reasonable workaround option, but not what I would call fix.