Thanks for the log file. Unfortunately, it is not a full run. I gues I needed to make some more things clear.
The command line you need to use here $ valgrind /usr/sbin/rsyslogd -c4 -d >rsyslog.log 2>&1 Is the same that you usually use, except that -n must be specified. I unfortunately do no know what you (or better: your distro) usually uses, but you may see it in a process list. Before you start it that way, you must stop the regular syslogd and you must be sure to su to root. The -d switch, while generally useful, takes a lot of time and will generate an immense log. So it is best to not specify it for now. What I am after are valgrind violations (these are printed during the run) and the memory stats at the end of the run. The later will show any memory leaks. The log I received did not receive any message via TLS but two via UDP. It looks like a very short run. Thanks again for your help, I hope I have now explained better ;) Rainer > -----Original Message----- > From: Mr. Demeanour [mailto:[email protected]] > Sent: Monday, November 09, 2009 8:03 PM > To: Rainer Gerhards > Subject: Re: Rsyslog 4.4.2: server out-of-memory with gnutls > (valgrind log) > > Hi, > > I finally got a decent valgrind log using this command: > $ valgrind /usr/sbin/rsyslogd -c4 -d >rsyslog.log 2>&1 > > The log is attached. Free memory was declining steadily > throughout this run. > > Thanks, > -- > Jack. > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
