On 2011-10-09, Jakub Jankowski wrote:
On 2011-10-09, Balazs Scheidler wrote:
On Wed, 2011-10-05 at 01:44 +0200, Jakub Jankowski wrote:
On Mon, 3 Oct 2011 14:34:13 +0200 (CEST), Jakub Jankowski wrote:
I think I spoke too soon. :-/ See attached cacti graph. This is basically an output of awk '/VmRSS:/ { $print $2*1024 }' /proc/$(cat /var/run/syslog-ng.pid)/status on git head ("3.3.1" ATM). There must be something else going on; any hints on how to diagnose this? It definitely seems to be a leak of some kind. If at all possible, running it for some time under valgrind like you did previously would be tremendous. I've run half my "live" traffic for approx. 5 minutes through another node, with syslog-ng 3.3.1 running under valgrind. Log available at: http://toxcorp.com/stuff/syslog-ng-leak/s3.3.1-prod-half-5min.log Does it ring any bells (it doesn't for me). Should I test it longer?
I've let it run ~83 minutes this time. No substantial changes in valgrind output: http://toxcorp.com/stuff/syslog-ng-leak/s3.3.1-prod-half-83min.log What baffles me is the number of errors related to "Syscall param epoll_ctl(event) points to uninitialised byte(s)". Anything else looks interesting? During this run, VmRSS kept rising, from: Sun Oct 9 21:44:51 CEST 2011; VmRSS: 3804 kB Sun Oct 9 21:44:52 CEST 2011; VmRSS: 3816 kB Sun Oct 9 21:44:53 CEST 2011; VmRSS: 3820 kB Sun Oct 9 21:44:54 CEST 2011; VmRSS: 3844 kB (...) to: Sun Oct 9 23:07:37 CEST 2011; VmRSS: 444760 kB Sun Oct 9 23:07:38 CEST 2011; VmRSS: 444764 kB Sun Oct 9 23:07:39 CEST 2011; VmRSS: 444764 kB Sun Oct 9 23:07:40 CEST 2011; VmRSS: 444880 kB Sun Oct 9 23:07:41 CEST 2011; VmRSS: 444896 kB Sun Oct 9 23:07:42 CEST 2011; VmRSS: 444896 kB Sun Oct 9 23:07:43 CEST 2011; VmRSS: 444896 kB Sun Oct 9 23:07:44 CEST 2011; VmRSS: 445332 kB HTH -- Jakub Jankowski|shasta@toxcorp.com|http://toxcorp.com/ GPG: FCBF F03D 9ADB B768 8B92 BB52 0341 9037 A875 942D