Re: BSDI 2.1 + squid => xmalloc problem

const@cris.crimea.ua writes:

>Dear Squider,
>
>I have follow problem:
>my squid was perfectly work during the several month, but the last week
>squid is abnormally terminates about 3 times a day with such diagnostic:
>
>cache.log:
>
>----
>FATAL: xmalloc: Unable to allocate 8192 bytes!
>
>Squid Cache (Version 1.1.10): Terminated abnormally.
>CPU Usage: user 110 sys 331
>Maximum Resident Size: 0 KB
>Page faults with physical i/o: 0
>97/06/30 16:05:50| storeWriteCleanLog: Starting...
>97/06/30 16:06:12| 4096 lines written so far.
>97/06/30 16:06:38| 8192 lines written so far.
>...
>---
>
>Please help.
>
>Squid version 1.1.10 + gmalloc
>OS: BSDI 2.1
>RAM: 64M
>cache_swap: 1.8G

Have you tried the things suggested in the FAQ?

http://squid.nlanr.net/Squid/FAQ/FAQ-7.html#ss7.5

7.5 My squid dies periodically, and I see log entries complaining about
    being unable to malloc(3) more memory, but my system has lots of RAM
    available!

In addition to maximum file descriptor limits, many systems also have
limits on the maximum amount of memory that can be devoted to a
process, especially for non-root processes. BSD/OS happens to have a
fairly low limit which you may want to increase. Edit your kernel
configuration file and change (or add) these lines as appropriate:

        options DFLDSIZ=67108864 # 64 meg default max data size (was 16)
        options MAXDSIZ=134217728 # 128 meg max data size (was 64)

This method requires a kernel rebuild and reboot.

To increase the data size for Digital UNIX, edit the file /etc/sysconfigtab and add the entry...

        proc:
                per-proc-data-size=1073741824

Or, with csh, use the limit command, such as

        zpoprp.zpo.dec.com > limit datasize 1024M

Editing /etc/sysconfigtab requires a reboot, but the limit command doesn't.

Duane W.
Received on Mon Jun 30 1997 - 09:21:15 MDT