[CentOS] CentOS 7, systemd,, and message floods

[Brian Mathis]

On Wed, Apr 5, 2017 at 3:18 PM, <m.roth at 5-cent.us> wrote:

> 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
> cookie=436 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
>


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?id=12425 and
https://wiki.centos.org/HowTos/Grub2"
fi


~ Brian Mathis
@orev