Am 30.11.2010 15:38, schrieb Michael Biebl:
On 01.10.2009 08:31, Christoph Martin wrote:
I use the syslog-tls feature to send syslog messages from a bunch of host
to a centralized rsyslog server. On initial startup of rsyslog on
the syslog server it consumes allready about 170M. If I only
Hi Michael,
Am 30.11.2010 15:38, schrieb Michael Biebl:
On 01.10.2009 08:31, Christoph Martin wrote:
I use the syslog-tls feature to send syslog messages from a bunch of host
to a centralized rsyslog server. On initial startup of rsyslog on
the syslog server it consumes allready about 170M.
On 30/11/10 11:38, Michael Biebl wrote:
On 01.10.2009 08:31, Christoph Martin wrote:
I use the syslog-tls feature to send syslog messages from a bunch of host
to a centralized rsyslog server. On initial startup of rsyslog on
the syslog server it consumes allready about 170M. If I only have
To: Rainer Gerhards
Cc: Plamen Tonev; 549...@bugs.debian.org
Subject: Bug#549168: RE: Bug#549168: rsyslog: consumes too much memory
On -10/01/37 16:59, Rainer Gerhards wrote:
-Original Message-
From: Plamen Tonev [mailto:pla...@tonev.net]
Sent: Friday, November 05, 2010 10:45 PM
On 01.10.2009 08:31, Christoph Martin wrote:
I use the syslog-tls feature to send syslog messages from a bunch of host
to a centralized rsyslog server. On initial startup of rsyslog on
the syslog server it consumes allready about 170M. If I only have one
client which sends syslog messages it
On -10/01/37 16:59, Rainer Gerhards wrote:
-Original Message-
From: Plamen Tonev [mailto:pla...@tonev.net]
Sent: Friday, November 05, 2010 10:45 PM
To: 549...@bugs.debian.org
Subject: Bug#549168: rsyslog: consumes too much memory
I'm experiencing the same problem. The rsyslogd
-Original Message-
From: Plamen Tonev [mailto:pla...@tonev.net]
Sent: Friday, November 05, 2010 10:45 PM
To: 549...@bugs.debian.org
Subject: Bug#549168: rsyslog: consumes too much memory
I'm experiencing the same problem. The rsyslogd with gnutls enabled and
1-2 minutes after
I'm experiencing the same problem. The rsyslogd with gnutls enabled and
1-2 minutes after start it is starting to use 100% CPU usage - until
killed. It is some sort of infinite loop...the debug file is REALLY
bigand obviously
something is broken with rsyslog+gnutls.
I was thinking that it
Some additional information.
Previous configuration that fails after a couple of hours:
rsyslog(internal SSL) network --- rsyslog(internal SSL)
A one which works for a couple of days now:
rsyslog(internal SSL) network --- stunnel4 -- rsyslog
--
Marcin Szewczyk
Hi there,
I'm experiencing the same or a similar problem.
There really seams to be an issue with TLS.
I attach the debug output. One file, when memory starts to disappear and
another, 1 million debug lines and 30MB of RAM later, when everything
but RAM comes back to normal.
--
Marcin Szewczyk
Hi Michael,
Michael Biebl schrieb:
Hi Christoph,
could you please attach the configuration you use on the client and server.
Files are attached. master is the server. m1234 and yoda are clients.
local conf is a configuration in /etc/rsyslog.d/
How do you messure the RAM usage?
Output
Christoph Martin schrieb:
I just found out that the logrotation is not automatically configured to
different logfiles like it was in plain old sysklogd. So my syslog.all
file on master has about 134M which would account for the initial size
of rsyslog on this host. But does rsyslog really
Package: rsyslog
Version: 4.2.0-1~bpo50+1
Severity: important
I use the syslog-tls feature to send syslog messages from a bunch of host
to a centralized rsyslog server. On initial startup of rsyslog on
the syslog server it consumes allready about 170M. If I only have one
client which sends
Christoph Martin wrote:
Package: rsyslog
Version: 4.2.0-1~bpo50+1
Severity: important
I use the syslog-tls feature to send syslog messages from a bunch of host
to a centralized rsyslog server. On initial startup of rsyslog on
the syslog server it consumes allready about 170M. If I only
14 matches
Mail list logo
