1833927 Members
3059 Online
110063 Solutions
New Discussion

Re: cclogd daemon

 
Isaac_4
Frequent Advisor

cclogd daemon

Hi, some body know while the cclogd daemon stop without any reason ?

we recived one message from the root mail !
The chassis code logging daemon (cclogd) is not currently running.


The time is gold
3 REPLIES 3
Tim Adamson_1
Honored Contributor

Re: cclogd daemon

The cclogd log files might provide some clues.

Refer to the cclogd(1M) man page for a list of the relevant log files. There are several of them.

/var/stm/logs/sys/activity_log_cclogd - Activity log of cclogd
/var/stm/logs/os/ccbootlog - Last OS Chassis Code boot log
/var/stm/logs/os/ccbootlog## - OS Chassis Code boot log archives
/var/stm/logs/os/ccerrlog - Chassis Code error log
/var/stm/data/daemon_list - List of daemons installed

I would start with the first one (activity_log_cclogd). You will be able to check its contents using cstm.


Tim
Yesterday is history, tomorrow is a mystery, today is a gift. That's why it's called the present.
Tim Adamson_1
Honored Contributor

Re: cclogd daemon

To view the log file try the following:

# cstm
cstm> uial


Scroll through the information to the date that the cclogd stopped running and determine if there are any error messages. Maybe some simply stopped diagnostics and forgot to start it again.


Tim.
Yesterday is history, tomorrow is a mystery, today is a gift. That's why it's called the present.
Mike Trax
New Member

Re: cclogd daemon

We get this all the time on our Superdome partitions, whenever we reboot or shutdown. We ignore them now. It's a superdome bug; seems there is a monitoring-timing issue, where the system is going thru it's normal shutting down of processes, and when it kills the cclogd, another monitoring process detects this, and reports it! This would be a false-error, (obviously) as the monitoring should be intelligent enough to ignore dying processes, after the "shutdown" process has initiated.
HP has told us to wait for a patch!! (We're still waiting...).