• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 339
  • Last Modified:

Memory issues in an old Netware 6 SBS server

I've got an old Compaq Proliant server which has recently started running out of memory. The machine is currently hosting NDPS and my Zenworks database, neither of which is used much. After being up for several days, eventually I start getting out of memory errors until I reboot.

Here's a typical message.
 5-02-2005   4:59:39 pm:    SERVER-5.60-0
   Severity = 5  Locus = 1  Class = 1
   Short term memory allocator is out of memory.
733 attempts to get more memory failed.
request size in bytes 86016 from Module NWPA.NLM

The module is always NWPA.NLM, I don't know if that's significant.

The machine currently has 256 megs of RAM. The problem is, I can't add more memory. It takes these really weird proprietary Compaq EDO sticks that look like 168-pin DIMMs, but are actually slightly different, and I have not been able to find them bigger than 64 megs, and if I did find them they'd probably cost a fortune.  

Anyway, until I can get a new machine, I'm trying to find ways to make more memory available on this one. I've been unloading DOS, but what other kinds of things can I do to increase available memory?

0
billmercer
Asked:
billmercer
  • 7
  • 4
  • 3
  • +1
3 Solutions
 
ShineOnCommented:
That kinda sounds like the NSS memory fragmentation issue.  Have you looked into that?  What SP is this server on?  Any post-SP patches?  Did this start after upgrading DS to eDirectory 8.7.3?
0
 
billmercerAuthor Commented:
Yes, it did start after the edir upgrade. Server is on SP5, with post-Sp5 patches for SLP and TCP, no others.

Is this TID what you're referring to?
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10091980.htm
0
 
PsiCopCommented:
Yes, that TID is the NSS Cache fragmentation issue that ShineOn mentioned. We addressed it, in our environment, using Step 5 of that TID, which we found effective. Altho I'm not convinced that the NSS Cache fragmentation is the culprit, because I seem to recall that the error message was different.
0
How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

 
ShineOnCommented:
Psi, it may have been different 'cause you weren't working on a server with 256 MB RAM. ;)  The TID mentions Short Term Memory Allocation errors as one of the possible symptoms...

Yes, bill, that's the TID.
0
 
ShineOnCommented:
Have you been watching what's going on with memory using NoRM?  Does this server have enuf memory to run NoRM along with NDPS and Zen inventory? Have you applied the NSS patch the TID mentions already?
0
 
billmercerAuthor Commented:
I've not tried installing remote manager on this machine, mostly because I was concerned about the memory and performance. We've just applied the suggestions from the TID, but it will probably be a while before we know the results. It usually takes several days to a week before we start seeing errors.

0
 
pgm554Commented:
After you applied the new Spack,did you reapply the Compaq one?
ALWAY defer to the Compaq Spacks over the Novell Spacks when it comes to hardware and drivers.
There is the possibility that the new NWPA and the Compaq HW drivers are having issues.
So, whatever the last Spack from Compaq is for that box, reapply it, and overwrite any chamges the Novell one made.
Make sure all the BIOS are flashed and uptodate.

I learned that one the hard way.

As for memory 256 is the minium,so what what is the model number ,I might have some 128 mb Compaq server memry laying around(unused)in the original unopened boxes.

0
 
billmercerAuthor Commented:
The bios is up-to-date.
There is a recent support pack for Proliants which I have not installed. If the TID ShineOn doesn't resolve the problem, I will give your suggestion a try next. I don't like to try two things at once, so I can know when I've really found the solution.  

The memory in question is 168 pin 60ns EDO DIMMs, used in the oldest Proliant 3000s. Near as I can tell, this memory was only used with the 300 and 333 MHz P2 Proliants. Currently I have four 64MB DIMMs, and no free slots, so I'd need to replace all four. (The server originally came with 128 MB, I added the 2nd 128 a few years ago)



0
 
pgm554Commented:
I have a kit of 2 x 128 EDO buffered (registered) for the Proliants around some where in storage from a customer that stiffed me a few years ago . If I find them, I'll post to this question and if you are interested,we can make arrangements.
I think max on those boxes is like 512 mb.
0
 
billmercerAuthor Commented:
Well, applying the TID did not resolve the problem, the errors came back after a week or so. I'm now applying the Compaq updater, to see if it helps.

0
 
PsiCopCommented:
pgm554 - got any of that in SDRAM?
0
 
pgm554Commented:
I am on the road for the next month and won't be able to get to it until June 20th or so.
When I get back I will post .
0
 
PsiCopCommented:
Thanks. I got an old ProLiant 3000 that I'm having the very devil of a time trying to fit with more RAM. Everyone has EDO for it, but I've got SDRAM in it now.
0
 
billmercerAuthor Commented:
I applied the Compaq update, but it basically said I didn't need anything. The only things it actually installed were some HP management stuff that I have no use for. Apparently my drivers, etc are already up-to-date.


I do know of a supplier for the EDO DIMMs, btw, they're available from www.memoryx.com.

0
 
pgm554Commented:
It not so much as what is up to date ,but what has been tested and supported (the art of the back rev).
0
 
billmercerAuthor Commented:
At this point nothing else has worked, so I'm going to buy more memory and see what happens.
0
 
billmercerAuthor Commented:
Okies, I've now got a whopping, maxed out 512 megs in this bad boy, and so far it's looking pretty good. If it does choke again, I'll probably just reboot it again or something, thanks for all suggestions.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 7
  • 4
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now