** Description changed:
This is coming from our UTAH testing. The main log snippet is:
[ 9.351693] systemd[1]: systemd-journald.service: Main process exited,
code=dumped, status=4/ILL
[ 9.351824] systemd[1]: systemd-journald.service: Failed with result
'core-dump'.
[ 9.352023] systemd[1]: Failed to start systemd-journald.service - Journal
Service.
[FAILED] Failed to start systemd-journald.service - Journal Service.
See 'systemctl status systemd-journald.service' for details.
+ This happens over and over again, and several systemd-* units also fail
+ as dependencies. I've attached the full logs to this bug.
- This happens over and over again, and several systemd-* units also fail as
dependencies. I've attached the full logs to this bug.
+ This is with image dated 2025-10-27, with sha256sum
+ 628691f031bfebc9fc8728431e19fa380b1a9cd474f7d7cd294b13ad54445bfa
** Changed in: ubuntu
Assignee: (unassigned) => Frank Heimes (fheimes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2130002
Title:
Resolute s390x server live images have systemd-journald.service
starting and crashing in a loop
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2130002/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
