Your message dated Tue, 5 Sep 2017 19:11:53 +0200
with message-id <[email protected]>
and subject line Re: rsyslog: New style permitnonkernelfacility imklog option 
inside module() doesn't work
has caused the Debian Bug report #868889,
regarding rsyslog: New style permitnonkernelfacility imklog option inside 
module() doesn't work
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
868889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868889
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rsyslog
Version: 8.28.0-1
Severity: normal

Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1703987
Upstream bug: https://github.com/rsyslog/rsyslog/issues/477
Upstream commit:
https://github.com/PascalWithopf/rsyslog/commit/5c35619385bbe50979fa417e6f1b14df531b2a4a

Dear Maintainer,

There are two ways to load the imklog module and pass it an option
(PermitNonKernelFacility in this case).

a) legacy
$ModLoad imklog
$KLogPermitNonKernelFacility on

b) "new style", also referred to as "v6+":
module(load="imklog" permitnonkernelfacility="on")

Upstream isn't honouring the new style option setting due to a bug of its
own:
https://github.com/rsyslog/rsyslog/issues/477

Patch was committed.

With the legacy config:
#module(load="imklog" permitnonkernelfacility="on")
$ModLoad imklog
$KLogPermitNonKernelFacility on

I get kernel messages in /var/log/syslog:
root@nsn7:~# grep andreas-was-here /var/log/syslog
root@nsn7:~# echo andreas-was-here > /dev/kmsg
root@nsn7:~# grep andreas-was-here /var/log/syslog
Jul 12 16:46:33 nsn7 kernel: [27774.476193] andreas-was-here
root@nsn7:~#

But with this new v6 config style:
module(load="imklog" permitnonkernelfacility="on") # provides kernel
logging support
#$ModLoad imklog
#$KLogPermitNonKernelFacility on

The text doesn't show up in /var/log/syslog. That's the upstream bug.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.11.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages rsyslog depends on:
ii  init-system-helpers  1.48
ii  libc6                2.24-12
ii  libestr0             0.1.10-2
ii  libfastjson4         0.99.6-1
ii  liblogging-stdlog0   1.0.6-1
ii  liblognorm5          2.0.3-1
ii  libsystemd0          233-10
ii  libuuid1             2.29.2-2
ii  lsb-base             9.20161125
ii  zlib1g               1:1.2.8.dfsg-5

Versions of packages rsyslog recommends:
ii  logrotate  3.11.0-0.1

Versions of packages rsyslog suggests:
pn  rsyslog-doc                    <none>
pn  rsyslog-gnutls                 <none>
pn  rsyslog-gssapi                 <none>
pn  rsyslog-mongodb                <none>
pn  rsyslog-mysql | rsyslog-pgsql  <none>
pn  rsyslog-relp                   <none>

-- Configuration Files:
/etc/rsyslog.conf changed:
module(load="imuxsock") # provides support for local system logging
module(load="imklog" permitnonkernelfacility="on")   # provides kernel
logging support
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
$FileOwner root
$FileGroup adm
$FileCreateMode 0640
$DirCreateMode 0755
$Umask 0022
$WorkDirectory /var/spool/rsyslog
$IncludeConfig /etc/rsyslog.d/*.conf
auth,authpriv.* /var/log/auth.log
*.*;auth,authpriv.none -/var/log/syslog
daemon.* -/var/log/daemon.log
kern.* -/var/log/kern.log
lpr.* -/var/log/lpr.log
mail.* -/var/log/mail.log
user.* -/var/log/user.log
mail.info -/var/log/mail.info
mail.warn -/var/log/mail.warn
mail.err /var/log/mail.err
*.=debug;\
auth,authpriv.none;\
news.none;mail.none -/var/log/debug
*.=info;*.=notice;*.=warn;\
auth,authpriv.none;\
cron,daemon.none;\
mail,news.none -/var/log/messages
*.emerg :omusrmsg:*


-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 8.29.0-1

On Wed, 19 Jul 2017 10:49:14 -0300 Andreas Hasenack
<[email protected]> wrote:
> Package: rsyslog
> Version: 8.28.0-1
> Severity: normal
> 
> Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1703987
> Upstream bug: https://github.com/rsyslog/rsyslog/issues/477
> Upstream commit:
> https://github.com/PascalWithopf/rsyslog/commit/5c35619385bbe50979fa417e6f1b14df531b2a4a
> 
> Dear Maintainer,
> 
> There are two ways to load the imklog module and pass it an option
> (PermitNonKernelFacility in this case).
> 
> a) legacy
> $ModLoad imklog
> $KLogPermitNonKernelFacility on
> 
> b) "new style", also referred to as "v6+":
> module(load="imklog" permitnonkernelfacility="on")
> 
> Upstream isn't honouring the new style option setting due to a bug of its
> own:
> https://github.com/rsyslog/rsyslog/issues/477
> 
> Patch was committed.
> 
> With the legacy config:
> #module(load="imklog" permitnonkernelfacility="on")
> $ModLoad imklog
> $KLogPermitNonKernelFacility on
> 
> I get kernel messages in /var/log/syslog:
> root@nsn7:~# grep andreas-was-here /var/log/syslog
> root@nsn7:~# echo andreas-was-here > /dev/kmsg
> root@nsn7:~# grep andreas-was-here /var/log/syslog
> Jul 12 16:46:33 nsn7 kernel: [27774.476193] andreas-was-here
> root@nsn7:~#
> 
> But with this new v6 config style:
> module(load="imklog" permitnonkernelfacility="on") # provides kernel
> logging support
> #$ModLoad imklog
> #$KLogPermitNonKernelFacility on
> 
> The text doesn't show up in /var/log/syslog. That's the upstream bug.

Thanks for the bug report.
Should be fixed by the new upstream release 8.29.0

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to