Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If a hardware error is cccurred, mcelog does not log into /var/log/messages after stopping systemd-journald #117

Open
zhuofeng6 opened this issue Sep 5, 2023 · 0 comments

Comments

@zhuofeng6
Copy link

zhuofeng6 commented Sep 5, 2023

Normally, if a hardware error occurs, mcelog writes the error to /var/log/messages.

If systemd-journald is restarted, mcelog still writes logs to /var/log/messages.

systemctl restart systemd-journald

image

But if I'm carrying out the following command (Because to stop systemd-journald, you need to stop systemd-journald-dev-log.socket and systemd-journald.socket.)

systemctl stop systemd-journald-dev-log.socket
systemctl stop systemd-journald.socket
systemctl stop systemd-journald
systemctl start systemd-journald

Then if a hardware error occurs, the log of the mcelog error is not written to /var/log/messages.
image

To continue writing logs to /var/log/messages, we need to restart mcelog.

Is this normal? or it is a bug in mcelog?

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

No branches or pull requests

1 participant