We do experience the same issue running the latest version from
backports (8.23.0-2~bpo8+1).
Rsyslog without TLS is stable, with TLS we are getting hang on higher
amount of messages (120.000.000 per day, not sure about the peak value
during the hang).
Process stucked in sleep state - consuming on
On Tue, 17 May 2016 06:28:50 +0200 Michael Biebl wrote:
> On Thu, 10 Mar 2016 17:23:50 +0100 Luca BRUNO wrote:
> > On Wednesday, March 09, 2016 09:09:42 PM you wrote:
> >
> > > 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 app
On Thu, 10 Mar 2016 17:23:50 +0100 Luca BRUNO wrote:
> On Wednesday, March 09, 2016 09:09:42 PM you wrote:
>
> > 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 actuall
On Wednesday, March 09, 2016 09:09:42 PM you wrote:
> 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.
I have this running live in a log aggregatio
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 r
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 rec
6 matches
Mail list logo
