[tproxy] anything known about potential memory leaks in tproxy 1.1.3 ?

Lennert Buytenhek buytenh@wantstofly.org
Fri, 2 Apr 2004 09:53:47 +0200


Our production firewall/transproxy suddenly became _really_ unresponsive
a few days ago after ~120 days of uptime, from what seems to have been a
memory leak.

The machine has 1GB of memory, but the amount of page cache was really small,
the number of processes waiting for disk I/O was about 30, and at avg 4MB/sec
reading from disk it was seeking all over the place.  Also, bash would
sometimes say something along the lines of 'resource unavailable' when
starting subprocesses.

Temporarily disabling the transproxy function by deleting the redirect rule
caused the disk to go idle (our transproxy-using app intercepts HTTP requests
and answers the requests locally for static data, fileset is about 5GB but
~200MB of it accounts for 90% of the hits.)  But every little thing that I
tried, even an ls or a grep in /etc caused massive disk I/O.

I hastily rebooted the machine and thus have no ways of debugging this
anymore.  But I was wondering, is anything known about memory leaks in the
1.1.3 version of the tproxy code?  I checked the changelogs, but couldn't
find anything related to memleaks.

Should I schedule maintenance to move the machine to 1.9.1?  Any other
advice?  (It's not a problem for me to schedule the machine to be rebooted
every 90 days or something like that.)