George Donnelly wrote:
the kernel limits the amount of ram a process can bind by default.
try the following
put this in /boot/loader.conf
kern.maxdsiz="1610612736"
kern.dfldsiz="1610612736"
kerm.maxssiz="1610612736"
Thanks for the hint George, I was able to accomplish this using only
the
This problem will happen and there will still be 1GB of free RAM and it
hasn't touched the swap at all. We are running FreeBSD 4.10 on this box.
the kernel limits the amount of ram a process can bind by default.
try the following
put this in /boot/loader.conf
kern.maxdsiz="1610612736"
ke
Pascal Peregrina wrote:
That looks wierd... Has the instance been running for a while when you
copied the content of the Cache Parameters tab ? I would have expected many
more connections (instead of just 2).
Can you give us your zserver-threads value (zope.conf) ?
It is not set so I assume it
On Sep 13, 2005, at 12:00 PM, Pascal Peregrina wrote:
What's the amount of RAM you have ?
When we started having this problem the box only had 1GB of RAM so we
replaced that RAM completely and put in a fresh 4GB of RAM to hopefully
get rid of the problem. This box is also running 3 other Z
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Calvin Hendryx-Parker wrote:
> In the last month I have started to get these errors using Zope 2.7.7 in
> a ZEO configuration with one client and one storage server:
>
> --
> 2005-09-12T23:46:07 ERROR(200) ZODB Couldn't load state for 0x055ba7
> T
