Re: Backports.org
Nate Duehr wrote: > Mike Dresser wrote: >> Anyone know what is going on with www.backports.org? >> >> I can get at it from a few rare hosts, but from most of the hosts I've >> tried it simply times out. Traceroute reveals it dies in the >> eurorings.net, and from another host i-p-x.de >> >> I had to use google's cache to get a peek at the mirror listing in order >> to find replacement deb lines that worked. >> >> Mike > Dies from my work connection. Very slow (350+ms) from Denver, Colorado > InterNAP/pnap connection on one of my home boxes. The above traceroute > shows the work connection. Very fast from here (T-Online, Germany). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SOLVED
Hugo Vanwoerkom wrote: > Andreas Schwarz wrote: >> Andreas Schwarz wrote: >> >>>Hello, >>> >>>I'm using Apache from Debian Woody on my server. Now I noticed that >>>Apache is eating up more and more memory, so that I have to restart it >>>every few days. >> >> >> I found the reason: libapache-mod-ruby 1.0.7-1 is leaking memory when >> Apache receives USR1. > > And how did you do that? I disabled module after module until I saw that "/etc/init.d/apache reload" didn't increase the memory usage of apache (ps aux | grep apache). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
SOLVED (was: Re: Apache memory leak)
Andreas Schwarz wrote: > Hello, > > I'm using Apache from Debian Woody on my server. Now I noticed that > Apache is eating up more and more memory, so that I have to restart it > every few days. I found the reason: libapache-mod-ruby 1.0.7-1 is leaking memory when Apache receives USR1. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Apache memory leak
Hello, I'm using Apache from Debian Woody on my server. Now I noticed that Apache is eating up more and more memory, so that I have to restart it every few days. The following graph of the swap usage illustrates the problem: https://andreas-s.net/mrtg/localhost.swap-week.png The big drop around saturday evening was when I restarted Apache. It seems this problem exists since I have set up a cronjob to run logrotate every hour to update my statistics. The rotation itself is only done once per week, but every time the logrotate script is run, it executes /etc/init.d/apache reload. So I tried to run "/etc/init.d/apache reload manually", and I could see the apache memory usage increase by about 500kB (fits quite well to the swapping graph): Before: 9765 www-data 10 0 24836 21M 19968 R 4.8 21.8 0:00 apache After /etc/init.d/apache reload: 10031 www-data 4 0 26888 23M 23508 S 0.0 23.8 0:00 apache Any ideas on how I could track down this problem? Andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
