Highlighted
Anonymous_User Absent Member.
Absent Member.
1792 views

memory allocator problem

i have a nw65sp8 server with 4GB memory and some problems :

Loading Module DSMC.NLM [ OK ]

6.06.2009 11.17.29 : SERVER-5.70-0 [nmID=6001D]
Cache memory allocator out of available memory.


6.06.2009 11.17.29 : SERVER-5.70-0 [nmID=2000A]
Short term memory allocator is out of memory.
1 attempts to get more memory failed.
request size in bytes 20971524 from Module RTVSCAN.NLM


6.06.2009 11.26.24 : SERVER-5.70-0 [nmID=6001D]
Cache memory allocator out of available memory.


6.06.2009 11.26.24 : SERVER-5.70-0 [nmID=2000A]
Short term memory allocator is out of memory.
2 attempts to get more memory failed.
request size in bytes 26214408 from Module RTVSCAN.NLM


6.06.2009 14.00.22 : SERVER-5.70-0 [nmID=6001D]
Cache memory allocator out of available memory.


6.06.2009 14.00.22 : SERVER-5.70-0 [nmID=2000A]
Short term memory allocator is out of memory.
31 attempts to get more memory failed.
request size in bytes 26214408 from Module RTVSCAN.NLM

Loading Module DSMC.NLM [ OK ]



segstat shows not much different allocation of RTVSCAN.NLM taking a snap
at Server uptime : 1d 13h 11m 46s
5. RTVSCAN.NLM 10.01.06 29 Nov 2007 84,980,592 bytes (81.0 MB)
and Server uptime : 16d 00h 56m 19s
5. RTVSCAN.NLM 10.01.06 29 Nov 2007 90,030,960 bytes (85.9 MB)

the Top 20 Memory Consuming NLMs are nearly constant too :

NLM Name Version Date Total NLM Memory
=================================================================================
1. DS.NLM 20217.06 4 Nov 2008 643,568,183 bytes (613.8 MB)
2. NSS.NLM 3.27 13 Nov 2008 205,745,232 bytes (196.2 MB)
3. SERVER.NLM 5.70.08 3 Oct 2008 141,257,888 bytes (134.7 MB)
4. GWPOA.NLM 7.00.03 8 Mar 2008 130,549,441 bytes (124.5 MB)
5. RTVSCAN.NLM 10.01.06 29 Nov 2007 84,980,592 bytes (81.0 MB)
6. NWPA.NLM 3.21.02 29 Oct 2008 19,019,486 bytes (18.1 MB)

=================================================================================
1. DS.NLM 20217.06 4 Nov 2008 605,819,447 bytes (577.8 MB)
2. NSS.NLM 3.27 13 Nov 2008 250,588,240 bytes (239.0 MB)
3. SERVER.NLM 5.70.08 3 Oct 2008 185,647,008 bytes (177.0 MB)
4. GWPOA.NLM 7.00.03 8 Mar 2008 120,927,937 bytes (115.3 MB)
5. RTVSCAN.NLM 10.01.06 29 Nov 2007 90,030,960 bytes (85.9 MB)
6. GWPOA.NLM 7.00.03 8 Mar 2008 52,401,857 bytes (50.0 MB)


the fragmentation after 1d 13h 11m 46s :

Logical Memory Summary Information
=================================================================================

File System Cache Information
FS Cache Free : 105,824,256 bytes (100.9 MB)
FS Cache Fragmented : 9,801,728 bytes (9.3 MB)
FS Cache Largest Segment : 39,960,576 bytes (38.1 MB)

Logical System Cache Information
LS Cache Free : 700,690,432 bytes (668.2 MB)
LS Cache Fragmented : 282,361,856 bytes (269.3 MB)
LS OS Reserved Data : 333,455,360 bytes (318.0 MB)
LS Cache Largest Segment : 62,464,000 bytes (59.6 MB)
LS Cache Largest Position : 65845000

Summary Statistics
Total Address Space : 4,294,967,296 bytes (4.00 GB)
Total Free : 806,514,688 bytes (769.2 MB)
Total Fragmented : 292,163,584 bytes (278.6 MB)
Highest Physical Address : F1FF9000
User Space : 884,998,144 bytes (844.0 MB)
User Space (High Water Mark) : 566,394,880 bytes (540.2 MB)
NLM Memory (High Water Mark) : 1,588,432,896 bytes (1.48 GB)
Kernel Address Space In Use : 2,076,033,024 bytes (1.93 GB)
Available Kernel Address Space : 861,417,472 bytes (821.5 MB)

and after 16d 00h 56m 19s :

Logical Memory Summary Information
=================================================================================

File System Cache Information
FS Cache Free : 83,210,240 bytes (79.4 MB)
FS Cache Fragmented : 45,498,368 bytes (43.4 MB)
FS Cache Largest Segment : 31,457,280 bytes (30.0 MB)

Logical System Cache Information
LS Cache Free : 267,558,912 bytes (255.2 MB)
LS Cache Fragmented : 498,110,464 bytes (475.0 MB)
LS OS Reserved Data : 333,455,360 bytes (318.0 MB)
LS Cache Largest Segment : 42,385,408 bytes (40.4 MB)
LS Cache Largest Position : BDF94000

Summary Statistics
Total Address Space : 4,294,967,296 bytes (4.00 GB)
Total Free : 350,769,152 bytes (334.5 MB)
Total Fragmented : 543,608,832 bytes (518.4 MB)
Highest Physical Address : CFE55000
User Space : 884,998,144 bytes (844.0 MB)
User Space (High Water Mark) : 576,348,160 bytes (549.6 MB)
NLM Memory (High Water Mark) : 1,852,006,400 bytes (1.72 GB)
Kernel Address Space In Use : 2,262,065,152 bytes (2.11 GB)
Available Kernel Address Space : 423,940,096 bytes (404.3 MB)


are these stats for fragmentation to high ?
the largest segments seem to be big enough for the request of RTVSCAN and
AFAIK it is the actual version.
Labels (2)
0 Likes
5 Replies
ataubman Absent Member.
Absent Member.

Re: memory allocator problem

request size in bytes 26214408 from Module RTVSCAN.NLM

This is a clear bug in RTVSCAN. A single request for 26mb of contiguous memory is unreasonable, requests should be much smaller than this. The version you have is Nov 2007, so check for updates to that.

Please download fconfig17.zip from the file finder at support.novell.com. Extract Config.nlm from it and copy that to SYS:SYSTEM .

On the console do LOAD CONFIG /jumba1se, and wait until the output file CONFIG.TXT gets created (on NW 6.x this message only appears on the Logger screen). Please post that file here, with any public IP addresses and RConsole passwords edited out. Thank you.

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: memory allocator problem

Here the config.txt :

http://www.hsinet.de/support/maxx/config.txt




On 18.06.2009 02:06, ataubman wrote:
>> request size in bytes 26214408 from Module RTVSCAN.NLM

> This is a clear bug in RTVSCAN. A single request for 26mb of contiguous
> memory is unreasonable, requests should be much smaller than this. The
> version you have is Nov 2007, so check for updates to that.
>
> Please download fconfig17.zip from the file finder at
> support.novell.com. Extract Config.nlm from it and copy that to
> SYS:SYSTEM .
>
> On the console do LOAD CONFIG /jumba1se, and wait until the output file
> CONFIG.TXT gets created (on NW 6.x this message only appears on the
> Logger screen). Please post that file here, with any public IP addresses
> and RConsole passwords edited out. Thank you.
>
>


0 Likes
ataubman Absent Member.
Absent Member.

Re: memory allocator problem

OK, I don't see any real configuration problems there. You should definitely check with HP for updated bios and CPQ drivers and utilities, as they are all old, but that's nothing to do with this current problem.

Once you have updated rtvscan, set File Cache Maximum Size = 2147483650

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
dcsph Absent Member.
Absent Member.

Re: memory allocator problem

I too am having a memory allocator issue. Am running a 6.5 sp3 server that gives me the following:
"cache memory allocator out of available memory".
I have attached the segstats file. This is just used as a file server.
0 Likes
jgray Absent Member.
Absent Member.

Re: memory allocator problem

I would get off of SP3 as soon as I could. That SP had a lot of issues with memory. I would update to SP8.

jgray
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.