diaglogd running at 100%

[Joe White]

I have an N class running hpux 11.0. For some reason the diaglogd daemon is running at 100%. Anybody have any ideas on why this is happening?

[harry d brown jr]

You might be experiencing excessive IO errors causing diaglogd to spin out of control.

[Tim D Fulford]

I'm pritty sure there are patches for this. You usually see cclogd at 100%, Try PHSS_20007 + dependants (if not already installed)

I would fix it (temporarily) by stopping & starting disgnostics

# /sbin/init.d/diagnostic stop
# /sbin/init.d/diagnostic start

Tim

[Paula J Frazer-Campbell]

Hi Joe

First fix - Stop and restart diaglogd.

diaglogd is launched automatically at boot by the STM daemon diagmond.
The STM User Interface, xstm , mstm , or cstm , Daemon commands can
also be used to launch the daemon as well as shut it down and view the
daemon's activity log.
HTH

Paula

[Joe White]

Thanks for the replies. We tried executing a /sbin/init.d/diagnostics stop/start but got errors as if something was missing in the startup script. We haven't had time to research the scripts. Has anyone tried a kill or kill -9 on dialogd without adversely affecting anything?

[Mark Graham]

Joe,

Check your root mail - if EMS is running, many messages will be sent to root's mail. Those messages will show the subsystem that might be casuing you stress.

Also, no messages in /var/adm/syslog/syslog.log to clue you as to why?

Hope this helps.

Mark Graham

[Insu Kim]

This is a known issue and you can fix it by updating the latest version of STM.
Get it at www.software.hp.com.

Hope this helps,

[Denver Osborn · Accepted solution]

Did you type /sbin/init.d/diagnostic and not diagnostics

This is how it could be stopped
# /sbin/init.d/diagnostic stop

You might also have noticed a large file growing, /var/stm/data/diaglogd_hold_list. After stopping diagnostics you can rename or remove this.

As others have said this is a known issue. It hink it occurs with STM from Dec 99 and maybe one after. Surest fix would be to update to the latest version of diagnostics.

You can download the latest release (Sept 2001) here:

http://software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=B6191AAE

Hope this helps
-denver

[Insu Kim]

When it comes to "kill",

If you use 'kill -9' to kill diagmond, you will not be able to restart it. This is because it was not able to release its socket port when it was killed and the port is therefore not available. If you need to kill the diagnostic daemon, use 'kill -2' or use the function File->Administration->STM Shutdown.

Hope this helps

[Juan Manuel López]

You have to install the patch 24044.
Juanma

[AlHassani Mohamed]

Hi
That is a known problem with the diagnostic version A.25.00 (March 2001) . These problem was fixed with the diagnostic version A.26.00 (June 2001).
You must installing the Version June01. You can do this online.
by

[Juan Manuel López]

Could you please give us points ?
Thanks.

[Deshpande Prashant]

Hi
I had seen this on one of my machine with Diag of Sept 2000. I upgraded to March 2001 (advised by HP) to fix this.

So upgrade you diagnostics (>= March01 )and apply latest patches to fix your problem.
Don't forget to shutdown diagnostics and MWA before upgrading it.

Thanks.
Prashant Deshpande.