Package: rsyslog-gnutls Version: 8.4.2-1+deb8u2 Severity: grave Tags: patch upstream Justification: causes non-serious data loss
I have a log-aggregating server using rsyslog to receive multiple streams (both UDP and TCP), including some remote logs via TLS. I'm experiencing a lock of the TLS receiver under normal usage, and consequently the TLS-receiving thread of rsyslog using 100% CPU. After some initial debugging, this seems to be the same upstream bug as reported here: https://github.com/rsyslog/rsyslog/issues/318 This has been fixed in the latest upstream version: https://github.com/rsyslog/rsyslog/pull/494 I think this basically affects all setups where rsyslog is used as a TLS receiver, and results in losing logs on the receiving side (and increased buffer pressure on senders). Thus I'm reporting this at severity grave. It would be great if this could be fixed for current stable version, as rsyslog-gnutls is too buggy for production usage at the moment. -- System Information: Debian Release: 8.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages rsyslog-gnutls depends on: ii libc6 2.19-18+deb8u3 ii libgnutls-deb0-28 3.3.8-6+deb8u3 ii libjson-c2 0.11-4 ii rsyslog 8.4.2-1+deb8u2 rsyslog-gnutls recommends no packages. Versions of packages rsyslog-gnutls suggests: ii gnutls-bin 3.3.8-6+deb8u3 -- no debconf information
