Skip to content

Conversation

bunnichx
Copy link
Contributor

  • During shutdown, there was conflict between journald and
  • umount.target resulting error logs on console. so added a
  • override.conf file to stop journald, when unmounting starts.

Merge Checklist

All boxes should be checked before merging the PR

  • The changes in the PR have been built and tested
  • [] cgmanifest file has been updated if required
  • Ready to merge

Description

"Failed unmounting var.mount" error was logged during os reboot. on investigating, there was a conflict between journald and umount.target which is keeping /var busy during unmounting. Added override.conf to overcome this issue. Ref ITEP-27253.

Any Newly Introduced Dependencies

How Has This Been Tested?

With changes, created raw image, loaded and on os reboot, not seeing any error log. Attached test results, to reported issue.

@bunnichx bunnichx requested a review from a team as a code owner September 17, 2025 13:00
@bunnichx bunnichx changed the title Add override.conf file for systemd-journald service file. Add override.conf for systemd-journald service file. Sep 17, 2025
# so adding below entry to systemd-journald.service, to stop journald
# when system starts to unmount.
[Unit]
After=umount.target
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This tells systemd to start the systemd-journald.service only after the umount.target has been reached - where umount.target is part of the shutdown. This means systemd-journald.service won't be running during normal system uptime.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @yepmunchun ,
I do see that systemd-journald.service is running during system uptime. verified through sudo systemctl status systemd-journald.service command and also observed logs are getting logged on execution i.e sudo journalctl -f. Attaching the log for reference.
journal.log

@yepmunchun
Copy link
Contributor

Instead of overriding the systemd-journald.service, have you tried stopping the systemd-journal-flush.service?

@bunnichx
Copy link
Contributor Author

bunnichx commented Oct 3, 2025

Instead of overriding the systemd-journald.service, have you tried stopping the systemd-journal-flush.service?

Hi @yepmunchun,
Couldnt test due to kernel issue on latest code. Today, tried stopping above service in %preun scriplet of spec file. With this change, issue still occurs.

- During shutdown, there was conflict between journald and
- umount.target resulting error logs on console. so added a
- override.conf file to stop journal-flush when unmounting starts.

Signed-off-by: Unniche, BasavarajX <[email protected]>
@bunnichx bunnichx force-pushed the fix-error-logs-reboot branch from 9d1fed7 to bb14467 Compare October 17, 2025 12:04
@bunnichx bunnichx requested a review from yepmunchun October 17, 2025 12:04
# https://fedoraproject.org/wiki/Changes/Systemd_presets_for_user_units.
systemctl preset-all &>/dev/null || :
systemctl --global preset-all &>/dev/null || :
systemctl daemon-reload &>/dev/null ||:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we do not need this

# changelog here.
%changelog
* Tue Oct 17 2025 Basavaraj unniche <[email protected]> - 255-30
- Add override.conf to systemd-journal-flush.service to fix conflict issues
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Filename not override.conf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants