aanthonisse2 Absent Member.
Absent Member.
1274 views

Memory problem

Hi,

One of our clients runs a Netware 6.5 SP8 server with 2GB of memory. For several weeks now, the server loses memory all the time, resulting in necessary reboots about every 3-4 days.

GWPOA is loaded in protected memory space, I don't know if that consumes a lot of extra RAM?

The NLM's eating most memory are NSS. DS and GWPOA. See the screen shot of SEG for the delta after 48 hours.

Is there some way to reduce the memory hunger of NSS or GWPOA?

Kind regards, Arjan
Labels (2)
0 Likes
8 Replies
jgray Absent Member.
Absent Member.

Re: Memory problem

Arjan,

Attach a segstats.txt. I would like to take a look at it.

After a reboot, if you type at the console, set file cache maxamum size, and then hit enter. What is the number in yellow that is returned.

jgray
0 Likes
Knowledge Partner
Knowledge Partner

Re: Memory problem

Hi,

aanthonisse wrote:
>
> Hi,
>
> One of our clients runs a Netware 6.5 SP8 server with 2GB of memory.
> For several weeks now, the server loses memory all the time, resulting
> in necessary reboots about every 3-4 days.


Why does this result in necessary reboots? Error messages?

> GWPOA is loaded in protected memory space, I don't know if that
> consumes a lot of extra RAM?


No.

> The NLM's eating most memory are NSS. DS and GWPOA. See the screen shot
> of SEG for the delta after 48 hours.


There is nothing to see there. The memory usage of all these nlms is
completely harmless, and in case of NSS, *will* rise to about 200MB over
the course of the next few days, which is completely normal. What
exactly is the problem?

> Is there some way to reduce the memory hunger of NSS or GWPOA?


There is no such thing. Your numbers in your screenshot are perfectly
fine.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
aanthonisse2 Absent Member.
Absent Member.

Re: Memory problem

jgray;1818437 wrote:
Arjan,

Attach a segstats.txt. I would like to take a look at it.

After a reboot, if you type at the console, set file cache maxamum size, and then hit enter. What is the number in yellow that is returned.

jgray


Hello JGRAY,

Attached is a segstats.txt.
IMHO as the server has only 2GB of memory, there is not much tuning that has to or can be done.

Kind regards, Arjan
0 Likes
aanthonisse2 Absent Member.
Absent Member.

Re: Memory problem

mrosen;1819053 wrote:
Hi,

aanthonisse wrote:
>
> Hi,
>
> One of our clients runs a Netware 6.5 SP8 server with 2GB of memory.
> For several weeks now, the server loses memory all the time, resulting
> in necessary reboots about every 3-4 days.


Why does this result in necessary reboots? Error messages?
The users experience problems logging in, especially when using LDAP logins. Since cachebuffers are very low then, I think that is related.


> GWPOA is loaded in protected memory space, I don't know if that
> consumes a lot of extra RAM?


No.

> The NLM's eating most memory are NSS. DS and GWPOA. See the screen shot
> of SEG for the delta after 48 hours.


There is nothing to see there. The memory usage of all these nlms is
completely harmless, and in case of NSS, *will* rise to about 200MB over
the course of the next few days, which is completely normal. What
exactly is the problem?

> Is there some way to reduce the memory hunger of NSS or GWPOA?


There is no such thing. Your numbers in your screenshot are perfectly
fine.

I thought so.
CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
Untitled Document

Kind regards, Arjan
0 Likes
Highlighted
aanthonisse2 Absent Member.
Absent Member.

Re: Memory problem

File Cache Maximum Size: 1073741825, almost the lowest value possible

Kind regards, Arjan
0 Likes
Knowledge Partner
Knowledge Partner

Re: Memory problem

Hi,

aanthonisse wrote:
> >
> > Why does this result in necessary reboots? Error messages?
> > The users experience problems logging in, especially when using LDAP
> > logins. Since cachebuffers are very low then, I think that is related.


Doubt it. Define "very low"?

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Knowledge Partner
Knowledge Partner

Re: Memory problem

Hi,

aanthonisse wrote:
>
> Attached is a segstats.txt.
> IMHO as the server has only 2GB of memory, there is not much tuning
> that has to or can be done.
>
> +----------------------------------------------------------------------+
> |Filename: SEGSTATS.TXT |
> |Download: http://forums.novell.com/attachment.php?attachmentid=3057 |
> +----------------------------------------------------------------------+


That's a completely different picture (and doesn't match your original
screenshot in any way). That server is severely abused.

1. Server.exe should not use +200MB of memory, unless you still have TFS
volumes on that box. Do you? At any rate, tat server is massively tuned
towards TFS volumes. Is that on purpose?

2. You're running two instances of sybase SQL in different versions on
that box. What's up with that?

3. NSS is completely crippled, by hard setting it's allowed memory. No
wonder the cache buffers on that server are low. Get rid of that totally
nasty c:\nwserver\nssstart.cfg

We need to know details about the volume setup on that server. If it
only has NSS volumes as it should, you should:

1. Use NRM to reset *all* set parameters to default.

2. Delete c:\nwserver\nssstart.cfg

3. Make sure you set NSS /cachebalance=85

4. Find out why you're runnign two instances of sybase SQL, and get rid
of one.

5. Last but not least, kill whoever has done that sort of "tuning" to
the poor server. <scnr>

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
aanthonisse2 Absent Member.
Absent Member.

Re: Memory problem

mrosen;1819242 wrote:
Hi,

aanthonisse wrote:
>
> Attached is a segstats.txt.
> IMHO as the server has only 2GB of memory, there is not much tuning
> that has to or can be done.
>
> +----------------------------------------------------------------------+
> |Filename: SEGSTATS.TXT |
> |Download: http://forums.novell.com/attachment.php?attachmentid=3057 |
> +----------------------------------------------------------------------+


That's a completely different picture (and doesn't match your original
screenshot in any way). That server is severely abused.

1. Server.exe should not use +200MB of memory, unless you still have TFS
volumes on that box. Do you? At any rate, tat server is massively tuned
towards TFS volumes. Is that on purpose?


2. You're running two instances of sybase SQL in different versions on
that box. What's up with that?

3. NSS is completely crippled, by hard setting it's allowed memory. No
wonder the cache buffers on that server are low. Get rid of that totally
nasty c:\nwserver\nssstart.cfg


We need to know details about the volume setup on that server. If it
only has NSS volumes as it should, you should:

1. Use NRM to reset *all* set parameters to default.
2. Delete c:\nwserver\nssstart.cfg
3. Make sure you set NSS /cachebalance=85
4. Find out why you're runnign two instances of sybase SQL, and get rid
of one.
5. Last but not least, kill whoever has done that sort of "tuning" to
the poor server. <scnr>

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
Untitled Document



This is correct, there are two different applications on the server (ZENWorks and Planon) that require seperate Sybase versions.

The c:\autoexec.bat contain had a command to start the server with -u
SERVER -u691000000 -nl
I removed -u691000000.

Contents of c:\nwserver\nssstart.cfg were:
/nocachebalance
/minbuffercachesize=44300
I removed it.

I let you know if this helps.

Kind regards, Arjan
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.