topic Re: frecover(5441) malloc error: not enough virtual memory in Operating System - HP-UX

frecover(5441) malloc error: not enough virtual memory

michi79 — Fri, 30 Nov 2001 10:49:27 GMT

to use fastsearch.
check swap und maxdsiz

swapinfo shows that:
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 409600 34148 375452 8% 0 - 1 /dev/vg00/lvol2
reserve - 44260 -44260
memory 86120 32120 54000 37%

maxdsiz is standard, the box has
256MB ram and the files on disc
are 56 GB

How should maxdsiz be configured ?
any ideas ??

L. Wahl

Re: frecover(5441) malloc error: not enough virtual memory

T. M. Louah — Fri, 30 Nov 2001 11:52:32 GMT

Start by increasing swap, then make maxdsiz value equals to total amount of swap.

Re: frecover(5441) malloc error: not enough virtual memory

Steven Gillard_2 — Fri, 30 Nov 2001 12:25:08 GMT

If maxdsiz is still at the default of 64Meg then this is likely to be your problem. 256Meg on a system is not a lot to play with, so I'd probably increase maxdsiz to match this.

Regards,
Steve

Re: frecover(5441) malloc error: not enough virtual memory

Krishna Prasad — Fri, 30 Nov 2001 15:08:43 GMT

I had this exact message at an off site DR test. We had to increase maxswapchunks and maxdsize, then add swapspace, reboot and this fixed the problem.

As far as a guide to how big to make maxdsize???

If you are running HPUX 11.0 you can make it as big as you wish. I have never heard of it causing a problem being to big, just to small.

Re: frecover(5441) malloc error: not enough virtual memory

A. Clay Stephenson — Fri, 30 Nov 2001 15:18:02 GMT

Hi:

While it is true that you can set maxdsiz (or the 64-bit equivalent) to large values; it is generally not a good idea. The value is simply a 'fence' and consumes no resources but it does serve a valuable purpose. Consider a really big process eating dynamically allocating memory. Eventually, the process will
will consume all the system-wide resources and bring the entire system to its knees. That is what maxdsiz is there to prevent. THe idea is that the offending process will fail during a malloc() and set ENOMEM. I would never set maxdsiz to the total size of virual memory; that truly will bring a box down in the above scenario. Now as to what is a good value - it depends but in 32-bit land 1GB or 512 MB is reasonable.