On 06/30/2014 05:12 PM, David Lang wrote: > On Mon, 30 Jun 2014, Chris J Arges wrote: > >> On 06/30/2014 03:02 PM, David Lang wrote: >>> On Mon, 30 Jun 2014, Chris J Arges wrote: >>> >>>> Hi, >>>> I've noticed that linux kernels before this commit behave >>>> differently in >>>> rsyslog: >>>> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=7ff9554bb578ba02166071d2d487b7fc7d860d62 >>>> >>>> >>>> >>>> What I've observed is if I do something like the following in kernels >>>> before this patch: >>>> # echo test > /dev/kmsg >>>> >>>> This will show up in kern.log with something as simple as: >>>> kern.* /var/log/kern.log >>>> >>>> However kernels after that patch no longer show up in kern.log with the >>>> same rule. What I've noticed is the default userspace kmsg priority >>>> level is different (observed via dmesg -r): >>>> >>>> Before that patch if we echo something into /dev/kmsg we get: >>>> <4>[ 35.084348] before >>>> >>>> If we do it on or after that patch we get: >>>> <12>[ 71.091005] after >>>> >>>> According to this documentation: >>>> http://www.mjmwired.net/kernel/Documentation/ABI/testing/dev-kmsg >>>> >>>> The <N> value is both the priority and facility combined (after that >>>> patch was introduced). >>>> >>>> Is there a way to specify kernel priority/facility levels greater >>>> than 7 >>>> in order to log userspace generated kmsg entries? >>> >>> nothing in rsyslog limits these values. what value are you trying to >>> use? >>> >> >> So, I've looked here: >> http://www.rsyslog.com/doc/imklog.html >> >> I've added this option to /etc/rsyslog.conf: >> $ConsoleLogLevel 14 >> >> And reloaded/restarted rsyslogd and they still don't seem to show kernel >> messages in /var/log/kern.log >> >> I did '# echo test > /dev/kmsg', and nothing shows up in kern.log/syslog. > > The first thing I would suggest is logging everything to a file > > *.* /var/log/testmessages > > and see if it shows up there. > > If it does, then it's just tracking down what facility/priority the log > is written as (logging with the format RSYSLOG_DebugFormat makes this easy) > > If it doesn't then we need to see what's changed. are you running > systemd? if so, is systemd set to forward the logs to rsyslog? > > David Lang > David, I figured it out. I needed to use $KLogPermitNonKernelFacility on
Now those messages are showing up properly. Thanks for your patience and help! --chris j arges _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
