January 11, 20233 yr Currently, every 2 weeks or so, I start to get a /var/log getting full warning. At current rate, I would need at least one reboot within a month to clear it This is not a question about what is in the logs. I can always reduce some logs, but that will probably only change how long it takes to fill up. What is recommended sizing methodology to keep going indefinitely without needing a reboot. Let's say I don't need more than 1 month of logs and I can come up with a size (let's assume 300MB) that would fulfill it... * is it possible to change tmpfs size permanently from 128MB to higher. I have RAM to allocate * are there other logrotate of similar mechanisms recommended to setup how much to keep? I can try to do things the usual Linux way and then stuff things into config/go, but I am looking for the unraid way of managing this. Suggestions?
January 11, 20233 yr Community Expert 1 minute ago, apandey said: This is not a question about what is in the logs. Maybe it should be. Do you have atop installed from NerdPack?
January 11, 20233 yr Author 1 hour ago, trurl said: Maybe it should be. Do you have atop installed from NerdPack? It can be, but my concern is not the size of the log right now, but rather if I can tune it to a given size. Are there any concerns if I decide that I want 256MB instead of 128MB? It can be something as simple as wanting to go longer at any given logging rate I understand that 128MB ought to be enough for everyone, but what if it's not?
January 11, 20233 yr Community Expert Just now, apandey said: It can be The reason I asked is because atop is notorious for filling log space with its own logs.
January 11, 20233 yr Community Expert Solution 1 hour ago, apandey said: into config/go That is the usual method mount -o remount,size=384M /var/log
January 11, 20233 yr Author 1 hour ago, trurl said: The reason I asked is because atop is notorious for filling log space with its own logs. Thanks. I don't have atop. All of my excess logs are something that I know. They largely fall into cases where I want to defer the solution to later for various reasons. One example is link up/down spam on P2P 10gbe DAC connection which shows up when the other side of link sleeps/wakes. Some are application stuff I want to look at later when I have free time In all cases, it's not runaway logging. Just a bit more that will can be managed with a different sizing Thanks for confirming the remount solution. I'll use that for now
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.