Proxmox 8.0.3 systemd-journald.service It gives an error and the system stops

kesen

New Member
Sep 25, 2023
8
2
3
Hello Friends, I am very new to Proxmox systems. I installed Proxmox 8.0.3 version on HP DL380 GEN-9 Server. With ZFS Raid. and I added 1 storage as ZFS2 Raid. Everything went well until now (1 week). But now something is wrong. I see the error appearing below and it's pages long. The server stops responding and of course the VMs are down. Proxmox cannot be accessed via web or SSH. It gets better after restarting the server, but it reoccurs after a few hours.
I have no idea what I can check or where the problem might be coming from.

Since I thought everything was going well, I ran the VMs I created live and I'm having problems.




systemd[1]: systemd-journald.service: Unit process 167**** (systemd-journal) remains running after unit stopped.
systemd[1]: systemd-journald.service: Unit process 167**** (systemd-journal) remains running after unit stopped.
systemd[1]: systemd-journald.service: Unit process 167**** (systemd-journal) remains running after unit stopped.
systemd[1]: systemd-journald.service: Unit process 167**** (systemd-journal) remains running after unit stopped.
systemd[1]: systemd-journald.service: Unit process 167**** (systemd-journal) remains running after unit stopped.
systemd[1]: systemd-journald.service: Unit process 167**** (systemd-journal) remains running after unit stopped.
systemd[1]: systemd-journald.service: Unit process 167**** (systemd-journal) remains running after unit stopped.
systemd[1]: systemd-journald.service: Unit process 167**** (systemd-journal) remains running after unit stopped.
systemd[1]: systemd-journald.service: Unit process 167**** (systemd-journal) remains running after unit stopped.
.....
.....
.....

systemd[1]: failed to start systemd-journald.service - journal Service.
systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 176.
systemd[1]: Stopped systemd-journald.service - Journal Service.

systemd[1]: systemd-journald.service: Found left-over process 1993**** (systemd-journal) in control group wile starting unit. Ignoring.
systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies
systemd[1]: systemd-journald.service: Found left-over process 1993**** (systemd-journal) in control group wile starting unit. Ignoring.
systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies
systemd[1]: systemd-journald.service: Found left-over process 1993**** (systemd-journal) in control group wile starting unit. Ignoring.
systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies
systemd[1]: systemd-journald.service: Found left-over process 1993**** (systemd-journal) in control group wile starting unit. Ignoring.
systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies
systemd[1]: systemd-journald[1109665]: File /var/log/journal/xxxxxxxxxxxxxxxxxx/system.journal corrupted or uncleanly shut down, renaming and replacing.
systemd[1]: systemd-journald.service: start operation timed out. Terminating.
.....
.....
.....

systemd[1]: systemd-journald.service: Killing process 167**** (systemd-journal) with signal SIGKILL.
systemd[1]: systemd-journald.service: Killing process 167**** (systemd-journal) with signal SIGKILL.
systemd[1]: systemd-journald.service: Killing process 167**** (systemd-journal) with signal SIGKILL.
systemd[1]: systemd-journald.service: Killing process 167**** (systemd-journal) with signal SIGKILL.
systemd[1]: systemd-journald.service: Killing process 167**** (systemd-journal) with signal SIGKILL.
systemd[1]: systemd-journald.service: Killing process 167**** (systemd-journal) with signal SIGKILL.
systemd[1]: systemd-journald.service: Killing process 167**** (systemd-journal) with signal SIGKILL.
systemd[1]: systemd-journald.service: Killing process 167**** (systemd-journal) with signal SIGKILL.
.....
.....
.....

systemd[1]: systemd-journald.service: Processes still aruund after SIGKILL. Ignoring.
 

Attachments

  • 2.jpg
    2.jpg
    302.8 KB · Views: 11
  • 3.jpg
    3.jpg
    441.1 KB · Views: 10
  • 1.jpg
    1.jpg
    782.7 KB · Views: 11
Last edited:
Sadly, none of the error messages is helpful in order to determine what went wrong. Can you try to post the output of dmesg (please in code tags)
 
Thanks for the reply, I just saw what you wrote. I'm looking for a solution.
The entire code did not fit on the page. The entire thing is available in the attachment.

(I revised the attached dmesg file.)
 

Attachments

  • dmesg.txt
    87.5 KB · Views: 4
Last edited:
Hello,
I'm having the same problem again. If downgrade ProxMox to version 7 will it be more stable?
I don't know if I can switch from V8 to V7. I don't know if it will be of any use?

Is there anyone with knowledge who can guide me about this error and what I can do?
 
Last edited:
Hello,
Thank you for trying to help and thank you for the answers.When I turned off all backup schedules, the problem seemed to be resolved.
I haven't experienced any system fault in 24 hours. I will examine it, but I cannot be at peace without making a backup.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!