Hi David. It's Perl's fault, not Bricolage's.
The good news is that CHECK_PROCESS_SIZE and
Apache::SizeLimit are your
friends.
See here:
http://www.bri
colage.cc/docs/faq/#s6q6
Hope this helps,
Bret
On Sun, 2007-12-09 at 05:14 -0500, Beaudet, David P. wrote:
> I had Bricolage running continuously without restarting
for about 2 months. Late last week, I got a call from a
user that the system was not responding. When I logged into
the machine, there were several httpd processes that had
gobbled up all the available memory and nearly overflowed my
swap space. I couldn't even shut down the machine from the
command line in a reasonable amount of time due to it being
so unresponsive so I ended up taking it down the hard way.
>
> I've put in a cron job to restart the bricolage web
server once per evening. Is this a common practice? Anyone
know if mod_perl or parts of Bric leak memory?
>
> Thanks,
>
> Dave
--
Bret Dawson
Producer
Pectopah Productions Inc.
(416) 895-7635
bret pectopah.com
www.pectopah.com
|