<?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 dm-chassis error 200 in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dm-chassis-error-200/m-p/4506781#M650145</link>
    <description>I've recieved the following error via EMS. Could someone who has exerienced this before educate me on what exactly has happened, and also the corrective action needed.&lt;BR /&gt;&lt;BR /&gt;====================================&lt;BR /&gt;&lt;BR /&gt;Event Time..........: Thu Oct  1 11:30:14 2009&lt;BR /&gt;Severity............: MAJORWARNING&lt;BR /&gt;Monitor.............: dm_chassis&lt;BR /&gt;Event #.............: 200                 &lt;BR /&gt;System..............: &lt;BR /&gt;&lt;BR /&gt;Summary:&lt;BR /&gt;      The chassis code logging daemon (cclogd) is not currently running.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Description of Error:&lt;BR /&gt;&lt;BR /&gt; The chassis code logging daemon supplies all the chassis logs monitored by&lt;BR /&gt; dm_chassis.  Cclogd must be running for dm_chassis to get the system chassis&lt;BR /&gt; codes.&lt;BR /&gt;&lt;BR /&gt;Probable Cause / Recommended Action:&lt;BR /&gt;&lt;BR /&gt;     This chassis code logging daemon has been shut-down. &lt;BR /&gt;          To re-start cclogd, run cstm as root.  If diagmond is not running,&lt;BR /&gt;          issue the command &lt;BR /&gt;          cstm&amp;gt;stmstartup&lt;BR /&gt;&lt;BR /&gt;          If diagmond is running, issue the command &lt;BR /&gt;          cstm&amp;gt;daemonstartup&lt;BR /&gt;&lt;BR /&gt;          From the list, select "cclogd".&lt;BR /&gt;=====================================</description>
    <pubDate>Fri, 02 Oct 2009 03:10:12 GMT</pubDate>
    <dc:creator>Noel Daniel</dc:creator>
    <dc:date>2009-10-02T03:10:12Z</dc:date>
    <item>
      <title>dm-chassis error 200</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dm-chassis-error-200/m-p/4506781#M650145</link>
      <description>I've recieved the following error via EMS. Could someone who has exerienced this before educate me on what exactly has happened, and also the corrective action needed.&lt;BR /&gt;&lt;BR /&gt;====================================&lt;BR /&gt;&lt;BR /&gt;Event Time..........: Thu Oct  1 11:30:14 2009&lt;BR /&gt;Severity............: MAJORWARNING&lt;BR /&gt;Monitor.............: dm_chassis&lt;BR /&gt;Event #.............: 200                 &lt;BR /&gt;System..............: &lt;BR /&gt;&lt;BR /&gt;Summary:&lt;BR /&gt;      The chassis code logging daemon (cclogd) is not currently running.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Description of Error:&lt;BR /&gt;&lt;BR /&gt; The chassis code logging daemon supplies all the chassis logs monitored by&lt;BR /&gt; dm_chassis.  Cclogd must be running for dm_chassis to get the system chassis&lt;BR /&gt; codes.&lt;BR /&gt;&lt;BR /&gt;Probable Cause / Recommended Action:&lt;BR /&gt;&lt;BR /&gt;     This chassis code logging daemon has been shut-down. &lt;BR /&gt;          To re-start cclogd, run cstm as root.  If diagmond is not running,&lt;BR /&gt;          issue the command &lt;BR /&gt;          cstm&amp;gt;stmstartup&lt;BR /&gt;&lt;BR /&gt;          If diagmond is running, issue the command &lt;BR /&gt;          cstm&amp;gt;daemonstartup&lt;BR /&gt;&lt;BR /&gt;          From the list, select "cclogd".&lt;BR /&gt;=====================================</description>
      <pubDate>Fri, 02 Oct 2009 03:10:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dm-chassis-error-200/m-p/4506781#M650145</guid>
      <dc:creator>Noel Daniel</dc:creator>
      <dc:date>2009-10-02T03:10:12Z</dc:date>
    </item>
    <item>
      <title>Re: dm-chassis error 200</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dm-chassis-error-200/m-p/4506782#M650146</link>
      <description>Did you do the suggested steps yet?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Also check if your version is up to date!&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE" target="_blank"&gt;http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE&lt;/A&gt;</description>
      <pubDate>Fri, 02 Oct 2009 08:30:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dm-chassis-error-200/m-p/4506782#M650146</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-10-02T08:30:29Z</dc:date>
    </item>
    <item>
      <title>Re: dm-chassis error 200</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dm-chassis-error-200/m-p/4506783#M650147</link>
      <description>Torsten,&lt;BR /&gt;&lt;BR /&gt;The daemon restarts as per instructions.&lt;BR /&gt;&lt;BR /&gt;But it has recurred after a lapse of over 3 months, today. Is this caused due to any known issue such as FW versions etc. ?&lt;BR /&gt;</description>
      <pubDate>Tue, 19 Jan 2010 11:01:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dm-chassis-error-200/m-p/4506783#M650147</guid>
      <dc:creator>Noel Daniel</dc:creator>
      <dc:date>2010-01-19T11:01:02Z</dc:date>
    </item>
    <item>
      <title>Re: dm-chassis error 200</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dm-chassis-error-200/m-p/4506784#M650148</link>
      <description>First I would check if the version is up2date.</description>
      <pubDate>Tue, 19 Jan 2010 15:22:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dm-chassis-error-200/m-p/4506784#M650148</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2010-01-19T15:22:47Z</dc:date>
    </item>
  </channel>
</rss>

