Server.nlm causes cpu to run up

I have noticed this problem on two different servers that we have.  It appears that the server.nlm run the CPU up to 75% utilization and holds there.  During this time the logins screech to a halt.  I fixed the problem last time by simply setting up a new server, however this is impossible to do now.  I have compression turned on on this server and I feel like it might have something to do with that.  I appreciate any help you guys could give me.

LVL 1
ddano2000Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ShineOnCommented:
We'd love to help, but you have to help us help you and give us information about your environment.

NetWare version and SP
Volume types
Additional software running on server (antivirus, backup, database, NDPS, Bordermanager, GroupWise, ZENworks, etc.)
Protocol(s) in use
Client mix and access type (Novell client/ver/sp, MS client, native access, MAC, prosoft, etc)
Server hardware configuration (processor class/speed, number of processors, memory, etc)

There may be more questions after that.
0
blcarter14Commented:
Are you running Symantec AV? If so turn it off.  As ShineOn stated, a little more info about your box is needed.  
0
ddano2000Author Commented:
Sorry about that guys, here is the info.  I'm running Netware 6.5 SP2 with Symantec and Veritas Backup client ( I did disable these to see if it would solve the problem...it didn't).  The workstations are Novell Client 4.9 SP2+D with no MS Client installed.  The Server is a Dell Poweredge 2500 PIII 933 single processor with 1 GB of RAM.

Heres another, perhaps interesting twist, when I rebooted the Server it initially had 48% of it's memory being utilized.  Over the course of the day, This has decreased to 28% although the user's logged in has not changed.  Don't know if that helps or not, but I thought I would throw that in.
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

blcarter14Commented:
Are your running netstorage? I would load the latest support pack (sp5) as a first step measure.  This cleans up several problems including a java memory leak and netstorage causing high utilization.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ddano2000Author Commented:
Does SP5 cause any problems if I don't patch my other Novell servers right away?
0
blcarter14Commented:
What version of Netware on you running on them?  As long as they are 6 or 6.5 you should not have any problems.  
0
blcarter14Commented:
This TID will give you some info on the support pack and requirements: TID2973048

It includes:
Support Pack Installation
 Preinstallation Checklist
Installing the Support Pack through NWCONFIG
Uninstalling the Support Pack

As long as you use the backup option during the install, you can roll the changes back if you have problems.
0
ShineOnCommented:
NetWare 6.5 SP2 had all sorts of issues.  I second the recommendation of blcarter14 to install SP5.

If SP5 updates eDirectory, and I think it does, you should apply it to the Master of [Root] - and maybe you should do that one first anyway.  All of your servers should, ideally, be at the same SP level with the same eDirectory version/SP/IR, but it's impossible to update all servers at once in most cases (unless you have ZEN for Servers.)

Memory leaks were one of the problems with the SP2 revision level, especially as regards eDirectory and NSS.  There are some TIDs floating around on that problem and they include workarounds but primarily say you should update to the latest support pack.
0
blcarter14Commented:
So no with OES Linux?
0
blcarter14Commented:
Ignore my OES comment, wrong forum.
0
ddano2000Author Commented:
Ok I've done the SP5 upgrade, to the root server and to the server in question here.  Now I have a new problem, in the the available memory is flagged as a health problem.  It's saying I only have 385MB of memory available when I really have 2GB.  Any ideas?
0
ShineOnCommented:
Is this all-NSS or do you have any traditional FAT (NWFS) volumes?

Are any applications loading in their own address spaces?

What kind of applications are running?  Anything besides AV and backup?
0
blcarter14Commented:
Check out this link.  It includes some general troubleshooting steps as well.  

http://www.novell.com/documentation/nw65/index.html?page=/documentation/nw65/sos__enu/data/hijriurj.html
0
DSPooleCommented:
Hit the Dell download site and download any Dell-specific Novell NetWare 6.5-related updates for the OS including the latest PSM module and drivers.
0
ddano2000Author Commented:
Well guys, it didn't help to apply the service pack.  Seems as though the CPU hang issue is not as bad, however logins are still slow.  I am running an all nss system.  Not quite sure how to tell if any applications are loading in there own address space, and the only apps running are monitor, symantec av, and I turned off the backup exec.  Not really sure where to go from here.  i took over this network about a year ago and have no idea how convoluted it is.  Could the slow logins be caused by our zenworks server?  Or some other server in the network?  Perhaps our edirectory is screwed up, I'm just not quite sure how it all fits together.  I'm sorry I such an idiot about Novell.  I'm trying to learn the OS but it is tough.  Thank you for all of your help.
0
ShineOnCommented:
Are logins generally slow?  I understood from your Question that logins slowed during the high CPU periods (and by the way, 75% CPU isn't really all that high - I've seen NetWare running at 90% CPU without a burp).  

If they're generally slow, then the next question I have for you is, do you use any NMAS login methods, like Universal Password for example?  If not, then you should disable NMAS Authentication on the client - in fact, if you don't use NMAS at all, you should uninstall NMAS from the workstation too.

The NMAS Authentication is disabled on the Novell Client Properties page, Advanced Login tab.  Look for "NMAS Authentication" and set it to "No."  Then, go into add/remove programs and uninstall Novell Modular Authentication Services (NMAS) or however it shows up there.  On future installs of the Novell Client, be sure to unselect NMAS from the install.  

You DID install the client using "custom" and not "typical" - right?

Also, there are post-SP2-post-"D" patches for NWFS and SERVLOC that you should apply to the client, too.
0
ddano2000Author Commented:
Well it seems as though the service pack did fix the issue.  i also went in an optimized the memory and so far so good.  Thanks for all of your help.  Just to answer the previous post, we don't install nmas or nici onto our client boxes as they seem to cause a lot of problems.  We can continue to discuss this and I can give you guys anymore information you might want but for now it seems to have "disappeared".
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Novell Netware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.