http://bugzilla.opensuse.org/show_bug.cgi?id=860778 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tonyj@suse.com) | --- Comment #26 from Felix Miata --- (In reply to Tony Jones from comment #25)

This isn't an audit bug, I've not no idea how his system got into this state and what is changing his

I don't know either, but remind that I don't have "system", I have numerous systems, many of which were doing this until I found out I could stop the problem by installing audit or rsyslog. Also, these installations were all begun either direct TW minimal X installations, or upgrades from what were originally minimal X installations that were zypper dup'd from 13.2, which may originally have been 13.1 minimal X installations dup'd to 13.2. Anything that caused these messages to begin showing up only in TW surely must have been caused by some kind of change in some part of one or more of the underlying subsystems. (In reply to Tony Jones from comment #24)

I suspect this is because I'm booting with cmdline option "quiet" and you are not.

I haven't had quiet in any bootloader stanza for any distro since sometime last century. I find little to no activity on vtty1 during init to be highly annoying. Not having quiet on cmdline has never been a problem before that I can remember.

If this is correct, as root, add "quiet" (or "loglevel=4") to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run grub2-mkconfig > /boot/grub2/grub.cfg [or yast equivalent] and reboot.

Grub2 is not installed in any rpm-based distro here. Most installations here are booting from a Grub Legacy installation on a primary partition that is never mounted as /boot.

Or install and enable rsyslog, or install and enable audit.

Those would seem to be workarounds, not cures for whatever it is we don't seem to have yet identified. I was having what was probably the same problem in my Fedora installations, but I think they all went away eventually via updates. That seems to be the case here now. As I'm running low on installations left that haven't either had audit installed, or do not exhibit the problem. The three I updated in recent hours (kt400, kt88b & t2240), which had last been dup'd 5-8 weeks ago, had neither audit installed nor the problem. All three just updated do have rsyslog-8.9.0-3.1 installed. T2240 has 7.4.3-1.3 first grep rsyslog return from /var/log/zypp/history, kt88b 7.4.7-1.1, kt400 7.4.4-2.1.2. This leads me to think more recent installs have had rsyslog installed as part of a minimal X, while later installs may not be including it. In contrast, host g5eas last updated a week ago, and originally installed 53 weeks ago does have this problem, and has neither audit nor rsyslog installed. I started to install rsyslog on it, but zypper wants to remove systemd-logger to permit it. Host big last updated a week ago, and originally installed 21 months ago does not have this problem, has rsyslog 8.9.0-3.1 installed now, and originally had 7.4.2-1.1 installed 21 months ago. Host gx270 last updated 3 weeks ago, and originally installed 58 weeks ago did have this problem, and had neither audit nor rsyslog installed. I started to install rsyslog on it, zypper wanted to remove systemd-logger to permit it, and I let it proceed. Problem gone on reboot. I'll have to check rsyslog history on newer original installs to try to affirm this likelihood if you wish. -- You are receiving this mail because: You are on the CC list for the bug.