NWPA.NLM 2

[dsimpaired]

Using Veritas Backup and getting the following message


"Short term memory allocator is out of memory

XX attempts to get more memory failed.

Request size in bytes 524288 from module nwpa.nlm"



Just popped up on servers that have been stable for a while, not sure what this means but has anyone else ever had this???

 

[LawnBoy]

If you're on SP4 or earlier, TSAFS could be eating up your memory. You can check it with the Remote Manager under Manage Applications -> List Modules. Mine is consuming < 1MB total.

SP4b and up seem to have solved the memory leak.

 

[marvhuffaker]

There's a TID about tweaking memory to prevent that from happening.. Lookup "Memory Fragmentation on NetWare 6.5".. BackupExec provokes a lot of the problems. If you haven't already followed that TID, that would be the first step.

Note that the TSAFS /CACHEMEMORYTHRESHOLD=1 AND setting DS to a hardset amount of memory have been the biggest help in resolving these issues.

Also like Lawnboy said, SP3 & SP4 were very prone to leaks.

Marvin Huffaker, MCNE

http://www.redjuju.com

See me speak at GWAVACON Jan 21-23 in Dallas.

http://www.redjuju.com/company/events.htm

 

[dsimpaired]

Sorry for the delay, had other fires to put out. I appreciate the info and I am currently checking it out. The other thing I noticed was that DS was at 400+ Mb utilization. Checking service pack version and reading tids, thanks, will update when I find out.

 

[marvhuffaker]

Sounds like DS is eating up your ram. Set that hard in iMonitor and it should resolve a lot of those DS related memory issues.

 

[marvhuffaker]

To clarify even further... Even in a reasonable sized network, the DS database might be 30-40MB in total size (dib size).

The recommendation is to hardcode DS to consume as much ram as the DIB size x 2. So say DIB size is 20MB... Give DS 40MB to work with. This gives it room to grow but keeps it from getting out of control.

So to see that you have a 400MB Memory -- it's clearly out of control and setting it to a fixed amount would make a very significant difference for your server.

That TID I referenced shows you where to hard set that RAM limit as well as find the size of your DS database. It's basically on the same page in iMonitor.

 

[dsimpaired]

Thanks I will check that out and yes we are at SP3. I downloaded 5 & 6 but a little scared of going to sp6 at the moment, would 5 be sufficient? Also, I will set the hard limits before I do anything and let it settle down before adding service pack.

 

[dsimpaired]

OK, we went ahead and updated to sp5 last night and all the servers are under 5% utilization now during slow times so it looks promising. After the update I downed and then during bootup 3 out of nine froze and I had to hard boot and after a couple of nervous minutes all nine were back online and looking good. Thanks for the input and help!