Novell is now a part of Micro Focus

NetWare 6 Only Shows 35% Free Memory

Articles and Tips: qna

01 Apr 2002


Q.

I am working with NetWare 6. I have discovered that whatever the amount of memory I put in my server, it always shows 35% free memory (even with 1, 2, or 4 GB of server memory). This occurs when I am running Netstorage, iFolder and iPrint. Then there is no way to use ZENworks for Desktops 3 or anything else due to the memory problems.

Novell Storage System's (NSS) cache balance has been changed from 60% to 10%, but there is no change in memory usage. Is this a bug? Or are there some particular parameters to change in web access parameters or another current program?

Memory Madness in Molokai

A.

Dear Madness: Go into the NetWare Remote Manager utility and click on the List Modules option. This will tell you what is taking up the most RAM. I would guess that NSS is taking up a lot (and you can normally turn this down).

By default, the Java Virtual Machine (JVM) will only take up to 64 MB. Also, eDirectory could be taking up a lot of RAM. NetStorage and iFolder use Apache, so you may want to look at the NVXADMUP.NCF file and modify it so that you restrict the memory used by Java. You do this by using the following switches on the load Java command line:

-XMS aa M -XMX bb M

Where: " aa " is the minimum memory limit and " bb " is the maximum memory limit.

For example: -XMS96M -XMX192M sets Java to use a minimum memory allocation of 96MB and a maximum of 192MB.

Put these commands on the load line before any references are made to "com.", etc. Hopefully this helps.

I would suggest that you use the Remote Manager utility to look at the memory that is being allocated in real-time. You could have a memory leak caused by a bad driver or something like that. As for iPrint, this is hosted by HTTPSTK. I do not know if you can tune HTTPSTK. You may need to contact Novell Technical Support on this one. Of course you do have NDPS running in the background as well, so you might want to check how much memory it is using.

* Originally published in Novell AppNotes


Disclaimer

The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.

© Copyright Micro Focus or one of its affiliates