/var/log constantly full = at /dev/zram1

[pdieguez]

Armbianmonitor:

https://paste.armbian.com/diziviwajo

Hello all,

 

I am running an Orange Pi 5 board with Armbian on a SD Card and I realized that my /var/log path is constantly full, with it being at /dev/zram1

It gets full at 50Mb with the file /var/log/samba/cores/smbd/core taking up all the space

 

I have not managed to read this file, so I can't tell what kinds of errors are showing up. My OpenMediaVault and samba setup are running perfectly fine, and even though I delete this core file, it shows up again during reboot.

I have tried to set 

enable core files = no

in smb.conf

With no sucess. The file continues to show up during reboot.

 

Any ideas how to solve this?

 

Best regards

[ozacas]

Hi,

 

Writing logs to certain types of storage can shorten the lifetime of the media (although it can be difficult to identify the impact of lifetime of writing logs due to commercial sensitivity). To address this, Armbian uses memory (RAM) instead.

 

This can be disabled by editing /etc/default/armbian-zram-config and changing the line

ENABLED=true

 

at the risk of shortening the longevity of your storage. YMMV. You will need to reboot for the change to take effect.

 

If you prefer to alter logging level for samba, perhaps this is what you need (although 50MB is not a lot of logs these days) - https://wiki.samba.org/index.php/Setting_the_Samba_Log_Level

[JohnU]

I had the same problem with /var/log filling up.  It was causing Jellyfin playback to fail.  I tried disabling armbian-zram-config service in the config file, but then the /var/log got mounted to an armbian-ramlog device that is the same 50M size.  So I ended up changing the armbian-ramlog size to 500M in it's config file and re-enabling the armbian-zram-config service in it's config file.  Now it's once again mounted to /dev/zram1, but it's now 500M.

Edited March 22 by JohnU

[killronaldreagan]

I was looking for a solution to this for a long time before seeing John's post and figuring it out. Here's a more explicit explanation to hopefully help make this info easier to find.

This was tested and does work on both the Orange Pi 5 16GB, and the Orange Pi Zero 3 4GB. I haven't run into this issue on my x86 nodes as it doesn't appear zram exists on them at all on a fresh install.

If you go to the /etc/default directory, there should be a file called <distro>-ramlog. If you're on armbian it will be armbian-ramlog, for me on Debian it's called orangepi-ramlog.

In this file there will be a line reading

"SIZE=50M"

Simply edit this line to whatever value you'd like, and then reboot the device.

If rebooting the system will cause serious problems, you can use the following command on armbian:
 

service armbian-zram-config restart

Again, I'm using the official Orange Pi Debian image, so for me, the command would instead be as follows:
 

service orangepi-zram-config restart 

 

Don't panic if you notice that this command results in the creation of a zram2 and zram3, as these duplicates will automatically remove themselves the next time you reboot the machine

Edited 17 hours ago by killronaldreagan