| Summary: | A squid process larger than 3G | ||
|---|---|---|---|
| Product: | Base System | Reporter: | wkwu <wkwu> |
| Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 5.2.1-RELEASE | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
wkwu
2004-03-31 07:50:20 UTC
On Wed, Mar 31, 2004 at 02:44:41PM +0800, Wei-Kai Wu wrote:
> >Description:
> When running squid allocated more than 3G memory, the squid will crash.
> I have tuned the kernel with MAXDSIZ=(3072UL*1024*1024) and KVA_PAGES=192.
>
> If I enlarged the MAXDSIZ > 3072, the system cannot boot with error message:
> (after loading kernel, running init)
> init in malloc(): error: recursive call
> init in malloc(): error: recursive call
> ...
What you described is not squid crashing, but init.
It sounds like you've adjusted the kernel parameters inappropriately,
and that's what you need to fix. I don't know the solution off-hand,
but check the mailing list archives for extensive discussion on how to
tune kernel parameters for large-memory configurations.
Be aware that what you're trying to do may be impossible - i.e. if you
really need 3GB of RAM for squid, it sounds like it's being heavily
used, and may therefore also require a lot of kernel memory to manage
the network resources.q If you need more than 1GB of kernel memory,
you're out of luck with only 4GB total.
Kris
----- Forwarded message from Kris Kennaway <kris@obsecurity.org> ----- X-Original-To: kris@obsecurity.org Delivered-To: kkenn@obsecurity.dyndns.org Date: Sat, 24 Apr 2004 01:01:24 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/64971: A squid process larger than 3G In-Reply-To: <200404010200.i3120e8s065381@freefall.freebsd.org> User-Agent: Mutt/1.4.2.1i X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.17.5 On Wed, Mar 31, 2004 at 06:00:40PM -0800, Kris Kennaway wrote: > What you described is not squid crashing, but init. > > It sounds like you've adjusted the kernel parameters inappropriately, > and that's what you need to fix. I don't know the solution off-hand, > but check the mailing list archives for extensive discussion on how to > tune kernel parameters for large-memory configurations. > > Be aware that what you're trying to do may be impossible - i.e. if you > really need 3GB of RAM for squid, it sounds like it's being heavily > used, and may therefore also require a lot of kernel memory to manage > the network resources.q If you need more than 1GB of kernel memory, > you're out of luck with only 4GB total. Did you resolve this problem? Kris ----- End forwarded message ----- State Changed From-To: open->closed major feedback timeout (since 2004) |