Am 04.03.2016 um 17:45 schrieb Luca Bruno: > 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
The upstream bug report is inconclusive whether this is fixed or not by this pull request. See https://github.com/rsyslog/rsyslog/issues/318#issuecomment-159699715 > 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, I don't have the setup to test this. So if you want to see this fixed in stable, it would be great if you can apply the upstream fix on top of 8.4.2 and test whether it actually fixes the issue. Once that is done, someone needs to ask the stable release team via a jessie-pu bug for their approval. I'm happy to prepare a stable release after that. Regards, Micahel -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
