brian.percival at targetlabs
Sep 13, 2011, 8:15 AM
Post #4 of 9
Thanks for your response.
I doing some additional research, we found that it seems to be from
Bricolage killing the http process after reaching the max_process_size that
is currently defined in our Bricolage config at 222880.
CHECK_PROCESS_SIZE = Yes
MAX_PROCESS_SIZE = 222880
CHECK_FREQUENCY = 10
MIN_SHARE_SIZE = 0
MAX_UNSHARED_SIZE = 0
I am seeing sizes of the http process of 354088, 373852, 347992 before the
process is being killed so I have raised it to 512000. But this poses
another question. What is the recommended size under a normal load? extra
load, etc..? Do these higher http sizes indicate another problem in our
On Mon, Sep 12, 2011 at 5:02 PM, David E. Wheeler <david [at] kineticode>wrote:
> On Sep 12, 2011, at 1:32 PM, Phillip Smith wrote:
> > I've never seen that error…
> > What's your set-up? Bricolage version, server OS, database, etc.?
> Also check your template sources for that string. Doesn't sound like a core
> Bricolage error.
Thanks for using Target Labs, Inc.!
The Target Labs, Inc. Team
brian.percival [at] targetlabs
Washington D.C. 301.842.7151
Google Talk: bpercival [at] gmail
Messenger: live [at] brianpercival
Skype: bjpercival <bpercival [at] gmail>