CentOS 7, Systemd,, And Message Floods
I’ve just updated a couple of servers, latest 7.3, and systemd is flooding dmesg, journalctl with info level messages… or maybe debug level 1.
Examples:
[ 478.258571] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/httpd_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookieC6 reply_cookie=0 error=n/a
[ 478.258971] systemd[1]: Got notification message for unit systemd-logind.service
[ 478.258980] systemd[1]: systemd-logind.service: Got notification message from PID 821 (WATCHDOG=1)
[ 478.258985] systemd[1]: systemd-logind.service: got WATCHDOG=1
What *is* all that garbage, and is there some way to turn it down to WARN
and ERR messages?
mark
3 thoughts on - CentOS 7, Systemd,, And Message Floods
if grep -q debug /proc/cmdline; then
echo “Kernel and systemd debugging was enabled as part of an errant script during the yum update”
echo “See https://bugs.CentOS.org/view.php?id425 and https://wiki.CentOS.org/HowTos/Grub2”
fi
~ Brian Mathis
@orev
Once upon a time, Brian Mathis said:
Assuming your GRUB entries are in the usual order (newest kernel first), you can do:
grub2-set-default “$(grep ‘^menuentry’ /boot/grub2/grub.cfg | grep -v debug | head -n 1 | cut -d\’ -f2)”
and then reboot.
Chris Adams wrote:
Thanks to both of you – that’s the issue.
mark