Add override.conf for systemd-journald service file. #446
Conversation
- 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. Signed-off-by: Unniche, BasavarajX <[email protected]>
bunnichx
changed the title
| # so adding below entry to systemd-journald.service, to stop journald | ||
| # when system starts to unmount. | ||
| [Unit] | ||
| After=umount.target |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
|
Instead of overriding the |
Hi @yepmunchun, |
Merge Checklist
All boxes should be checked before merging the PR
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.