> -----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 start it is starting to use 100% CPU usage - until > killed. It is some sort of infinite loop...the debug file is REALLY > big....and obviously > something is broken with rsyslog+gnutls. > I was thinking that it was some RBAC restrtiction with my grsec kernel, > but I have compiled clean vanilla 2.6.36 kernel - and surprisingly - it > takes 100% CPU even without grsecurity restrictions.
I am the rsyslog author. I just came across this very useful Debian bug report. I am tracking this issue for some while now in rsyslog's bugzilla under http://bugzilla.adiscon.com/show_bug.cgi?id=194 A big problem is that I seem to be unable to reproduce the issue (but I will retry with the configs posted here, however, the look extremely similar to what I already use). Question now: would those of you who can reproduce it be willing to test a special version that I modify so that it contains some more instrumentation? >From what I have seen so far, it looks that for some reason GnuTLS requires an operaton retry (something absolutely OK with TLS) but then seems to be unable to finish it. That leads to a retry loop. But I have very little insight into the situation and so any help is deeply appreciated. Thanks, Rainer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
