Mr. Demeanour wrote: > Rainer Gerhards wrote: >>>> So my suggestion is to move to v4-stable and see if the problem >>>> persists there (obviously, contrary to what I said, v5 would >>>> have fixed it in that case as well - so never trust a dev... >>>> ;)). >> >> args, important type: suggest to move to v4-beta NOT -stable... > > OK, so it looks like I've still got the problem, with v4 beta > (4.5.6). I'll have another go with valgrind tomorrow.
I have been running a setup with 4.5.6 collecting messages by GnuTLS only, and logging to a file; and the problem has failed to materialise. Perhaps I didn't run it for long enough; but a few hours is normally sufficient for serious memory depletion to occur, and it hasn't so far. The other variables are that only one (LAN) client is logging to this instance - all previous runs have involved multiple clients, some logging via the internet; and that only one input and one output method is configured. Previous tests have had both imudp and imtcp configured, and have used both omfile and ommysql. I've now changed this from logging to a file to log via mySQL. If that remains stable after several hours, I'll reconfigure with dual input and output methods; then with multiple clients. Eventually I should be able to describe a method of replication. -- Jack. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
