<?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: Start the Cluster in debug mode in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/start-the-cluster-in-debug-mode/m-p/4687702#M667429</link>
    <description>If i want to start the cluster in debug mode for check what is the procedure</description>
    <pubDate>Thu, 16 Sep 2010 19:51:56 GMT</pubDate>
    <dc:creator>R.SRIDHAR</dc:creator>
    <dc:date>2010-09-16T19:51:56Z</dc:date>
    <item>
      <title>Start the Cluster in debug mode</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/start-the-cluster-in-debug-mode/m-p/4687700#M667427</link>
      <description>Hi&lt;BR /&gt;   Can any one say me how to start the service guard in hp-ux in debug mode.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 16 Sep 2010 18:50:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/start-the-cluster-in-debug-mode/m-p/4687700#M667427</guid>
      <dc:creator>R.SRIDHAR</dc:creator>
      <dc:date>2010-09-16T18:50:14Z</dc:date>
    </item>
    <item>
      <title>Re: Start the Cluster in debug mode</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/start-the-cluster-in-debug-mode/m-p/4687701#M667428</link>
      <description>clarify what you mean by "debug mode"&lt;BR /&gt;are you looking to increase logging into syslog.log?&lt;BR /&gt;for the cluster as whole?&lt;BR /&gt;and why?&lt;BR /&gt;</description>
      <pubDate>Thu, 16 Sep 2010 19:04:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/start-the-cluster-in-debug-mode/m-p/4687701#M667428</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2010-09-16T19:04:52Z</dc:date>
    </item>
    <item>
      <title>Re: Start the Cluster in debug mode</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/start-the-cluster-in-debug-mode/m-p/4687702#M667429</link>
      <description>If i want to start the cluster in debug mode for check what is the procedure</description>
      <pubDate>Thu, 16 Sep 2010 19:51:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/start-the-cluster-in-debug-mode/m-p/4687702#M667429</guid>
      <dc:creator>R.SRIDHAR</dc:creator>
      <dc:date>2010-09-16T19:51:56Z</dc:date>
    </item>
    <item>
      <title>Re: Start the Cluster in debug mode</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/start-the-cluster-in-debug-mode/m-p/4687703#M667430</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;You did not specify which version of&lt;BR /&gt;Serviceguard is used.&lt;BR /&gt;&lt;BR /&gt;The cmsetlog command (obsolete with SG A.11.19)&lt;BR /&gt;enables users to obtain a more verbose output&lt;BR /&gt;of cmcld. This is extremely useful if a&lt;BR /&gt;problem should be reproduced. cmsetlog allows&lt;BR /&gt;to set the log level and to restrict logging&lt;BR /&gt;to specific categories and modules.&lt;BR /&gt;&lt;BR /&gt;From SG A.11.19 onwards you can start logging&lt;BR /&gt;for cmcld by adding the following lines in&lt;BR /&gt;the /etc/cmcluster.conf and do a&lt;BR /&gt;kill -SIGHUP &lt;PID&gt;.&lt;BR /&gt;&lt;BR /&gt;CMCLD_LOG_FILE=/var/adm/cmcluster/cmcld.log&lt;BR /&gt;CMCLD_LOG_LEVEL=5&lt;BR /&gt;&lt;BR /&gt;You can also enable debug logging for a&lt;BR /&gt;specific module only by setting in the same&lt;BR /&gt;file:&lt;BR /&gt;&lt;BR /&gt;CMCLD_{module mnemonic}_LOG_LEVEL=5&lt;BR /&gt;&lt;BR /&gt;where {module mnemonic} is one of the following:&lt;BR /&gt;&lt;BR /&gt;ATN = Auto Trans&lt;BR /&gt;CDB = Configuration Database&lt;BR /&gt;CLM = Cluster Management&lt;BR /&gt;CMD = Commands&lt;BR /&gt;CML = SAF Distributed Lock Service&lt;BR /&gt;CMP = Config/Status Proxy&lt;BR /&gt;CMS = SAF Cluster Membership Service&lt;BR /&gt;CNF = Configuration&lt;BR /&gt;COM = Communication Server&lt;BR /&gt;CSV = Command Server&lt;BR /&gt;DFA = Disk File Access&lt;BR /&gt;DLK = Disk Lock&lt;BR /&gt;DLM = Distributed Lock Management&lt;BR /&gt;EVT = Cluster Management Event&lt;BR /&gt;GMD = Group Membership Server&lt;BR /&gt;GMS = Group Membership Service&lt;BR /&gt;LOC = Local Communication&lt;BR /&gt;LVM = Logical Volume Management&lt;BR /&gt;MDV = Module Version&lt;BR /&gt;MSG = Messaging&lt;BR /&gt;NET = Network Management&lt;BR /&gt;PKG = Package Management&lt;BR /&gt;PLE = Placement Engine&lt;BR /&gt;QSM = Quorum Service&lt;BR /&gt;REM = Remote Communication&lt;BR /&gt;RES = EMS Resources&lt;BR /&gt;SDB = Status Database&lt;BR /&gt;SEC = Security Service&lt;BR /&gt;SES = Sessions&lt;BR /&gt;SRV = Service Management&lt;BR /&gt;STA = Status Database API&lt;BR /&gt;SYN = Synchronization&lt;BR /&gt;UNK = Unknown&lt;BR /&gt;UTD = Utility Daemon&lt;BR /&gt;&lt;BR /&gt;There is also debug logging of SG commands &lt;BR /&gt;using the '-D' option (SG A.11.18 and later)&lt;BR /&gt;If you want to change the logging for a&lt;BR /&gt;single command, you can specify -D {1-5} or&lt;BR /&gt;-O {filename) on the command line of any &lt;BR /&gt;commands. These command line options will&lt;BR /&gt;take precedence over the COMMAND_LOG_LEVEL/COMMAND_LOG_FILE values&lt;BR /&gt;specified in /etc/cmcluster.conf.&lt;BR /&gt;&lt;BR /&gt;And so on.&lt;BR /&gt;&lt;BR /&gt;As you can see, there are many ways to do it.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;VK2COT&lt;BR /&gt;&lt;/PID&gt;</description>
      <pubDate>Fri, 17 Sep 2010 05:34:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/start-the-cluster-in-debug-mode/m-p/4687703#M667430</guid>
      <dc:creator>VK2COT</dc:creator>
      <dc:date>2010-09-17T05:34:29Z</dc:date>
    </item>
  </channel>
</rss>

