activity_log is too big under /var/stm/logs/sys

[Mohammad Kaleem]

Hi,

activity_log under /var/stm/logs/sys directory is too big, caused 100% /var filesystem full.

Can I just remove this file or I have to stop/start any proccess?

Regards,
MKaleem

[MarkSyder]

Null the file.

> /var/stm/logs/sys/filename will remove the contents of the file without deleting the file.

Mark Syder (like the drink but spelt different)

[G. Vrijhoeven]

Hi

I think you need to check your hardware with stm ( errorlog)
There must be a reason for the system to be logging link this.

Gideon

[Zeev Schultz]

Hi

Usually stm's activity log records internal messages/events (like stm daemons are up etc).
I don't beleive its size has to do with hardware problems.It could be old stm version (check with swlist -l bundle | grep -i online),
lack of stm patches or some internal issue.

A simple workaround was suggested to null. But
I'd stop diagnostics (/sbin/init.d/diagnostics stop), go to that dir , move the file to file.OLD, start diagnostics.

One more , you can see what kind of messages are filling activity_log. Run (command line):
echo "sal" | cstm .

Zeev

[MarkSyder]

Hi Zeev,

If he moves the file to file.OLD won't he still have the problem of /var being 100% full?

Mark Syder (like the drink but spelt different)

[Bruno Ganino]

See my attachment

HTH
Bruno

[Marco Santerre]

Though I agree that nulling the file is one work-around, I'd also stop the dignostics.

That being said, I would certainly look at my hardware to see if there is anything wrong at all. I went through the same problem last week, and found out I had one of my controllers on my Auto-Raid failing on me. So, if possible try to read your log first.