diaglogd_activity_log

[Steven Burgess]

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

[G. Vrijhoeven]

Hi,

Try man dialogd.

Gideon

[Deshpande Prashant]

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

[harry d brown jr]

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

[Sanjay_6]

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

[Steven Burgess]

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

[Steven Burgess]

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

[Roger Baptiste]

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