k3s spontaneous implosion about k3s

[IngwiePhoenix]

Found it.

root@cluserboi /v/log# cat /etc/default/armbian-ramlog
# configuration values for the armbian-ram-logging service
#
# enable the armbian-ram-logging service?
ENABLED=false

k3s crashed because it ran out of logspace. That... is really... not good. o.o It should at least print something to STDERR imo.
Found it by chance because I forgot to add a path to df -h and saw the ramlog mount was full. Disabled, rebooted, and it's back online.

[brandond]

k3s crashed because it ran out of logspace. That... is really... not good. o.o It should at least print something to STDERR imo.

K3s does log to stderr/stdout. That is collected by systemd and logged to journald. I'm not sure exactly what journald does with logs when the host runs out of disk space, but I'm not sure it's something that K3s needs to be enhanced to handle better.