topic Re: STM log in Operating System - HP-UX

STM log

Macho_2 — Fri, 27 May 2005 01:46:22 GMT

I cannot find the ccerrlog file under the /var/stm/logs/os directory.
What is purpose of the ccerrlog file and how to view the file?
Is it the ccerrlog file is the script that I should run to get output for the stmlog?

Re: STM log

Joseph Loo — Fri, 27 May 2005 02:18:49 GMT

hi,

what are the logfiles in /var/stm/logs/os? did any one remove that file?

have u try restarting the diagnostic and verify if the logs appear?

regards.

Re: STM log

Macho_2 — Fri, 27 May 2005 02:49:06 GMT

sngxxxx cd /var/stm/logs/os
sngxxxx [/var/stm/logs/os]ll
total 158
-rw-r--r-- 1 root root 10780 Dec 28 2003 log1.raw.cur
-rw-r--r-- 1 root root 69196 May 27 15:25 memlog
sngxxxx [/var/stm/logs/os]

Re: STM log

Joseph Loo — Fri, 27 May 2005 03:03:48 GMT

hi,

ccerrlog is the chassis code error log file. just like to check if diagmond daemon is running:

# ps -ef|grep diagmond

any output, also, if running:

# /sbin/init.d/diagnostic stop
and then restart:
# /sbin/init.d/diagnostic start

in order to view the error log:

# cclogview /var/stm/logs/os/ccerrlog|more

for more info on the logs:

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000066936191

regards.

Re: STM log

Macho_2 — Fri, 27 May 2005 04:08:27 GMT

sngxxxx [/]/sbin/init.d/diagnostic stop
sngxxxx [/]/sbin/init.d/diagnostic start
sngxxxx [/]ps -ef | grep diagmond
root 6072 5880 0 16:36:23 ttyp2 0:00 grep diagmond
root 5950 1 0 16:36:03 ? 0:00 /usr/sbin/stm/uut/bin/sys/diagmo
nd
sngxxxx [/]cd /var/stm/logs/os/
sngxxxx [/var/stm/logs/os]ls
log1.raw.cur memlog
Hi, I still can't find the file.What is the other method to get the file.

Thank You.

Re: STM log

Andrew Merritt_2 — Wed, 01 Jun 2005 07:21:44 GMT

The ccerrlog file will only exist if the cclogd daemon is running on your system (it is not applicable to all hardware) has found any chassis code errors.

The absence of the file does not of itself indicate a problem.

You can view the file, if it is present, in the 'logtool' tool inside of STM.

'cclogview' is an unsupported tool, and doesn't understand all the latest chassis codes, so the output of this may terminate suddenly without reading all of the file.

What is the reason you are looking for the ccerrlog file?

Andrew