RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1398811 - 219-30.el7_3.6.x86_64 and previous build flooding logs
Summary: 219-30.el7_3.6.x86_64 and previous build flooding logs
Keywords:
Status: CLOSED DUPLICATE of bug 1285601
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: grubby
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: rmarshall
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-26 10:32 UTC by Harald Reindl
Modified: 2017-03-07 20:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-07 20:02:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Harald Reindl 2016-11-26 10:32:02 UTC
the two blocks below are only a small piece of what goes on at boot and the second block seems to happen later too - dmesg over ssh is not funny when you get flooeded with megabytes of text bascially saying all the time the same

[    3.502442] systemd-udevd[330]: passed unknown number of bytes to netlink monitor 0x7f92ec36f120
[    3.502458] systemd-udevd[330]: seq 1955 processed with 0
[    3.502460] systemd-udevd[300]: seq 1971 queued, 'add' 'tty'
[    3.502467] systemd-udevd[300]: maximum number (16) of children reached
[    3.502474] systemd-udevd[300]: maximum number (16) of children reached
[    3.502480] systemd-udevd[300]: maximum number (16) of children reached
[    3.502486] systemd-udevd[300]: maximum number (16) of children reached
[    3.502492] systemd-udevd[300]: maximum number (16) of children reached
[    3.502497] systemd-udevd[300]: maximum number (16) of children reached
[    3.502503] systemd-udevd[300]: maximum number (16) of children reached
[    3.502509] systemd-udevd[300]: maximum number (16) of children reached
[    3.502514] systemd-udevd[300]: maximum number (16) of children reached
[    3.502520] systemd-udevd[300]: maximum number (16) of children reached
[    3.502526] systemd-udevd[300]: maximum number (16) of children reached
[    3.502532] systemd-udevd[300]: maximum number (16) of children reached
[    3.502538] systemd-udevd[300]: maximum number (16) of children reached
[    3.502544] systemd-udevd[300]: maximum number (16) of children reached
[    3.502550] systemd-udevd[300]: maximum number (16) of children reached

[  399.224567] systemd-logind[389]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=SessionNew cookie=14 reply_cookie=0 error=n/a
[  399.224663] systemd-logind[389]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/login1/user/_0 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=15 reply_cookie=0 error=n/a
[  399.224721] systemd-logind[389]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/dev_2dsda1_2edevice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=158 reply_cookie=0 error=n/a
[  399.224770] systemd-logind[389]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/dev_2dsda1_2edevice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=159 reply_cookie=0 error=n/a
[  399.224813] systemd-logind[389]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/dev_2dsda3_2edevice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=160 reply_cookie=0 error=n/a
[  399.224856] systemd-logind[389]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/dev_2dsda3_2edevice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=161 reply_cookie=0 error=n/a
[  399.224899] systemd-logind[389]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=168 reply_cookie=0 error=n/a
[  399.225080] systemd-logind[389]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/user_2d0_2eslice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=170 reply_cookie=0 error=n/a
[  399.225364] systemd[1]: session-1.scope changed dead -> running
[  399.225383] systemd[1]: Job session-1.scope/start finished, result=done
[  399.225408] systemd[1]: Started Session 1 of user root.
[  399.225517] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=177 reply_cookie=0 error=n/a
[  399.225564] systemd[1]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=RemoveMatch cookie=178 reply_cookie=0 error=n/a
[  399.225678] systemd-logind[389]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=177 reply_cookie=0 error=n/a
[  399.225902] systemd-logind[389]: Sending reply about created session: id=1 object_path=/org/freedesktop/login1/session/_31 uid=0 runtime_path=/run/user/0 session_fd=19 seat= vtnr=0
[  399.225959] systemd-logind[389]: Sent message type=method_return sender=n/a destination=:1.3 object=n/a interface=n/a member=n/a cookie=16 reply_cookie=2 error=n/a
[  399.226601] systemd[1]: Starting Session 1 of user root.
[  399.226782] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/session_2d1_2escope interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=179 reply_cookie=0 error=n/a
[  399.226898] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/session_2d1_2escope interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=180 reply_cookie=0 error=n/a
[  399.226964] systemd[1]: Got message type=signal sender=org.freedesktop.DBus destination=n/a object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameOwnerChanged cookie=9 reply_cookie=0 error=n/a
[  399.227007] systemd-logind[389]: Got message type=signal sender=org.freedesktop.DBus destination=n/a object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameOwnerChanged cookie=9 reply_cookie=0 error=n/a
[  399.227097] systemd-logind[389]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/session_2d1_2escope interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=179 reply_cookie=0 error=n/a
[  399.227155] systemd-logind[389]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/session_2d1_2escope interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=180 reply_cookie=0 error=n/a

Comment 1 Harald Reindl 2016-11-26 10:34:19 UTC
[  505.769878] systemd[1]: Got notification message for unit systemd-journald.service
[  505.769899] systemd[1]: systemd-journald.service: Got notification message from PID 269 (WATCHDOG=1)
[  505.769912] systemd[1]: systemd-journald.service: got WATCHDOG=1
[  505.770040] systemd[1]: Got notification message for unit systemd-logind.service
[  505.770055] systemd[1]: systemd-logind.service: Got notification message from PID 389 (WATCHDOG=1)
[  505.770067] systemd[1]: systemd-logind.service: got WATCHDOG=1
[  604.675879] systemd[1]: Got notification message for unit systemd-journald.service
[  604.675900] systemd[1]: systemd-journald.service: Got notification message from PID 269 (WATCHDOG=1)
[  604.675914] systemd[1]: systemd-journald.service: got WATCHDOG=1


[  618.845533] systemd[1]: Got notification message for unit systemd-logind.service
[  618.845549] systemd[1]: systemd-logind.service: Got notification message from PID 389 (WATCHDOG=1)
[  618.845563] systemd[1]: systemd-logind.service: got WATCHDOG=1


[  618.846744] systemd[1]: Failed to load configuration for session-2.scope: No such file or directory
[  618.848337] systemd[1]: Trying to enqueue job session-2.scope/start/fail
[  618.848399] systemd[1]: Installed new job session-2.scope/start as 228
[  618.848431] systemd[1]: Enqueued job session-2.scope/start as 228

[  618.850644] systemd[1]: session-2.scope changed dead -> running
[  618.850665] systemd[1]: Job session-2.scope/start finished, result=done
[  618.850692] systemd[1]: Started Session 2 of user root.

[  618.996714] systemd[1]: session-2.scope: cgroup is empty
[  618.996730] systemd[1]: session-2.scope changed running -> dead
[  618.997019] systemd[1]: Sent message type=method_return sender=n/a destination=:1.1 object=n/a interface=n/a member=n/a cookie=193 reply_cookie=24 error=n/a
[  618.997045] systemd[1]: Collecting session-2.scope


[  736.134152] systemd[1]: Got notification message for unit systemd-journald.service
[  736.134171] systemd[1]: systemd-journald.service: Got notification message from PID 269 (WATCHDOG=1)
[  736.134184] systemd[1]: systemd-journald.service: got WATCHDOG=1

Comment 2 Harald Reindl 2016-11-26 10:41:54 UTC
any since when spits systemd-tmpfiles dmesg full?

[  926.444419] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/etc.conf".
[  926.444539] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/initscripts.conf".
[  926.444643] systemd-tmpfiles[988]: Reading config file "/run/tmpfiles.d/kmod.conf".
[  926.444686] systemd-tmpfiles[988]: Ignoring entry c! "/dev/fuse" because --boot is not specified.
[  926.444708] systemd-tmpfiles[988]: Ignoring entry c! "/dev/btrfs-control" because --boot is not specified.
[  926.444727] systemd-tmpfiles[988]: Ignoring entry c! "/dev/loop-control" because --boot is not specified.
[  926.444760] systemd-tmpfiles[988]: Ignoring entry c! "/dev/net/tun" because --boot is not specified.
[  926.444780] systemd-tmpfiles[988]: Ignoring entry c! "/dev/ppp" because --boot is not specified.
[  926.444799] systemd-tmpfiles[988]: Ignoring entry c! "/dev/uinput" because --boot is not specified.
[  926.444833] systemd-tmpfiles[988]: Ignoring entry c! "/dev/mapper/control" because --boot is not specified.
[  926.444853] systemd-tmpfiles[988]: Ignoring entry c! "/dev/uhid" because --boot is not specified.
[  926.444884] systemd-tmpfiles[988]: Ignoring entry c! "/dev/vfio/vfio" because --boot is not specified.
[  926.444905] systemd-tmpfiles[988]: Ignoring entry c! "/dev/vhci" because --boot is not specified.
[  926.444928] systemd-tmpfiles[988]: Ignoring entry c! "/dev/vhost-net" because --boot is not specified.
[  926.445019] systemd-tmpfiles[988]: Ignoring entry c! "/dev/snd/timer" because --boot is not specified.
[  926.445061] systemd-tmpfiles[988]: Ignoring entry c! "/dev/snd/seq" because --boot is not specified.
[  926.445109] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/legacy.conf".
[  926.445732] systemd-tmpfiles[988]: Ignoring entry r! "/forcefsck" because --boot is not specified.
[  926.445755] systemd-tmpfiles[988]: Ignoring entry r! "/fastboot" because --boot is not specified.
[  926.445774] systemd-tmpfiles[988]: Ignoring entry r! "/forcequotacheck" because --boot is not specified.
[  926.445820] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/libselinux.conf".
[  926.445900] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/openvpn.conf".
[  926.446104] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/pam.conf".
[  926.446205] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/python.conf".
[  926.446281] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/rpm.conf".
[  926.446355] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/sap.conf".
[  926.446443] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/screen.conf".
[  926.446608] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/systemd-nologin.conf".
[  926.446654] systemd-tmpfiles[988]: Ignoring entry F! "/run/nologin" because --boot is not specified.
[  926.446704] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/systemd.conf".
[  926.446762] systemd-tmpfiles[988]: Ignoring entry F! "/run/utmp" because --boot is not specified.
[  926.448471] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/tmp.conf".
[  926.448678] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/var.conf".
[  926.448947] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/vnstat.conf".
[  926.449120] systemd-tmpfiles[988]: Reading config file "/usr/lib/tmpfiles.d/x11.conf".
[  926.449216] systemd-tmpfiles[988]: Ignoring entry r! "/tmp/.X[0-9]*-lock" because --boot is not specified.
[  926.449261] systemd-tmpfiles[988]: Running clean action for entry d /run/lock
[  926.449274] systemd-tmpfiles[988]: Running clean action for entry d /run/lock/subsys
[  926.449288] systemd-tmpfiles[988]: Running clean action for entry d /var
[  926.449298] systemd-tmpfiles[988]: Running clean action for entry L /var/run
[  926.449308] systemd-tmpfiles[988]: Running clean action for entry d /var/run/netreport
[  926.449320] systemd-tmpfiles[988]: Running clean action for entry L /etc/os-release
[  926.449332] systemd-tmpfiles[988]: Running clean action for entry d /var/run/faillock
[  926.449344] systemd-tmpfiles[988]: Running clean action for entry d /run/systemd/machines
[  926.449356] systemd-tmpfiles[988]: Running clean action for entry d /run/systemd/shutdown
[  926.449368] systemd-tmpfiles[988]: Running clean action for entry d /run/systemd/netif
[  926.449380] systemd-tmpfiles[988]: Running clean action for entry d /run/systemd/sessions
[  926.449391] systemd-tmpfiles[988]: Running clean action for entry d /var/lib
[  926.449402] systemd-tmpfiles[988]: Running clean action for entry v /tmp
[  926.449544] systemd-tmpfiles[988]: Cleanup threshold for mount point "/tmp" is Wed 2016-11-16 11:35:08.836024 CET
[  926.449639] systemd-tmpfiles[988]: Ignoring "/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-openvpn.service-SqZobx": a separate glob exists.
[  926.449666] systemd-tmpfiles[988]: Ignoring "/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-dnsmasq.service-cgEHFP": a separate glob exists.
[  926.449691] systemd-tmpfiles[988]: Ignoring "/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-dhcpd.service-6NAMa8": a separate glob exists.
[  926.449715] systemd-tmpfiles[988]: Ignoring "/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-ntpd.service-izJLGq": a separate glob exists.
[  926.449740] systemd-tmpfiles[988]: Ignoring "/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-postfix.service-CM40lM": a separate glob exists.
[  926.449765] systemd-tmpfiles[988]: Ignoring "/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-vnstat.service-8RuVkb": a separate glob exists.
[  926.449789] systemd-tmpfiles[988]: Ignoring "/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-haveged.service-yEsVvA": a separate glob exists.
[  926.449810] systemd-tmpfiles[988]: Ignoring "/tmp/.Test-unix": a separate entry exists.
[  926.449830] systemd-tmpfiles[988]: Ignoring "/tmp/.X11-unix": a separate entry exists.
[  926.449849] systemd-tmpfiles[988]: Ignoring "/tmp/.XIM-unix": a separate entry exists.
[  926.449869] systemd-tmpfiles[988]: Ignoring "/tmp/.font-unix": a separate entry exists.
[  926.449888] systemd-tmpfiles[988]: Ignoring "/tmp/.ICE-unix": a separate entry exists.
[  926.449907] systemd-tmpfiles[988]: Running clean action for entry d /tmp/.font-unix
[  926.449943] systemd-tmpfiles[988]: Cleanup threshold for directory "/tmp/.font-unix" is Wed 2016-11-16 11:35:08.836525 CET
[  926.449965] systemd-tmpfiles[988]: Running clean action for entry d /run/log
[  926.449978] systemd-tmpfiles[988]: Running clean action for entry d /run/user
[  926.449991] systemd-tmpfiles[988]: Running clean action for entry d /run/lock/lockdev
[  926.450004] systemd-tmpfiles[988]: Running clean action for entry d /var/lib/systemd
[  926.450015] systemd-tmpfiles[988]: Running clean action for entry d /var/lib/systemd/coredump
[  926.450048] systemd-tmpfiles[988]: Cleanup threshold for directory "/var/lib/systemd/coredump" is Wed 2016-11-23 11:35:08.836632 CET
[  926.459677] systemd-tmpfiles[988]: Running clean action for entry v /var/lib/machines
[  926.459698] systemd-tmpfiles[988]: Running clean action for entry d /run/systemd/netif/leases
[  926.459713] systemd-tmpfiles[988]: Running clean action for entry d /var/cache
[  926.459728] systemd-tmpfiles[988]: Running clean action for entry d /run/systemd/seats
[  926.459742] systemd-tmpfiles[988]: Running clean action for entry d /tmp/.XIM-unix
[  926.459790] systemd-tmpfiles[988]: Cleanup threshold for directory "/tmp/.XIM-unix" is Wed 2016-11-16 11:35:08.846345 CET
[  926.459818] systemd-tmpfiles[988]: Running clean action for entry d /run/systemd/netif/links
[  926.459834] systemd-tmpfiles[988]: Running clean action for entry d /var/spool
[  926.459849] systemd-tmpfiles[988]: Running clean action for entry d /var/run/console
[  926.459863] systemd-tmpfiles[988]: Running clean action for entry d /run/systemd/users
[  926.459877] systemd-tmpfiles[988]: Running clean action for entry v /var/tmp
[  926.459916] systemd-tmpfiles[988]: Cleanup threshold for mount point "/var/tmp" is Thu 2016-10-27 12:35:08.846479 CEST
[  926.459962] systemd-tmpfiles[988]: Ignoring "/var/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-openvpn.service-9kKqWn": a separate glob exists.
[  926.459992] systemd-tmpfiles[988]: Ignoring "/var/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-dnsmasq.service-BqnnqG": a separate glob exists.
[  926.460021] systemd-tmpfiles[988]: Ignoring "/var/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-dhcpd.service-Zt41UY": a separate glob exists.
[  926.460049] systemd-tmpfiles[988]: Ignoring "/var/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-ntpd.service-lmgxqh": a separate glob exists.
[  926.460077] systemd-tmpfiles[988]: Ignoring "/var/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-postfix.service-t3l0Wz": a separate glob exists.
[  926.460105] systemd-tmpfiles[988]: Ignoring "/var/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-vnstat.service-JKV1KY": a separate glob exists.
[  926.460133] systemd-tmpfiles[988]: Ignoring "/var/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-haveged.service-vWePUn": a separate glob exists.
[  926.460158] systemd-tmpfiles[988]: Running clean action for entry d /var/run/setrans
[  926.460173] systemd-tmpfiles[988]: Running clean action for entry L /var/lock
[  926.460188] systemd-tmpfiles[988]: Running clean action for entry d /run/systemd/ask-password
[  926.460203] systemd-tmpfiles[988]: Running clean action for entry d /var/log
[  926.460216] systemd-tmpfiles[988]: Running clean action for entry f /var/log/wtmp
[  926.460230] systemd-tmpfiles[988]: Running clean action for entry f /var/log/btmp
[  926.460243] systemd-tmpfiles[988]: Running clean action for entry L /etc/localtime
[  926.460258] systemd-tmpfiles[988]: Running clean action for entry D /var/run/openvpn
[  926.460271] systemd-tmpfiles[988]: Running clean action for entry d /dev/net
[  926.460284] systemd-tmpfiles[988]: Running clean action for entry d /tmp/.Test-unix
[  926.460324] systemd-tmpfiles[988]: Cleanup threshold for directory "/tmp/.Test-unix" is Wed 2016-11-16 11:35:08.846886 CET
[  926.460351] systemd-tmpfiles[988]: Running clean action for entry d /var/run/screen
[  926.460367] systemd-tmpfiles[988]: Running clean action for entry d /dev/vfio
[  926.460381] systemd-tmpfiles[988]: Running clean action for entry d /var/run/sepermit
[  926.460395] systemd-tmpfiles[988]: Running clean action for entry d /tmp/.ICE-unix
[  926.460433] systemd-tmpfiles[988]: Cleanup threshold for directory "/tmp/.ICE-unix" is Wed 2016-11-16 11:35:08.846996 CET
[  926.460459] systemd-tmpfiles[988]: Running clean action for entry D /run/vnstat
[  926.460474] systemd-tmpfiles[988]: Running clean action for entry d /dev/snd
[  926.460487] systemd-tmpfiles[988]: Running clean action for entry d /dev/snd
[  926.460501] systemd-tmpfiles[988]: Running clean action for entry d /dev/mapper
[  926.460514] systemd-tmpfiles[988]: Running clean action for entry d /tmp/.X11-unix
[  926.460552] systemd-tmpfiles[988]: Cleanup threshold for directory "/tmp/.X11-unix" is Wed 2016-11-16 11:35:08.847115 CET
[  926.460580] systemd-tmpfiles[988]: Running clean action for entry x /var/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-*
[  926.460622] systemd-tmpfiles[988]: Running clean action for entry x /tmp/.hdb*lock
[  926.460638] systemd-tmpfiles[988]: Running clean action for entry x /tmp/.sap*
[  926.460653] systemd-tmpfiles[988]: Running clean action for entry x /tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-*
[  926.460668] systemd-tmpfiles[988]: Running clean action for entry z /var/log/journal
[  926.460686] systemd-tmpfiles[988]: Running clean action for entry X /tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-*/tmp
[  926.460805] systemd-tmpfiles[988]: Running clean action for entry A /var/log/journal/e73eadc6125544ef8715e973711ee8e3
[  926.460823] systemd-tmpfiles[988]: Running clean action for entry a /var/log/journal/e73eadc6125544ef8715e973711ee8e3
[  926.460838] systemd-tmpfiles[988]: Running clean action for entry z /var/log/journal/e73eadc6125544ef8715e973711ee8e3
[  926.460853] systemd-tmpfiles[988]: Running clean action for entry z /run/log/journal
[  926.460869] systemd-tmpfiles[988]: Running clean action for entry A /run/log/journal/e73eadc6125544ef8715e973711ee8e3
[  926.460883] systemd-tmpfiles[988]: Running clean action for entry Z /run/log/journal/e73eadc6125544ef8715e973711ee8e3
[  926.460898] systemd-tmpfiles[988]: Running clean action for entry a /run/log/journal/e73eadc6125544ef8715e973711ee8e3
[  926.460911] systemd-tmpfiles[988]: Running clean action for entry x /tmp/pymp-*
[  926.460927] systemd-tmpfiles[988]: Running clean action for entry X /var/tmp/systemd-private-0d9a31d0430043ec858cca8fbda50de2-*/tmp
[  926.461023] systemd-tmpfiles[988]: Running clean action for entry r /var/lib/rpm/__db.*
[  926.461668] systemd[1]: Received SIGCHLD from PID 988 (systemd-tmpfile).
[  926.461752] systemd[1]: Child 988 (systemd-tmpfile) died (code=exited, status=0/SUCCESS)
[  926.461859] systemd[1]: Child 988 belongs to systemd-tmpfiles-clean.service
[  926.461886] systemd[1]: systemd-tmpfiles-clean.service: main process exited, code=exited, status=0/SUCCESS
[  926.462782] systemd[1]: systemd-tmpfiles-clean.service changed start -> dead
[  926.463079] systemd[1]: Job systemd-tmpfiles-clean.service/start finished, result=done
[  926.463114] systemd[1]: Started Cleanup of Temporary Directories.
[  926.463241] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=208 reply_cookie=0 error=n/a
[  926.463270] systemd[1]: systemd-tmpfiles-clean.timer got notified about unit deactivation.
[  926.463293] systemd[1]: systemd-tmpfiles-clean.timer: Monotonic timer elapses in 23h 59min 59.976191s.
[  926.463308] systemd[1]: systemd-tmpfiles-clean.timer changed running -> waiting
[  926.463394] systemd[1]: systemd-tmpfiles-clean.timer: Monotonic timer elapses in 23h 59min 59.976089s.
[  926.463418] systemd[1]: systemd-tmpfiles-clean.service: cgroup is empty

Comment 4 Michal Sekletar 2016-11-28 09:59:23 UTC
systemd's logging infrastructure is setup in a way that logs usually end up in a journald, even when system is still running from initramfs. Usually we start udev first and then journald and since then no logs should end up in /dev/kmsg. Hence those log lines in dmesg output from  5 min after power-on indicate that something is not quite right. Is journald running fine on the server? 

Also, to reduce the log verbosity please disable debug logging. Seems like you have it enabled for both udev and systemd.

In the meantime you can use dmesg -k to inspect only log messages originating from kernel.

Comment 5 Harald Reindl 2016-11-28 10:03:30 UTC
that happens all the time (periodly) not just shortly after boot the point is that nobody has enabled debug logging and that bevior started with the CR updates from CentOS which will end in CentOS 7.3

i even commented "LogLevel=info" which should be the default anyways

cat /etc/systemd/system.conf | grep Log
LogLevel=info
#LogTarget=journal-or-kmsg
#LogColor=yes
#LogLocation=no

at the moment i did just a "dmesg -c" to get rid of the megabytes crap from last nigth, will have a look at "dmesg -k" later since i guess it takes not too long to alert out again

Comment 6 Harald Reindl 2016-11-28 10:05:59 UTC
[root@localhost:~]$ dmesg
[172081.148551] systemd[1]: Got notification message for unit systemd-logind.service
[172081.148571] systemd[1]: systemd-logind.service: Got notification message from PID 389 (WATCHDOG=1)
[172081.148585] systemd[1]: systemd-logind.service: got WATCHDOG=1
[172081.148714] systemd[1]: Got notification message for unit systemd-journald.service
[172081.148729] systemd[1]: systemd-journald.service: Got notification message from PID 269 (WATCHDOG=1)
[172081.148741] systemd[1]: systemd-journald.service: got WATCHDOG=1

[root@localhost:~]$ dmesg -k

[root@localhost:~]$ systemctl status systemd-journald.service
? systemd-journald.service - Journal Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static; vendor preset: disabled)
   Active: active (running) since Sam 2016-11-26 11:19:47 CET; 1 day 23h ago
     Docs: man:systemd-journald.service(8)
           man:journald.conf(5)
 Main PID: 269 (systemd-journal)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-journald.service
           ??269 /usr/lib/systemd/systemd-journald

Comment 7 Harald Reindl 2016-11-29 10:08:24 UTC
it's only systemd stuff in dmesg

[root@localhost:~]$ dmesg -k
[root@localhost:~]$ dmesg | wc -l
6761

why in the world while syslog is silent?
what makes systemd believe someone told him to log debug informations?

Comment 8 Harald Reindl 2016-12-15 02:07:59 UTC
what drives me really crazy here is that we have 4 CentOS7 machines, all the same patchlevel

* 1 webserver for 3rd party stuff like Magento (VM)
* 1 clone of it for testing and mariadb.replication
* 1 NFS server
* 1 micro PC acting as router/vpn-gateway

today i also upgraded the NFS-server to 7.3 and it's also fine
the only machine which thinks it need to spit out debug logging all day long is the micropc :-(

Comment 9 Harald Reindl 2017-01-01 02:33:49 UTC
the main question is what idiot piece of software added "systemd.log_level=debug systemd.log_target=kmsg" to the kernel line at /boot/grub2/grub.cfg while this does not and did never exist in /etc/default/grub and why "grub2-mkconfig" insists in generate that pure bullshit

"cat /etc/default/grub | grep -i debug" don't show anything



cat /boot/grub2/grub.cfg | grep debug
        linux16 /vmlinuz-3.10.0-514.2.2.el7.x86_64 root=UUID=381a9b06-ad0a-4191-a669-afc1fc477cdb ro audit=0 rd.plymouth=0 plymouth.enable=0 net.ifnames=0 biosdevname=0 nodmraid raid=noautodetect nomodeset selinux=0 clocksource=hpet elevator=noop divider=20 noresume nmi_watchdog=0 pcie_aspm=off acpi_osi=Linux consoleblank=0 rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 vconsole.font=latarcyrheb-sun16 vconsole.keymap=de-latin1-nodeadkeys locale.LANG=de_DE.UTF-8 LANG=de_AT.UTF-8 systemd.log_level=debug systemd.log_target=kmsg
menuentry 'CentOS Linux (3.10.0-514.2.2.el7.x86_64) 7 (Core) with debugging' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-327.4.4.el7.x86_64-advanced-381a9b06-ad0a-4191-a669-afc1fc477cdb' {
        linux16 /vmlinuz-3.10.0-514.2.2.el7.x86_64 root=UUID=381a9b06-ad0a-4191-a669-afc1fc477cdb ro audit=0 rd.plymouth=0 plymouth.enable=0 net.ifnames=0 biosdevname=0 nodmraid raid=noautodetect nomodeset selinux=0 clocksource=hpet elevator=noop divider=20 noresume nmi_watchdog=0 pcie_aspm=off acpi_osi=Linux consoleblank=0 rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 vconsole.font=latarcyrheb-sun16 vconsole.keymap=de-latin1-nodeadkeys locale.LANG=de_DE.UTF-8 LANG=de_AT.UTF-8 systemd.log_level=debug systemd.log_target=kmsg
menuentry 'CentOS Linux (3.10.0-514.el7.x86_64) 7 (Core) with debugging' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-327.4.4.el7.x86_64-advanced-381a9b06-ad0a-4191-a669-afc1fc477cdb' {
        linux16 /vmlinuz-3.10.0-514.el7.x86_64 root=UUID=381a9b06-ad0a-4191-a669-afc1fc477cdb ro audit=0 rd.plymouth=0 plymouth.enable=0 net.ifnames=0 biosdevname=0 nodmraid raid=noautodetect nomodeset selinux=0 clocksource=hpet elevator=noop divider=20 noresume nmi_watchdog=0 pcie_aspm=off acpi_osi=Linux consoleblank=0 rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 vconsole.font=latarcyrheb-sun16 vconsole.keymap=de-latin1-nodeadkeys locale.LANG=de_DE.UTF-8 LANG=de_AT.UTF-8 systemd.log_level=debug systemd.log_target=kmsg

Comment 10 Harald Reindl 2017-01-01 02:40:24 UTC Comment hidden (abuse)
Comment 11 Harald Reindl 2017-01-21 04:04:46 UTC Comment hidden (abuse)
Comment 12 Harald Reindl 2017-01-21 04:09:27 UTC
https://www.centos.org/forums/viewtopic.php?t=61030
fix whatever did set "MAKEDEBUG=yes" in /etc/sysconfig/kernel unasked

Comment 13 rmarshall 2017-03-07 20:02:36 UTC
I have submitted fixes for this issue to 7.1, 7.2, 7.3, and 7.4 versions of Red Hat Enterprise Linux.

This fix will flow into CentOS from the 7.3 zstream which is being tracked in bugzilla #1420749.

*** This bug has been marked as a duplicate of bug 1285601 ***


Note You need to log in before you can comment on or make changes to this bug.