Monitor - kernel - threads, and
NRM - profile/debug - Profile CPU execution by NLM
to see what is causing the high util.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)
Opinions expressed above are not
necessarily those of Novell Inc.
the top two threads are always "server" with interrupt counts in the
millions and all others in the thousands
I used debugging and profiling in the web portal (this is nw51 sp2a).
It shows AIOCOMX using almost all the cpu time.
The very first thing I tried was to unload pwrchute, aio, and aiocomx
but the cpu spikes continued.
i have a cputrace utility. with the pwrchute nlm's unloaded, whenever
cputrace shows a cpu spike, the nlm than was running is ds.nlm .
BTW is this causing you any actual operational problem?
I suggest you apply nw51sp8 and nw51os8a. If and only if the spikes
continue, please download fconfig15.exe from the file finder at
support.novell.com. Extract Config.nlm from it and copy that to SYS:SYSTEM .
On the console do LOAD CONFIG /jumba1se, and wait until the output file
CONFIG.TXT gets created (on NW 6.x this message only appears on the
Logger screen). Please post that file here, with any public IP addresses
and RConsole passwords edited out. Thank you.
On Jan 22, 5:07 pm, Andrew C Taubman
<ataubman.RemoveThisToMai...@novell.AndThis.com> wrote:
> So it could simply be a DS sync?
there are three servers in the tree. only one is spiking.
> BTW is this causing you any actual operational problem?
something is making the backups slower. that's how i noticed the
problem in the first place.