Control the Cloudera Manager Logging Level

[#1]

Summary

Cloudera Manager is the best-in-class holistic interface that provides end-to-end system management and key enterprise features to provide granular visibility into and control over every part of an enterprise data hub. From time to time, you’ll need to increase the logging level if you’re troubleshooting issues within Cloudera Manager.

Change your Cloudera Manager Server logging level

The Cloudera Manager Server must be configured from the command line within Cloudera Manager Server itself.

Log in as root to your Cloudera Manager Server:

mbush@mbush-MBP16 CDSW % ssh root@<CM SERVER FQDN>

Check the Cloudera Manager Server log4j file:

[root@<CM SERVER FQDN> ~]# cat /etc/cloudera-scm-server/log4j.properties

# Copyright (c) 2012 Cloudera, Inc. All rights reserved.

#

# !!!!! IMPORTANT !!!!!

# The Cloudera Manager server finds its log file by querying log4j. It

# assumes that the first file appender in this file is the server log.

# See LogUtil.getServerLogFile() for more details.

#

# Define some default values that can be overridden by system properties

cmf.root.logger=INFO,CONSOLE

cmf.log.dir=.

cmf.log.file=cmf-server.log

cmf.perf.log.file=cmf-server-perf.log

cmf.jetty.log.file=cmf-server-nio.log

..

..

..

The key line to control the logging level of the Cloudera Manager Server is highlighted in red.

This can be done by amending the cmf.root.logger parameter and restarting the CM Server:

cmf.root.logger=DEBUG,CONSOLE

#RESTART THE CLOUDERA MANAGER SERVICE TO COMMIT THE AMENDMENT

[root@<CM SERVER FQDN> ~]# systemctl restart cloudera-scm-server

If you would like to know more about controlling further elements, refer to another very helpful Cloudera Community page -  How to enable debug logging for Cloudera Manager server. This blog also goes into more detail about how you can amend the logging level at the CM Server binary level (if you are simply unable to get the CM Server to start at all).