<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: About cclogd daemon in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/about-cclogd-daemon/m-p/2623775#M39255</link>
    <description>Hi,&lt;BR /&gt;It is a known problem.&lt;BR /&gt;Yoy need to load a patch PHSS 23658&lt;BR /&gt;(. On systems which use the chassis code logging daemon&lt;BR /&gt;            (cclogd) the daemon will go into an endless loop at&lt;BR /&gt;            a certain point, and use a high percentage of the CPU.&lt;BR /&gt;            Such systems include Superdome, N-Class, L-Class,)&lt;BR /&gt;            &lt;BR /&gt;A new command called 'cclogview' is available starting&lt;BR /&gt;with the March 2001 release of the Online Diagnostics&lt;BR /&gt;(Support Tools Manager - STM) for HP-UX servers.&lt;BR /&gt;&lt;BR /&gt;The purpose of the utility is to allow the GSP chassis&lt;BR /&gt;logs to be read via the operating system; the output can&lt;BR /&gt;be viewed without having access to the console; another&lt;BR /&gt;advantage is that tools such as 'vi' and 'grep' can be&lt;BR /&gt;used to review the log files.&lt;BR /&gt;&lt;BR /&gt;The GSP logs are logged to the operating system by the&lt;BR /&gt;cclogd(1m) daemon, which runs from the operating system.&lt;BR /&gt;The files created are cc*log* (such as 'ccbootlog' and 'ccerrlog').&lt;BR /&gt;The 'cclogview' utility allows the files to be formatted to viewable&lt;BR /&gt;text.&lt;BR /&gt;&lt;BR /&gt;According to the cclogview(1m) man page, this command&lt;BR /&gt;will run on all HP-UX systems; however only systems that generate&lt;BR /&gt;chassis logs (such as L-class, N-class, Superdome, etc) will&lt;BR /&gt;have logs files to view.&lt;BR /&gt;&lt;BR /&gt;Syntax examples:&lt;BR /&gt;&lt;BR /&gt;  cclogview /var/stm/logs/os/ccbootlog | more&lt;BR /&gt;&lt;BR /&gt;  or&lt;BR /&gt;&lt;BR /&gt;  cd /var/stm/logs/os&lt;BR /&gt;  cclogview ./ccbootlog | more&lt;BR /&gt;&lt;BR /&gt;Animesh&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 03 Dec 2001 08:03:03 GMT</pubDate>
    <dc:creator>Animesh Chakraborty</dc:creator>
    <dc:date>2001-12-03T08:03:03Z</dc:date>
    <item>
      <title>About cclogd daemon</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-cclogd-daemon/m-p/2623774#M39254</link>
      <description>I had found that the cclogd daemon had caused the cpu over 90%. Can anyone tell me what had happened to my server and how to view the problem log?&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Mon, 03 Dec 2001 07:37:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-cclogd-daemon/m-p/2623774#M39254</guid>
      <dc:creator>Kenny Chau</dc:creator>
      <dc:date>2001-12-03T07:37:55Z</dc:date>
    </item>
    <item>
      <title>Re: About cclogd daemon</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-cclogd-daemon/m-p/2623775#M39255</link>
      <description>Hi,&lt;BR /&gt;It is a known problem.&lt;BR /&gt;Yoy need to load a patch PHSS 23658&lt;BR /&gt;(. On systems which use the chassis code logging daemon&lt;BR /&gt;            (cclogd) the daemon will go into an endless loop at&lt;BR /&gt;            a certain point, and use a high percentage of the CPU.&lt;BR /&gt;            Such systems include Superdome, N-Class, L-Class,)&lt;BR /&gt;            &lt;BR /&gt;A new command called 'cclogview' is available starting&lt;BR /&gt;with the March 2001 release of the Online Diagnostics&lt;BR /&gt;(Support Tools Manager - STM) for HP-UX servers.&lt;BR /&gt;&lt;BR /&gt;The purpose of the utility is to allow the GSP chassis&lt;BR /&gt;logs to be read via the operating system; the output can&lt;BR /&gt;be viewed without having access to the console; another&lt;BR /&gt;advantage is that tools such as 'vi' and 'grep' can be&lt;BR /&gt;used to review the log files.&lt;BR /&gt;&lt;BR /&gt;The GSP logs are logged to the operating system by the&lt;BR /&gt;cclogd(1m) daemon, which runs from the operating system.&lt;BR /&gt;The files created are cc*log* (such as 'ccbootlog' and 'ccerrlog').&lt;BR /&gt;The 'cclogview' utility allows the files to be formatted to viewable&lt;BR /&gt;text.&lt;BR /&gt;&lt;BR /&gt;According to the cclogview(1m) man page, this command&lt;BR /&gt;will run on all HP-UX systems; however only systems that generate&lt;BR /&gt;chassis logs (such as L-class, N-class, Superdome, etc) will&lt;BR /&gt;have logs files to view.&lt;BR /&gt;&lt;BR /&gt;Syntax examples:&lt;BR /&gt;&lt;BR /&gt;  cclogview /var/stm/logs/os/ccbootlog | more&lt;BR /&gt;&lt;BR /&gt;  or&lt;BR /&gt;&lt;BR /&gt;  cd /var/stm/logs/os&lt;BR /&gt;  cclogview ./ccbootlog | more&lt;BR /&gt;&lt;BR /&gt;Animesh&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Dec 2001 08:03:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-cclogd-daemon/m-p/2623775#M39255</guid>
      <dc:creator>Animesh Chakraborty</dc:creator>
      <dc:date>2001-12-03T08:03:03Z</dc:date>
    </item>
    <item>
      <title>Re: About cclogd daemon</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-cclogd-daemon/m-p/2623776#M39256</link>
      <description>Thanks for your quick response.&lt;BR /&gt;&lt;BR /&gt;I had got part of the results like this:&lt;BR /&gt;&lt;BR /&gt;Log Entry 1568: 01/01/1970 00:06:26&lt;BR /&gt;Alert Level 0: No failure; Keyword: 110F21F&lt;BR /&gt;Processor 0 ; Status: 15&lt;BR /&gt;Logged by HP-UX 0 during display_activity update subActivity 21&lt;BR /&gt;Legacy PA HEX chassis-code: f21f&lt;BR /&gt;0xf8e007001100f21f 0x000000000000f21f&lt;BR /&gt;0x58e00f001100f21f 0x000046000100061a&lt;BR /&gt;&lt;BR /&gt;So do you know that happened to my server? How to fix it? Need to download the patch for that?&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Dec 2001 08:13:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-cclogd-daemon/m-p/2623776#M39256</guid>
      <dc:creator>Kenny Chau</dc:creator>
      <dc:date>2001-12-03T08:13:07Z</dc:date>
    </item>
    <item>
      <title>Re: About cclogd daemon</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-cclogd-daemon/m-p/2623777#M39257</link>
      <description>Hi &lt;BR /&gt;&lt;BR /&gt;yep, you need to download the patch and install it . &lt;BR /&gt;&lt;BR /&gt;to fix the problem before installing the patch &lt;BR /&gt;do &lt;BR /&gt;     # /sbin/init.d/diagnostic stop&lt;BR /&gt;&lt;BR /&gt;     # /sbin/init.d/diagnostic start&lt;BR /&gt;&lt;BR /&gt;like it was writen this is an know problem . &lt;BR /&gt;&lt;BR /&gt;you can download the patch from the itrc . &lt;BR /&gt;</description>
      <pubDate>Mon, 03 Dec 2001 08:27:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-cclogd-daemon/m-p/2623777#M39257</guid>
      <dc:creator>eran maor</dc:creator>
      <dc:date>2001-12-03T08:27:57Z</dc:date>
    </item>
    <item>
      <title>Re: About cclogd daemon</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/about-cclogd-daemon/m-p/2623778#M39258</link>
      <description>Hi Kenny,&lt;BR /&gt;&lt;BR /&gt;Also have a look at this thread,&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://us-support.external.hp.com/cki/bin/doc.pl/sid=6020fe5e0595c9919a/screen=ckiDisplayDocument?docId=200000055980703" target="_blank"&gt;http://us-support.external.hp.com/cki/bin/doc.pl/sid=6020fe5e0595c9919a/screen=ckiDisplayDocument?docId=200000055980703&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Dec 2001 14:12:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/about-cclogd-daemon/m-p/2623778#M39258</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2001-12-03T14:12:01Z</dc:date>
    </item>
  </channel>
</rss>

