[opensuse] kernel dmesg output on virtual terminals
Hi list, on our server, the dmesg kernel output is printed to all virtual terminals. The machine is Leap 42.3 (just dup-ed from 42.2). The problem already existed with 42.2, and ISTR that it started when I removed plymouth from the system (it's a server, most of the time even without connected monitor). Could that be the case? And what to do against it? I know here's more people around with disabled plymouth. Do you also suffer this issue? Any suggestions what to look for? Google mostly points me to 10-year old 'solutions' involving syslog.conf :( -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Peter Suetterlin composed on 2018-02-20 17:58 (UTC+0100):
on our server, the dmesg kernel output is printed to all virtual terminals.
The machine is Leap 42.3 (just dup-ed from 42.2). The problem already existed with 42.2, and ISTR that it started when I removed plymouth from the system (it's a server, most of the time even without connected monitor).
Could that be the case? And what to do against it? I know here's more people around with disabled plymouth. Do you also suffer this issue? Any suggestions what to look for?
Google mostly points me to 10-year old 'solutions' involving syslog.conf :(
This sounds like the reason why I have kernel.printk = 3 4 1 3 in /etc/sysctl.d/local.conf -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
Peter Suetterlin composed on 2018-02-20 17:58 (UTC+0100):
on our server, the dmesg kernel output is printed to all virtual terminals.
This sounds like the reason why I have
kernel.printk = 3 4 1 3
in /etc/sysctl.d/local.conf
Ah, indeed. Before the dmesg -D, this had been 4 4 1 7 and now it is 1 4 1 7 So your solution still puts important warings on the conoles, correct? Guess I'll follow your road then! (BUT - it still doesn't explain why with the 4 4 1 7 setting I don't see them on my laptop here. Something's eating them....) Thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Peter Suetterlin wrote:
Felix Miata wrote:
Peter Suetterlin composed on 2018-02-20 17:58 (UTC+0100):
on our server, the dmesg kernel output is printed to all virtual terminals.
This sounds like the reason why I have
kernel.printk = 3 4 1 3
in /etc/sysctl.d/local.conf
Ah, indeed. Before the dmesg -D, this had been 4 4 1 7 and now it is 1 4 1 7
On xen guests leap423 - 7 4 1 7 On xen guests leap150 - 7 4 1 7 on laptop leap422 - 7 4 1 7 on desktop leap423 - 7 4 1 7 on desktop leap150 - 7 4 1 7 on desktop 13.1 - 7417 on desktop 10.3 - 1417 on xen server 13.2 - 7417 on laptop 12.3 1 4 1 7 TMK, I have never dabbled with that setting or dmesg -D. -- Per Jessen, Zürich (0.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
20.02.2018 21:02, Per Jessen пишет:
Peter Suetterlin wrote:
Felix Miata wrote:
Peter Suetterlin composed on 2018-02-20 17:58 (UTC+0100):
on our server, the dmesg kernel output is printed to all virtual terminals.
This sounds like the reason why I have
kernel.printk = 3 4 1 3
in /etc/sysctl.d/local.conf
Ah, indeed. Before the dmesg -D, this had been 4 4 1 7 and now it is 1 4 1 7
On xen guests leap423 - 7 4 1 7 On xen guests leap150 - 7 4 1 7 on laptop leap422 - 7 4 1 7 on desktop leap423 - 7 4 1 7 on desktop leap150 - 7 4 1 7 on desktop 13.1 - 7417 on desktop 10.3 - 1417 on xen server 13.2 - 7417 on laptop 12.3 1 4 1 7
TMK, I have never dabbled with that setting or dmesg -D.
The first '7' comes from the last '7' which is default unless explicitly overridden. '4' is default when "quiet" is used and should suppress most messages. '1' may come from sysvinit scripts (I definitely remember that one effect of switching to systemd was much more noise on ttys). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
20.02.2018 21:02, Per Jessen пишет:
On xen guests leap423 - 7 4 1 7 On xen guests leap150 - 7 4 1 7 on laptop leap422 - 7 4 1 7 on desktop leap423 - 7 4 1 7 on desktop leap150 - 7 4 1 7 on desktop 13.1 - 7417 on desktop 10.3 - 1417 on xen server 13.2 - 7417 on laptop 12.3 1 4 1 7
TMK, I have never dabbled with that setting or dmesg -D.
The first '7' comes from the last '7' which is default unless explicitly overridden. '4' is default when "quiet" is used
Aah! Another puzzle piece.
and should suppress most messages.
Second number is the setting for messages that don't specify a level. So IMHO makes sense to have the first one lower than the second...
'1' may come from sysvinit scripts (I definitely remember that one effect of switching to systemd was much more noise on ttys).
It's said to be the lowest allowed value. I.e., mode-0 messages will always show up on console, even with dmesg -D -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
20.02.2018 21:26, Peter Suetterlin пишет:
Andrei Borzenkov wrote:
20.02.2018 21:02, Per Jessen пишет:
On xen guests leap423 - 7 4 1 7 On xen guests leap150 - 7 4 1 7 on laptop leap422 - 7 4 1 7 on desktop leap423 - 7 4 1 7 on desktop leap150 - 7 4 1 7 on desktop 13.1 - 7417 on desktop 10.3 - 1417 on xen server 13.2 - 7417 on laptop 12.3 1 4 1 7
TMK, I have never dabbled with that setting or dmesg -D.
The first '7' comes from the last '7' which is default unless explicitly overridden. '4' is default when "quiet" is used
Aah! Another puzzle piece.
and should suppress most messages.
Second number is the setting for messages that don't specify a level. So IMHO makes sense to have the first one lower than the second...
All levels numerically greater or equal to console_loglevel are suppressed. With console_loglevel 4 printed are 3 and lower.
It's said to be the lowest allowed value. I.e., mode-0 messages will always show up on console, even with dmesg -D
If your system needs to print emergency messages you better see them ... you may not have any chance to capture them otherwise. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Peter Suetterlin wrote:
Hi list,
on our server, the dmesg kernel output is printed to all virtual terminals.
....
Google mostly points me to 10-year old 'solutions' involving syslog.conf :(
OK, writing this mail obviously helped looking for the right strings. I found how to turm it off: dmesg -D but why is it on? At least I don't have this output on any of my other machines (Leap 42.2|3, TW)... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Peter Suetterlin <pit@astro.su.se> [02-20-18 12:15]:
Peter Suetterlin wrote:
Hi list,
on our server, the dmesg kernel output is printed to all virtual terminals.
....
Google mostly points me to 10-year old 'solutions' involving syslog.conf :(
OK, writing this mail obviously helped looking for the right strings. I found how to turm it off:
dmesg -D
but why is it on? At least I don't have this output on any of my other machines (Leap 42.2|3, TW)...
but that turns off console output from dmesg to *all* consoles rather than directing to a single console, #10 in my instance. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
OK, writing this mail obviously helped looking for the right strings. I found how to turm it off:
dmesg -D
but why is it on? At least I don't have this output on any of my other machines (Leap 42.2|3, TW)...
but that turns off console output from dmesg to *all* consoles rather than directing to a single console, #10 in my instance.
That is correct. Hmm, in the good-old-days that had been done in syslog.conf, too. No idea how/where today. And on my TW laptop I don't have that feature either. There all consoles are 'empty/silent', w/o me tweaking anything. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-21 21:22, Peter Suetterlin wrote:
Patrick Shanahan wrote:
OK, writing this mail obviously helped looking for the right strings. I found how to turm it off:
dmesg -D
but why is it on? At least I don't have this output on any of my other machines (Leap 42.2|3, TW)...
but that turns off console output from dmesg to *all* consoles rather than directing to a single console, #10 in my instance.
That is correct. Hmm, in the good-old-days that had been done in syslog.conf, too. No idea how/where today. And on my TW laptop I don't have that feature either. There all consoles are 'empty/silent', w/o me tweaking anything.
The command I posted sends all the messages back to tty 10. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-20 a las 17:58 +0100, Peter Suetterlin escribió:
Hi list,
on our server, the dmesg kernel output is printed to all virtual terminals.
The machine is Leap 42.3 (just dup-ed from 42.2). The problem already existed with 42.2, and ISTR that it started when I removed plymouth from the system (it's a server, most of the time even without connected monitor).
Could that be the case? And what to do against it? I know here's more people around with disabled plymouth. Do you also suffer this issue? Any suggestions what to look for?
Google mostly points me to 10-year old 'solutions' involving syslog.conf :(
I can tell you what to do when it happens: klogconsole -r 10 as root. No, I don't know why it happens. I never install plymouth, but it doesn't happen to me currently. In the past, starting vmware trigged it. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlqMWksACgkQja8UbcUWM1wXpAD/cd+eiB58D6miHyp3hYhGYoYq QgMSMI7VutC9ry9xeigA/2a8B4S3KD14HBTSmpoBWKaoYUmL013f+Tcv42x1kCja =GtLn -----END PGP SIGNATURE-----
20.02.2018 19:58, Peter Suetterlin пишет:
Hi list,
on our server, the dmesg kernel output is printed to all virtual terminals.
Not really. It is printed on virtual console which is connected to active vt. So it follows you on virtual terminals.
The machine is Leap 42.3 (just dup-ed from 42.2). The problem already existed with 42.2, and ISTR that it started when I removed plymouth from the system
In other message you said your console level is 4 which means only errors and more severe messages are printed. If you have so many of them you probably should look why. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
20.02.2018 19:58, Peter Suetterlin пишет:
Hi list,
on our server, the dmesg kernel output is printed to all virtual terminals.
Not really. It is printed on virtual console which is connected to active vt. So it follows you on virtual terminals.
Ah, tricky bastard. I need a no-track option :D
The machine is Leap 42.3 (just dup-ed from 42.2). The problem already existed with 42.2, and ISTR that it started when I removed plymouth from the system
In other message you said your console level is 4 which means only errors and more severe messages are printed. If you have so many of them you probably should look why.
I really is everything (AFAIKS) from dmesg, main part is firewall messages. So either they are at that level, or don't have one, and get set to 4 (and will be printed - see my other reply. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
20.02.2018 21:30, Peter Suetterlin пишет:
Andrei Borzenkov wrote:
20.02.2018 19:58, Peter Suetterlin пишет:
Hi list,
on our server, the dmesg kernel output is printed to all virtual terminals.
Not really. It is printed on virtual console which is connected to active vt. So it follows you on virtual terminals.
Ah, tricky bastard. I need a no-track option :D
The machine is Leap 42.3 (just dup-ed from 42.2). The problem already existed with 42.2, and ISTR that it started when I removed plymouth from the system
In other message you said your console level is 4 which means only errors and more severe messages are printed. If you have so many of them you probably should look why.
I really is everything (AFAIKS) from dmesg, main part is firewall messages.
SuSEfirewall configures rules to log at level 4 (see iptables -L output).
So either they are at that level, or don't have one, and get set to 4 (and will be printed - see my other reply.
Messages at level 4 are not printed when console_loglevel is set to 4. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
SuSEfirewall configures rules to log at level 4 (see iptables -L output).
Correct, I see lots of log level warning - assume this is KERN_WARNING
So either they are at that level, or don't have one, and get set to 4 (and will be printed - see my other reply.
Messages at level 4 are not printed when console_loglevel is set to 4.
Obviously a missinterpretation due to my sloppy reading.. But this brings back the initial question: If '4 4 1 7' is not supposed to show those messages - why did I see them nevertheless? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
20.02.2018 22:11, Peter Suetterlin пишет:
Andrei Borzenkov wrote:
SuSEfirewall configures rules to log at level 4 (see iptables -L output).
Correct, I see lots of log level warning - assume this is KERN_WARNING
So either they are at that level, or don't have one, and get set to 4 (and will be printed - see my other reply.
Messages at level 4 are not printed when console_loglevel is set to 4.
Obviously a missinterpretation due to my sloppy reading..
But this brings back the initial question: If '4 4 1 7' is not supposed to show those messages - why did I see them nevertheless?
I do not see them (SFW2 messages) unless I set console_loglevel to 5. This is vanilla 42.3 without any tweaks (also with default kernel command line). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
20.02.2018 22:11, Peter Suetterlin пишет:
But this brings back the initial question: If '4 4 1 7' is not supposed to show those messages - why did I see them nevertheless?
I do not see them (SFW2 messages) unless I set console_loglevel to 5. This is vanilla 42.3 without any tweaks (also with default kernel command line).
I know. Well, I don't have them either on my other machines. To make it even more weird: After having done the 'dmesg -D' before, if I now do a sysctl kernel.printk="4 4 1 7" again, I do *not* see messages on the console anymore. To wrap up, something seemed to be left in a strange state on that computer, and it's probably not worthwhile to dig deeper, as I know now how to correct it.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
Felix Miata -
Patrick Shanahan -
Per Jessen -
Peter Suetterlin