Dear all,
Since a while I'm having the problem that updating to kernel 7.0.6+ my System Log in Live Mode wasn't updating anymore.
See my earlier post here:
Live logs not updating after boot finishes kernel 7-0-14-1-pve
Meanwhile working on an Ansible Playbook to install Proxmox fresh, I was wondering if maybe some configuration I did together with updating to Kernel 7 broke something.
Services that I have deactivated: Postfix / pve-ha-crm / pve-ha-lrm / corosync / spiceproxy. With this config, and Kernel older than 7.0.12 all worked fine.
After each activation of a service, I deleted the Journald logs and rebooted proxmox.
1. I started with activating Postfix again ==> Did something but broke again after reboot.
2. Corosync + pve-ha-crm + pve-ha-lrm ==> Did nothing and thus deactivated again.
3. spiceproxy ==> Did nothing and deactivated again.
Next step, checking on packages that I'm installing.
1. Started with logrotate and deactivated it. ==> Nothing changed, thus activated again.
2. Deactivated log2ram == == == > Live Mode started populating / updating again with log messages!!
Activated it again to double-check, Live Mode stopped populating messages again after boot was finished. Deactivated log2ram again and Live Mode is filling up with messages again as supposed to.
Haven't got around it yet what to do now. Leave log2ram deactivated, is there a configuration change I need to make that currently isn't working with the new Kernel?
Not sure if anybody still has a same issue, or perhaps has solved it...
I'm not an expert, and looking for suggestions where to begin trouble shooting with log2ram.
I'll keep fiddling around with this, hoping to find the solution. Should I find a working solution, I'll post it here.
Thanks in advance for your help and suggestions.
[UPDATE: 04-08-2026]
Dear all,
I just wanted to share a solution that is working for me.
After fiddling around a lot with the config files of log2ram and logrotate, I've started to check the config file of Journald (journald.conf).
With the below config, at least the two nodes that were presenting the problem have the Live Mode System Logs running the way supposed to.
Only not sure if for journals.conf one also can use an override config file...have to check this.
One thing is for sure, this config also goes into my Ansible playbook to apply standard to all my PVEs.
Since a while I'm having the problem that updating to kernel 7.0.6+ my System Log in Live Mode wasn't updating anymore.
See my earlier post here:
Live logs not updating after boot finishes kernel 7-0-14-1-pve
Meanwhile working on an Ansible Playbook to install Proxmox fresh, I was wondering if maybe some configuration I did together with updating to Kernel 7 broke something.
Services that I have deactivated: Postfix / pve-ha-crm / pve-ha-lrm / corosync / spiceproxy. With this config, and Kernel older than 7.0.12 all worked fine.
After each activation of a service, I deleted the Journald logs and rebooted proxmox.
1. I started with activating Postfix again ==> Did something but broke again after reboot.
2. Corosync + pve-ha-crm + pve-ha-lrm ==> Did nothing and thus deactivated again.
3. spiceproxy ==> Did nothing and deactivated again.
Next step, checking on packages that I'm installing.
1. Started with logrotate and deactivated it. ==> Nothing changed, thus activated again.
2. Deactivated log2ram == == == > Live Mode started populating / updating again with log messages!!
Activated it again to double-check, Live Mode stopped populating messages again after boot was finished. Deactivated log2ram again and Live Mode is filling up with messages again as supposed to.
Haven't got around it yet what to do now. Leave log2ram deactivated, is there a configuration change I need to make that currently isn't working with the new Kernel?
Not sure if anybody still has a same issue, or perhaps has solved it...
I'm not an expert, and looking for suggestions where to begin trouble shooting with log2ram.
I'll keep fiddling around with this, hoping to find the solution. Should I find a working solution, I'll post it here.
Thanks in advance for your help and suggestions.
[UPDATE: 04-08-2026]
Dear all,
I just wanted to share a solution that is working for me.
After fiddling around a lot with the config files of log2ram and logrotate, I've started to check the config file of Journald (journald.conf).
With the below config, at least the two nodes that were presenting the problem have the Live Mode System Logs running the way supposed to.
Only not sure if for journals.conf one also can use an override config file...have to check this.
One thing is for sure, this config also goes into my Ansible playbook to apply standard to all my PVEs.
Code:
[Journal]
...
...
#Storage=auto
Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitIntervalSec=30s
#RateLimitBurst=10000
SystemMaxUse=256M
SystemKeepFree=50G
SystemMaxFileSize=90M
SystemMaxFiles=12
#RuntimeMaxUse=
...
...
Last edited:
