5 replies
by acurrin
A couple things to look at:
Are there any new NLMs running on the server? Anti-virus? GroupWise? CD-ROM software? If so, look into the memory that each NLM is using, note it and then look at each the next day and see if one is climbing.
Also, look at the volume space on all the volumes, if space is low, use of files that are compressed will cause them to be decompressed, but the OS will have to work real hard to manage the files in the minimal free space. Run a purge on the volumes to reduce directory entries that may be eating up RAM and clear up space.
by bobrace
by jaolson40
Also, maybe run a DSREPAIR. I once had a situation exactly like the one you're describing, where I would run out of available memory within a couple of days. Checking the memory stats in MONITOR showed that DS.NLM had the bulk of the RAM, and apparently errors in the NDS database was causing the server to allocate more and more memory to the process. A DSREAPIR fixed it.
Certainly check the memory stats in MONITOR, tho. One glance when memory is low will usually show you the offending NLM orprocess and give you a starting point.
by bobrace
by bobrace
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending