Package: rsyslog Version: 8.1901.0-1 Severity: important Tags: upstream patch
Dear Maintainer, In high-volume situations, omfile with asyncWriting enabled can stop writing to output files and remain stuck there until rsyslog is restarted. I have seen this twice in the last couple of months on my buster hosts. Upstream bug report: https://github.com/rsyslog/rsyslog/issues/1701 Upstream fix: https://github.com/rsyslog/rsyslog/pull/2794 This patch was released in upstream v8.2012, and so is likely also fixed in Debian's rsyslog 8.2012.0-1 (testing) and 8.2102.0-2 (unstable). I suggest a backported patch for the next stable point release and/or an updated package on buster-backports would be nice for those who don't have the ability to patch and build their own packages. Thanks! Rob N. -- System Information: Debian Release: 10.8 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-0.bpo.3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages rsyslog depends on: ii init-system-helpers 1.56+nmu1 ii libc6 2.28-10 ii libestr0 0.1.10-2.1 ii libfastjson4 0.99.8-2 ii liblognorm5 2.0.5-1 ii libsystemd0 241-7~deb10u6 ii libuuid1 2.33.1-0.1 ii lsb-base 10.2019051400 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages rsyslog recommends: ii logrotate 3.14.0-4 Versions of packages rsyslog suggests: pn rsyslog-doc <none> ii rsyslog-gnutls 8.1901.0-1 pn rsyslog-gssapi <none> pn rsyslog-mongodb <none> pn rsyslog-mysql | rsyslog-pgsql <none> pn rsyslog-relp <none> -- Configuration Files: /etc/logrotate.d/rsyslog changed [not included] /etc/rsyslog.conf changed [not included] -- no debconf information
