<?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>question Re: How to enable debug logging for Cloudera Manager server in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-enable-debug-logging-for-Cloudera-Manager-server/m-p/79986#M83330</link>
    <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/21997"&gt;@desind&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are a few ways to enable DEBUG or TRACE depending on what sort of problem you are attempting to troubleshoot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(1)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If CM won't start or if there is a problem where you do not have an idea what classes are involved, you can enable DEBUG or TRACE for the whole server.&amp;nbsp; &lt;FONT color="#FF6600"&gt;Warning&lt;/FONT&gt;:&amp;nbsp; this can be very very verbose, so it is likely going to be difficult to capture an event&lt;FONT color="#000000"&gt;.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Edit &lt;STRONG&gt;/usr/sbin/cmf-server &lt;/STRONG&gt;in CM 5--- Edit &lt;STRONG&gt;/opt/cloudera/cm/bin/cm-server&lt;/STRONG&gt; in CM 6&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Change this:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier" color="#000000"&gt;export CMF_ROOT_LOGGER="INFO,LOGFILE"&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;to&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier" color="#000000"&gt;export CMF_ROOT_LOGGER="&lt;STRONG&gt;DEBUG&lt;/STRONG&gt;,LOGFILE"&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;Restart CM to have the change apply.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;(2)&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;If you know what class or package you want to DEBUG, you can edit &lt;STRONG&gt;/etc/cloudera-scm-server/log4j.properties&lt;/STRONG&gt;:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;Add lines as follows... this is an example of turning on debugging for just ldap classes in SpringFramework (used in LDAP authentication):&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier" color="#000000"&gt;log4j.logger.org.springframework.ldap=TRACE&lt;BR /&gt;log4j.logger.org.springframework.security.ldap=TRACE&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;Restart CM to have the changes apply&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;(3)&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;If you want to turn on some debug or trace level logging for just the current session of Cloudera Manager, you can use the debug page:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;https://cm_host:cm_port/cmf/debug/logLevel&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Choose the Logger from the drop-down&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Select the level to which you want to change the logging&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Click "Submit Query" button to apply&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;The log level you selected will only apply until you restart Cloudera Manager&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;(4)&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;API debugging.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;You can enable API debugging in the Cloudera Manager interface:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Navigate to: &lt;STRONG&gt;Administration --&amp;gt; Settings&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Search for &lt;STRONG&gt;Enable Debugging of API&lt;/STRONG&gt;&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Check the box next to it and Save&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;API debugging will be written to the /var/log/cloudra-scm-server/cloudera-scm-server.log file without restart.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;(5)&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;NOTE:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;If you do enable verbose debugging, you may need to increase the size of log files or the number to be able to review relevant lines.&amp;nbsp; To do so, I believe you can simply edit the following in &lt;STRONG&gt;/etc/cloudera-scm-server/log4j.properties&lt;/STRONG&gt;:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;log4j.appender.LOGFILE.MaxFileSize=10MB&lt;BR /&gt;log4j.appender.LOGFILE.MaxBackupIndex=10&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 18 Sep 2018 15:41:41 GMT</pubDate>
    <dc:creator>bgooley</dc:creator>
    <dc:date>2018-09-18T15:41:41Z</dc:date>
    <item>
      <title>How to enable debug logging for Cloudera Manager server</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-enable-debug-logging-for-Cloudera-Manager-server/m-p/79591#M83329</link>
      <description>&lt;P&gt;What changes do i need to make in&amp;nbsp;/etc/cloudera-scm-server/log4j.properties&amp;nbsp; to view debug logs.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Sep 2018 15:31:03 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-enable-debug-logging-for-Cloudera-Manager-server/m-p/79591#M83329</guid>
      <dc:creator>desind</dc:creator>
      <dc:date>2018-09-10T15:31:03Z</dc:date>
    </item>
    <item>
      <title>Re: How to enable debug logging for Cloudera Manager server</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-enable-debug-logging-for-Cloudera-Manager-server/m-p/79986#M83330</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/21997"&gt;@desind&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are a few ways to enable DEBUG or TRACE depending on what sort of problem you are attempting to troubleshoot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(1)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If CM won't start or if there is a problem where you do not have an idea what classes are involved, you can enable DEBUG or TRACE for the whole server.&amp;nbsp; &lt;FONT color="#FF6600"&gt;Warning&lt;/FONT&gt;:&amp;nbsp; this can be very very verbose, so it is likely going to be difficult to capture an event&lt;FONT color="#000000"&gt;.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Edit &lt;STRONG&gt;/usr/sbin/cmf-server &lt;/STRONG&gt;in CM 5--- Edit &lt;STRONG&gt;/opt/cloudera/cm/bin/cm-server&lt;/STRONG&gt; in CM 6&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Change this:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier" color="#000000"&gt;export CMF_ROOT_LOGGER="INFO,LOGFILE"&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;to&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier" color="#000000"&gt;export CMF_ROOT_LOGGER="&lt;STRONG&gt;DEBUG&lt;/STRONG&gt;,LOGFILE"&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;Restart CM to have the change apply.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;(2)&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;If you know what class or package you want to DEBUG, you can edit &lt;STRONG&gt;/etc/cloudera-scm-server/log4j.properties&lt;/STRONG&gt;:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;Add lines as follows... this is an example of turning on debugging for just ldap classes in SpringFramework (used in LDAP authentication):&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier" color="#000000"&gt;log4j.logger.org.springframework.ldap=TRACE&lt;BR /&gt;log4j.logger.org.springframework.security.ldap=TRACE&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;Restart CM to have the changes apply&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;(3)&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;If you want to turn on some debug or trace level logging for just the current session of Cloudera Manager, you can use the debug page:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;https://cm_host:cm_port/cmf/debug/logLevel&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Choose the Logger from the drop-down&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Select the level to which you want to change the logging&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Click "Submit Query" button to apply&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;The log level you selected will only apply until you restart Cloudera Manager&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;(4)&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;API debugging.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;You can enable API debugging in the Cloudera Manager interface:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Navigate to: &lt;STRONG&gt;Administration --&amp;gt; Settings&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Search for &lt;STRONG&gt;Enable Debugging of API&lt;/STRONG&gt;&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;- Check the box next to it and Save&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;API debugging will be written to the /var/log/cloudra-scm-server/cloudera-scm-server.log file without restart.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;(5)&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;NOTE:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;If you do enable verbose debugging, you may need to increase the size of log files or the number to be able to review relevant lines.&amp;nbsp; To do so, I believe you can simply edit the following in &lt;STRONG&gt;/etc/cloudera-scm-server/log4j.properties&lt;/STRONG&gt;:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;log4j.appender.LOGFILE.MaxFileSize=10MB&lt;BR /&gt;log4j.appender.LOGFILE.MaxBackupIndex=10&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Sep 2018 15:41:41 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-enable-debug-logging-for-Cloudera-Manager-server/m-p/79986#M83330</guid>
      <dc:creator>bgooley</dc:creator>
      <dc:date>2018-09-18T15:41:41Z</dc:date>
    </item>
  </channel>
</rss>

