Never mind, operator error. Wasn't the python i thought it was...
it was a binary copied from another machine and built with a
different glibc apparently.
On Wed, Aug 20, 2003 at 07:19:01PM -0400, Paul Winkler wrote:
> Like the subject says... python2.1 wo_pcgi fails...
(snip)
--
Paul Winkler
h
Leonardo,
If you're using Linux, you might be able to take some of the pressure
off by using AutoLance to automatically restart the server when memory
grows above a certain threshhold.
http://zope.org/Members/mcdonc/Products/AutoLance/view
On Sat, 2003-08-23 at 15:17, Jens Vagelpohl wrote:
> We
On Friday 22 August 2003 03:38 pm, Leonardo Rochael Almeida wrote:
> Hi,
>
> In trying to narrow down the causes of the leak, we detected what looks
> like a minor one. If you insert a very simple dtml method in Zope root
> and bang on it at a rate of, say, 100 requests per second, Zope will
> incr
alan milligan wrote at 2003-8-20 04:43 +:
> ...
> >"mapply" is often tricked out by a "func_code" definition.
> >Maybe, your class has such an attribute and it does not
> >match the "__call__" signature?
>
> Hmmm - this isn't MY class, it's HelpSys::STXTopic. I can't see any
> func_co
Leonardo Rochael Almeida wrote at 2003-8-22 18:38 -0300:
> ...
> I tried installing the LeakFinder product but discovered it didn't work
> before stumbling in a message in the archives that told me exactly that
> :-) The RefCounts view in the LeakFinder object fails with the following
> traceb
Paul Winkler wrote at 2003-8-20 19:19 -0400:
> Like the subject says... python2.1 wo_pcgi fails...
>
> this is the same python 2.1.3 that I built from source, and which
> I used to build and run zope 2.6.1 for a few months now...
>
>
> -
>>> Paul Winkler wrote
> Like the subject says... python2.1 wo_pcgi fails...
>
> this is the same python 2.1.3 that I built from source, and which
> I used to build and run zope 2.6.1 for a few months now...
>
> gcc -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -Wall
> -Wstrict-prototype
On 08/22/2003 05:38 PM, Leonardo Rochael Almeida wrote:
In time, DateTime refcounts eventually dwarves the second place by an
order of magnitude. I think this is related to the fact that DateTime
instances are stored as metadata, even though the date indexes have been
converted to DateTime indexes.
Well, to at least reduce the immediate pressure, why don't you throw
more RAM into that server? Memory is cheap.
jens
On Friday, Aug 22, 2003, at 17:38 US/Eastern, Leonardo Rochael Almeida
wrote:
Hi,
For a long time now, one of our clients, running Zope 2.5.1, has been
experiencing memory lea
