<?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: cclogd daemon in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cclogd-daemon/m-p/3066329#M139705</link>
    <description>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.&lt;BR /&gt;HP has told us to wait for a patch!! (We're still waiting...).</description>
    <pubDate>Thu, 11 Sep 2003 21:09:45 GMT</pubDate>
    <dc:creator>Mike Trax</dc:creator>
    <dc:date>2003-09-11T21:09:45Z</dc:date>
    <item>
      <title>cclogd daemon</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cclogd-daemon/m-p/3066326#M139702</link>
      <description>Hi, some body know while the cclogd daemon stop without any reason ?&lt;BR /&gt;&lt;BR /&gt;we recived one message from the root mail !&lt;BR /&gt; The chassis code logging daemon (cclogd) is not currently running.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Sep 2003 21:49:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cclogd-daemon/m-p/3066326#M139702</guid>
      <dc:creator>Isaac_4</dc:creator>
      <dc:date>2003-09-08T21:49:19Z</dc:date>
    </item>
    <item>
      <title>Re: cclogd daemon</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cclogd-daemon/m-p/3066327#M139703</link>
      <description>The cclogd log files might provide some clues.&lt;BR /&gt;&lt;BR /&gt;Refer to the cclogd(1M) man page for a list of the relevant log files.  There are several of them.  &lt;BR /&gt;&lt;BR /&gt;/var/stm/logs/sys/activity_log_cclogd - Activity log of cclogd&lt;BR /&gt;/var/stm/logs/os/ccbootlog - Last OS Chassis Code boot log&lt;BR /&gt;/var/stm/logs/os/ccbootlog## - OS Chassis Code boot log archives&lt;BR /&gt;/var/stm/logs/os/ccerrlog - Chassis Code error log&lt;BR /&gt;/var/stm/data/daemon_list - List of daemons installed&lt;BR /&gt;&lt;BR /&gt;I would start with the first one (activity_log_cclogd).  You will be able to check its contents using cstm.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Tim</description>
      <pubDate>Mon, 08 Sep 2003 21:54:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cclogd-daemon/m-p/3066327#M139703</guid>
      <dc:creator>Tim Adamson_1</dc:creator>
      <dc:date>2003-09-08T21:54:20Z</dc:date>
    </item>
    <item>
      <title>Re: cclogd daemon</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cclogd-daemon/m-p/3066328#M139704</link>
      <description>To view the log file try the following:&lt;BR /&gt;&lt;BR /&gt;# cstm&lt;BR /&gt;cstm&amp;gt; uial&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Tim.</description>
      <pubDate>Mon, 08 Sep 2003 21:57:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cclogd-daemon/m-p/3066328#M139704</guid>
      <dc:creator>Tim Adamson_1</dc:creator>
      <dc:date>2003-09-08T21:57:57Z</dc:date>
    </item>
    <item>
      <title>Re: cclogd daemon</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cclogd-daemon/m-p/3066329#M139705</link>
      <description>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.&lt;BR /&gt;HP has told us to wait for a patch!! (We're still waiting...).</description>
      <pubDate>Thu, 11 Sep 2003 21:09:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cclogd-daemon/m-p/3066329#M139705</guid>
      <dc:creator>Mike Trax</dc:creator>
      <dc:date>2003-09-11T21:09:45Z</dc:date>
    </item>
  </channel>
</rss>

