Description of problem: In previous versions of Fedora (and RHEL) rsyslog would display KERN_EMERG messages in all connected terminals. For example, when doing an 'echo L > /proc/sysrq-trigger' a terminal would display Message from syslogd@intel-s3e37-04 at Jan 25 14:18:06 ... kernel:Code: ff ff a8 08 75 25 31 d2 48 8d 86 38 e0 ff ff 48 89 d1 0f 01 c8 0f ae f0 48 8b 86 38 e0 ff ff a8 08 75 08 b1 01 4c 89 e0 0f 01 c9 <e8> ea 69 dd ff 4c 29 e8 48 89 c7 e8 0f bc da ff 49 89 c4 49 89 Message from syslogd@intel-s3e37-04 at Jan 25 14:18:06 ... kernel:Stack: Message from syslogd@intel-s3e37-04 at Jan 25 14:18:06 ... kernel:Call Trace: This appears to have changed at some point. Messages are no longer being output to the individual terminals. The documentation implies that this should happen by default on install as # Everybody gets emergency messages *.emerg * is specified in /etc/rsyslog.conf This *could* be a kernel issue, however, if I specify kern.crit /dev/console in /etc/rsyslog.conf, I do see the messages on the console (but not any of the connected terminals). Version-Release number of selected component (if applicable): rsyslog-5.8.5-1.fc16.x86_64 How reproducible: 100% Steps to Reproduce: 1. Boot 2. ssh into system 3. echo L > /proc/sysrq-trigger Information should be displayed on terminal window as above. Actual results: No information is displayed Expected results: Message from syslogd@intel-s3e37-04 at Jan 25 14:18:06 ... kernel:Code: ff ff a8 08 75 25 31 d2 48 8d 86 38 e0 ff ff 48 89 d1 0f 01 c8 0f ae f0 48 8b 86 38 e0 ff ff a8 08 75 08 b1 01 4c 89 e0 0f 01 c9 <e8> ea 69 dd ff 4c 29 e8 48 89 c7 e8 0f bc da ff 49 89 c4 49 89 Message from syslogd@intel-s3e37-04 at Jan 25 14:18:06 ... kernel:Stack: Message from syslogd@intel-s3e37-04 at Jan 25 14:18:06 ... kernel:Call Trace: Additional info: Can be reproduced across several systems.
This might be a problem with selinux-policy. You can retest with # setenforce 0
Here's a simple test: install selinux-policy of version at least 3.10.0-75.fc16 # setsebool syslog_user_tty 1 # echo l > /proc/sysrq-trigger Do the messages appear as expected?
*** This bug has been marked as a duplicate of bug 765767 ***