topic Re: diaglogd_activity_log in Operating System - HP-UX

diaglogd_activity_log

Steven Burgess — Thu, 08 Nov 2001 20:13:17 GMT

Urgent

does anyone know what writes to the following
log

/var/stm/logs/sys/diaglogd_activity_log

it's currently filling up the /var directory in one of our servers

I have tried to fuser diaglogd_activity_log
but no process details are returned

Re: diaglogd_activity_log

G. Vrijhoeven — Thu, 08 Nov 2001 20:16:23 GMT

Hi,

Try man dialogd.

Gideon

Re: diaglogd_activity_log

Deshpande Prashant — Thu, 08 Nov 2001 20:29:05 GMT

Hi
Are you running online diag older version (I think
Thanks.
Prashant.

Re: diaglogd_activity_log

harry d brown jr — Thu, 08 Nov 2001 20:29:39 GMT

It's filling up for a reason, and probably not a good one. You need to review these logs!

gointo stm

select logtool

view the log, especially for errors.

live free or die

Re: diaglogd_activity_log

Sanjay_6 — Thu, 08 Nov 2001 20:35:11 GMT

The file is generated by diagmond which is the STM tool manager daemon. Do a man diagmond for more info. This file should not be big, The actual activity of diagmond is written to activity_log in that directory. Are you getting a lot of messages from diagmond / EMS.

Hope this helps.

Regds

Re: diaglogd_activity_log

Steven Burgess — Thu, 08 Nov 2001 20:38:47 GMT

The log is growing at an alarming rate. I have /sbin/init.d/diagnostic stop, for the moment. Also getting alarms for filesystems not mounted when they actually are

Re: diaglogd_activity_log

Steven Burgess — Thu, 08 Nov 2001 21:30:05 GMT

I have attempted to diagnose the activity log , it is that large the stm tool is unable to do anything with it. If i stop the dameon so the log doesn't grow you cannot diagnose it.

If i string the log the entries in there are

/dev/diag2
A.03.00
diaglogd
18x01 # on nw844_1

Has anyone any answers

Re: diaglogd_activity_log

Roger Baptiste — Thu, 08 Nov 2001 21:41:57 GMT

Hi,

The key issue here is there is a problem
with your system which is making diaglogd
spew all those messages. Shut diaglogd for
the moment and see where the problem is.

For filesystem related errors ->
do a #mount to see whether all the mount
points (as reflected in mnttab) is accessible.

Look at /var/adm/syslog/syslog.log file
because critical messages get recorded in this
file too.

Do a dmesg and look for console message.
do dmesg - (minus sign) again to see
whether there are any new messages being
displayed on your console.

HTH
raj