topic Re: cclogd process in Operating System - HP-UX

cclogd process

Harikrishna Babu — Mon, 03 Sep 2001 23:17:24 GMT

Hi all,

We're using HP-UX 11 with 2 CPUs. I could always see a process 'cclogd' run by root, which utilizes highest CPU time always (reported by glance & top utilities).

$ ps -ef | grep cclogd
root 1899 1589 238 22:41:51 ? 577:43 cclogd

What is it all about? appriciate any guidance.

Regards,
Hari

Re: cclogd process

Frank Li — Mon, 03 Sep 2001 23:44:28 GMT

Hi,

go to: search.hp.com
and type "cclogd" in the search box, you will get lots on this question.

Re: cclogd process

Michael Tully — Mon, 03 Sep 2001 23:58:06 GMT

Hi Hari,

The 'cclogd' is the Chassis Log logging daemon.
The support tools manager STM uses this process. See the man page for further details
# man cclogd

HTH
-Michael

Re: cclogd process

Sridhar Bhaskarla — Tue, 04 Sep 2001 00:10:39 GMT

The earlier version of DIAGNOSTICS seems to have problems with cclogd that kills CPU. There have been recent patches released to get rid of this problem. The most recent patch that I know is is PHSS_24044 that superceded PHSS_23658

//Start
SR 8606179466 / DTS JAGad48690: 2. On systems which use the chassis code logging
daemon (cclogd), like Superdome, N-Class, L-Class,
and A-Class, the daemon will go into an endless
loop at a certain point, and use a high percentage of the CPU.
//End

Get your ONLINE DIAGNOSTICS updated to the most recent version.

-Sri

Re: cclogd process

linuxfan — Tue, 04 Sep 2001 00:57:04 GMT

Hi Hari,

This is a known problem and there is a patch for this.

If you are using the version A.24.00 then you would need to install the patch PHSS_23655 but if you are using version A.25.00 then you would need the patch PHSS_24044

The best thing is to upgrade to the latest version of STM which A.28.00
http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=B6191AAE

-HTH
Ramesh

Re: cclogd process

Dayanand Naik — Tue, 04 Sep 2001 04:09:48 GMT

Hi Hari,

I had similar problem with cclogd daemon on my L Class server. As it is a chasis log dameon reporting error or warning, you can just kill that process and the process will start by itself. And the CPU process utilization will be normal as you can expect.

As Ramesh mention you can also apply patch for rectifing the same.

Hope this helps.

Dayanand Naik