00:45 <RoyK> any idea why armbian won't /root/.bashrc when I login with ssh?

01:04 <TRS-80> something something interactive login (maybe?)

01:46 <DC-IRC> [Discord] <menu> how do i disable ramlog (it keeps filling up) and write logs to my SSD instead?

01:59 <DC-IRC> [Discord] <menu> specifically, i'm having an issue where `/var/log` fills, causing IO errors

01:59 <DC-IRC> [Discord] <menu> ```

01:59 <DC-IRC> [Discord] <menu> root@armbian:~# df -h /var/log

01:59 <DC-IRC> [Discord] <menu> Filesystem Size Used Avail Use% Mounted on

01:59 <DC-IRC> [Discord] <menu> /dev/zram1 47M 46M 0 100% /var/log

01:59 <DC-IRC> [Discord] <menu> ```

03:50 <DC-IRC> [Discord] <Werner> Check /etc/default/armbian-*

03:51 <DC-IRC> [Discord] <Werner> However since these 50M are actually compressed I'd prefer digging for the cause that fills it up.

03:53 <DC-IRC> [Discord] <Werner> 50M of compressed text is actually a lot

10:55 <DC-IRC> [Discord] <menu> proxmox, logging to `/var/log/pve`, wouldn't be an issue if i wasn't churning through VMs

10:55 <DC-IRC> [Discord] <menu> i don't really know what i'm doing to disable it, and don't want to break anything permanently

12:47 <DC-IRC> [Discord] <Werner> There should be two files, one is ramlog and one is zram or something. you want to set enabled=false in ramlog. If you don't want to use compressed swap in memory you can disable zram as well. Generated a standard swapfile on your nvme and use that instread.

13:04 <DC-IRC> [Discord] <menu> with ramlog `enabled=false` will it just log to disk as i'd normally expect? the VM is on an NVME that's capable of handling it, although it makes sense why it's the default to protect the SD card

13:05 <DC-IRC> [Discord] <menu> i don't really understand having swap in memory, my understanding of swap is that it's for swapping data in an out of memory

13:07 <DC-IRC> [Discord] <Werner> You are correct. However sdcard are no good for having swap on. Wearing out quickly and are way too slow to be effective. So armbian takes half of available memory, compresses it and adds it as swap to get a little more out of it. Back in the days when SBCs had 256 or 512M only this way very helpful. Does not make much sense with 4G and more devices though. Depends on user scenario though

13:08 <DC-IRC> [Discord] <Werner> Yes, every 10 minutes if you did not adjust fstab as well. By default armbian writes changes every 10 minutes (or 600 seconds) to sd to expand its lifetime. Not needed for nvme of course

13:10 <DC-IRC> [Discord] <menu> so it's running a ramdisk, compressing the ramdisk, then running swap in the compressed ramdisk? that's... actually genius

13:11 <DC-IRC> [Discord] <Werner> Yes

13:45 <DC-IRC> [Discord] <menu> i'll turn both off then, ty @werner, you're incredibly helpful <3

13:45 <DC-IRC> [Discord] <Werner> Welcome

13:45 <RoyK> I have another suggestion

13:46 <RoyK> First, what you see in df, isn't compressed - I just doublechecked

13:46 <RoyK> it's the raw data - compression happens after that, apparently

13:46 <RoyK> otherwise you'd see difference between du -sch /var/log and du -sch --apparent-size /var/log

13:46 <RoyK> which you don't

13:48 <RoyK> second, keeping the logs small, is prime for having them on zram, so I'd suggest setting up a syslog host to receive the data and configure rsyslogd to log everything to @mylogserver.my.tld

13:49 <RoyK> third, change logrotate, at least for proxmox, to rotate the local logs frequently, a lot more than the defaults. You'll have a copy of them on the loghost anyway

13:50 <DC-IRC> [Discord] <rkarlsba> …and there I was on discord too 🙂

13:50 <DC-IRC> [Discord] <rkarlsba> @menu those above were for you, sir

13:51 <DC-IRC> [Discord] <rkarlsba> @menu those above were for you, madame

13:53 <DC-IRC> [Discord] <menu> unfortunately most of that's gone straight over my head, logging isn't something i've ever actually bothered with, because i usually know what the problem is already (it's PEBCAK, always PEBCAK)

13:55 <DC-IRC> [Discord] <menu> huh, there's a `./armbian-allwinner-battery` in the generic UEFI build

13:56 <DC-IRC> [Discord] <Werner> never seen that before

14:00 <DC-IRC> [Discord] <menu> oop wait no i was in the wrong machien 🤣

14:09 <DC-IRC> [Discord] <menu> ~~huh, there's a `./armbian-allwinner-battery` in the generic UEFI build~~

22:10 <DC-IRC> [Discord] <lanefu> the UEFI ARM64 image would be best. mainline because proxmox is providing a generic UEFI for grub to boot from. The opi5 image wouldn't work because it's uboot and needs to boot real hardware

22:10 <DC-IRC> [Discord] <lanefu> the armbian qemu image is unique iirc and actually is for an edge case for using qemu uboot rather than UEFI (if its the same one that i setup years ago)

22:12 <DC-IRC> [Discord] <lanefu> the UEFI ARM64 image would be best. mainly because proxmox is providing a generic UEFI for grub to boot from. The opi5 image wouldn't work because it's uboot and needs to boot real hardware

22:12 <DC-IRC> [Discord] <lanefu> the armbian qemu image is unique iirc and actually is for an edge case for using qemu uboot rather than UEFI (if its the same one that i setup years ago)

22:12 <DC-IRC> [Discord] <menu> i've got *one of them* (i don't remember which, but it boots, which is the main thing)

22:13 <DC-IRC> [Discord] <menu> iirc it was the generic UEFI, would rather something bootable with SeaBIOS but it *works* and that's what matters