On Sat, 4 Nov 2000, kyue wrote:
>
>
>
> Hi,everyone
>
> I found one messages in my log files,I don't know what it means,would everyone like to explain it for me?
>
> Log messages:
> Unable to allocate 4096 blocks of 1bytes(I don't understand this sentence!!!)
> squid parent:child process 226 exited with status 1
> child process 2409 started
8.7. xmalloc: Unable to allocate 4096 bytes!
by Henrik Nordstrom <mailto:hno@hem.passagen.se>
Messages like "FATAL: xcalloc: Unable to allocate 4096 blocks of 1
bytes!" appear when Squid can't allocate more memory, and on most
operating systems (inclusive BSD) there are only two possible reasons:
1. The machine is out of swap
2. The process' maximum data segment size has been reached
The first case is detected using the normal swap monitoring tools
available on the platform (pstat on SunOS, perhaps pstat is used on
BSD as well).
To tell if it is the second case, first rule out the first case and
then monitor the size of the Squid process. If it dies at a certain
size with plenty of swap left then the max data segment size is
reached without no doubts.
The data segment size can be limited by two factors:
1. Kernel imposed maximum, which no user can go above
2. The size set with ulimit, which the user can control.
When squid starts it sets data and file ulimit's to the hard level. If
you manually tune ulimit before starting Squid make sure that you set
the hard limit and not only the soft limit (the default operation of
ulimit is to only change the soft limit). root is allowed to raise the
soft limit above the hard limit.
This command prints the hard limits:
ulimit -aH
This command sets the data size to unlimited:
ulimit -HSd unlimited
-- To unsubscribe, see http://www.squid-cache.org/mailing-lists.htmlReceived on Sat Nov 04 2000 - 01:49:00 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:56:14 MST