On 2004.10.06, Andrew Grumet <[EMAIL PROTECTED]> wrote: > We don't seem to be out of the woods yet on this. We dumped core today, > with this message in the log > > unable to realloc 2479192 bytes > > Coredump is 2.4GB, but I'm not sure if we got the whole coredump because the > disk filled up :( > > Our last restart was about 3 hours ago. The nsd process is now size 1090M > and seems to be growing.
On Solaris, the per-process memory limit is 4 GB. Due to heap fragmentation and so on, the practical limit is ~3.2 GB. As your nsd process grows to the 3.0+ GB range, the odds of not being able to allocate (or reallocate) memory causing a fatal error like the one you saw, increases. Has your AOLserver always run this large? If not, look at what code changes have been made recently and try and identify where you're not cleaning up resources which will continue to consume memory ... There's no easy answer here without being familiar with the code you're running and what changes have been made recently. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
