[SOLVED] System Log - Live Mode stopped working

[Pato_77]

Hi all,

Since yesterday, 07-06-2026 12:46:26pm my node isn't showing any more new log messages in System Log (GUI) - Live Mode.
It's stuck at the last massage on the date just mentioned before.

I did had an error during the night regarding the intel nic:

kernel: e1000e 0000:00:19.0 nic0: Detected Hardware Unit Hang

Supposedly solved it by a solution given by a Reddit-user, referring to a post here on the Proxmox forum:
intel-nic-e1000e-hardware-unit-hang

I do can call up an overview from date till date. When I call up a date-to-date overview, I've noticed the order of showing the messages (earliest to latest) is completely mixed up. It starts on top, scrolling downwards time goes up, all of a sudden a time jump and starts going backwards.

I have log2ram and logrotate installed, should this be of any help
Tried to deactivate both, use default configuration, not solving the problem.

Deleting all log files, would that help (which log files should I need to delete??)?
Any suggestions how I can check if some involved service is still active or needs to be reactivated?

Actually don't want to reinstall Proxmox just for this. Anybody knows how I can fix this?

(Running Proxmox v9.2.3)

Thanks.

[UPDATE: 08-06-2026]
Solved it by completely deleting the journal logs on disk. Reboot and it's writing again. I guess the log file was corrupted or something.

 

[YaZoal]

Thanks for sharing the workaround.
You can mark the thread as solved by editing your post and selecting '[SOLVED]' from the drop-down menu next to the title.

 

[clangren]

@Pato_77 Thanks for the post and workaround.

We have a small 4-node cluster, running Proxmox 9.2.11, all VMs and LXCs fully up-to-date thru yesterday. Primarily run debian trixie vms.

Had the same issue - all 4 nodes - no log data displaying in System Log tab in the GUI. Logging was fine and visible from journalctl at the command line.

It seems (from having 4 chances to try) the command to let System Logs display again was: journalctl --vacuum-time="XX"

With "XX" being 7d or 1s or whatever you want the setting to be. We used both 7d and 1s successfully.

We did not need to stop and start systemd-journald.service and we did not need to reboot. Just have journalctl "touch" the logs and they immediately began displaying in the GUI tab.

 

[Pato_77]

@Pato_77 Thanks for the post and workaround.

We have a small 4-node cluster, running Proxmox 9.2.11, all VMs and LXCs fully up-to-date thru yesterday. Primarily run debian trixie vms.

Had the same issue - all 4 nodes - no log data displaying in System Log tab in the GUI. Logging was fine and visible from journalctl at the command line.

It seems (from having 4 chances to try) the command to let System Logs display again was: journalctl --vacuum-time="XX"

With "XX" being 7d or 1s or whatever you want the setting to be. We used both 7d and 1s successfully.

We did not need to stop and start systemd-journald.service and we did not need to reboot. Just have journalctl "touch" the logs and they immediately began displaying in the GUI tab.

Dear,

Glad this worked out for you.
Though, for me the issue came back again and this work around didn't work anymore.

The working solution for me, is modifying the journald.conf file. Now all my node are up te date, and working with logrotate/log2ram/Live mode System logs working.

See this link with my post where I posted my solution:

kernel-7, log2ram and effect on live mode system logs.