Clearly, no one has any particularly helpful suggestions on what to do
differently.
Apache, even under relatively light load, swallowed up 700+MB over two days.
So the only path forward I can see is to restart apache fairly regularly and
delve in to switching to nginx.
Thanks to those of you w
On 20/11/2009, at 18:21 , Nick Kew wrote:
> On 20 Nov 2009, at 09:59, Peter N Lewis wrote:
>
>> On 20/11/2009, at 17:29 , André Warnier wrote:
>>
>>> Peter N Lewis wrote:
>>>> I am having a serious problem with my site running out of memory. apache
>
On 20/11/2009, at 18:20 , André Warnier wrote:
> Peter N Lewis wrote:
>> I already have:
>>MaxRequestsPerChild 1000
>> So the worker processes should die and clean that out.
>> I'm suspicious that the worker threads are not dieing because I've seen
&g
On 20/11/2009, at 17:29 , André Warnier wrote:
> Peter N Lewis wrote:
>> I am having a serious problem with my site running out of memory. apache is
>> leaking memory/processes.
>
> Probably a lot more likely : your "mod_perl pages" are leaking memory.
> Pe
I am having a serious problem with my site running out of memory. apache is
leaking memory/processes.
I have half a dozen virtual hosts, but relatively light traffic, around 40,000
accesses per day (that includes all files on all hosts), so on the order of 1
access per second average.
Current
At 21:48 -0500 6/6/06, William A. Rowe, Jr. wrote:
apachectl should not change significantly, why not just leave it alone
between minor subversion bumps?
That's true, and I could just copy apachectl twice, configure both
and then hope nothing changes, but it disturbs me to copy something
out
On my server, I run the httpd daemon twice, using almost identical
httpd.conf files, one on the main port (the live server) and one on a
high numbered port (my working draft). Then I edit the
files/configuration of the working draft server, restarting it as
necessary. When all changes are in
