Known Issues Fixed in Cloudera Manager 4.0.2

— Two links in the Cloudera Manager Admin Console allow read-only access to arbitrary files on managed hosts.

Severity: Medium

Resolution: Fixed in Cloudera Manager 4.0.2. For More Information, see the Cloudera Security Bulletin. Solution: Upgrade to Cloudera Manager version 4.0.2 or later

Work Around: If immediate upgrade is not possible, disable non-admin user access to Cloudera Manager to limit the vulnerability to Cloudera Manager admins.

— (Applies to MySQL usage only) After upgrading to Cloudera Manager 4.0.1, the Cloudera Manager Managementservices fail to start.

After upgrading to Cloudera Manager 4.0.1, the Cloudera Manager Management services fail to start and have a health status of BAD in the Cloudera Manager Admin Console. The following message appears in the log:

                  2012-04-26 11:46:14,109 ERROR com.cloudera.enterprise.dbutil.SqlFileRunner: Exception while executing
                  ddl scripts. java.sql.SQLException: Thread stack overrun: 5512 bytes used of a 131072 byte stack, and
                  131072 bytes needed. Use 'mysqld -O thread_stack=#' to specify a bigger stack.
                

Severity: Low

Resolution: Fixed in Cloudera Manager 4.0.2

Workaround: This issue occurs if the MySQL thread stack is too small.

To increase the MySQL thread stack:

Increase the thread_stack value in the my.cnf file to 256KB. The my.cnf file is normally located in /etc or /etc/mysql.

Restart the mysql service:

                  $ sudo service mysql restart
                

Restart the failed service(s) in the Cloudera Manager Admin Console.