Troubleshooting Installation and Upgrade Problems
For information on known issues, see http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM5/latest/Cloudera-Manager-Release-Notes/cm5rn_known_issues.html.
|"Failed to start server" reported by cloudera-manager-installer.bin. /var/log/cloudera-scm-server/ cloudera-scm-server.log contains a message beginning Caused by: java.lang.ClassNotFoundException: com.mysql.jdbc.Driver...||You may have SELinux enabled.||Disable SELinux by running sudo setenforce 0 on the Cloudera Manager Server host. To disable it permanently, edit /etc/selinux/config.|
|Installation interrupted and installer won't restart.||You need to do some manual cleanup.||See Uninstalling Cloudera Manager and Managed Software .|
|Cloudera Manager Server fails to start. Server is configured to use a MySQL database to store information about service configuration.||Tables may be configured with the ISAM engine.||Make sure that the InnoDB engine is configured, not the MyISAM engine. To check what engine your tables are using, run the following command from the MySQL shell: mysql> show table status;|
|Agents fail to connect to server. Error 113 ('No route to host') in cloudera-scm-agent.log.||You may have SELinux or iptables enabled.||Check /var/log/cloudera-scm-server/cloudera-scm-server.log on the Server system and /var/log/cloudera-scm-agent/cloudera-scm-agent.log on the Agent system(s). Disable SELinux and iptables.|
|Some cluster hosts do not appear when you click Find Hosts in install or update wizard.||You may have network connectivity problems.||
|"Access denied" in install or update wizard during database configuration for Activity Monitor, Reports Manager, or Service Monitor.||Hostname mapping or permissions are incorrectly set up.|
|Activity Monitor, Reports Manager, or Service Monitor databases fail to start.||MySQL binlog format problem.||Set binlog_format=mixed in /etc/my.cnf. For more information, see this MySQL bug report. See also Cloudera Manager and CDH Databases.|
|You have upgraded the Cloudera Manager Server, but now cannot start services.||You may have mismatched versions of the Cloudera Manager Server and Agents.||Make sure you have upgraded the Cloudera Manager Agents on all host hosts. (The previous version of the Agents will heartbeat with the new version of the Server, but you can't start HDFS and MapReduce with this combination.)|
|Cloudera services fail to start.||Java may not be installed or may be installed at a custom location.||See Using Custom Java Home Locations for more information on resolving this issue.|
|The Service Monitor, Activity Monitor, or Host Monitor display a status of BAD in the Cloudera Manager Admin Console. The log file contains the following message: ERROR 1436 (HY000): Thread stack overrun: 7808 bytes used of a 131072 byte stack, and 128000 bytes needed. Use 'mysqld -O thread_stack=#' to specify a bigger stack.||The MySQL thread stack is too small.||Update the thread_stack value in my.cnf 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 using the Cloudera Manager Admin Console.
|The Service Monitor or Activity Monitor agents fail to start. Logs contain the error read-committed isolation not safe for the statement binlog format.||The binlog_format is not set to mixed.||Modify the mysql.cnf file to include the entry for binlog format as specified in MySQL Database.|
|Attempts to reinstall older versions of CDH or Cloudera Manager using yum fails.||It is possible to install, uninstall, and reinstall CDH and Cloudera Manager. In certain cases, this does not complete as expected. If you install Cloudera Manager 5 and CDH 5, then uninstall Cloudera Manager and CDH, and then attempt to install CDH 4 and Cloudera Manager 4, incorrect cached information may result in the installation of an incompatible version of the Oracle JDK.||Clear information in the yum cache:
Checking Database Hostnames
The value you enter into the wizard as the database hostname must match the value you entered for the hostname (if any) when you configured the database.
For example, if you entered the following for the Activity Monitor database:
grant all on activity_monitor.* TO 'amon_user'@'localhost' IDENTIFIED BY 'amon_password';
the value you enter here for the database hostname must be localhost. On the other hand, if you had entered the following when you created the database
grant all on activity_monitor.* TO 'amon_user'@'myhost1.myco.com' IDENTIFIED BY 'amon_password';
the value you enter here for the database hostname must be myhost1.myco.com. If you did not specify a host, or used a wildcard to allow access from any host, you can enter either the fully-qualified domain name (FQDN) here, or localhost. For example, if you entered
grant all on activity_monitor.* TO 'amon_user'@'%' IDENTIFIED BY 'amon_password';
the value you enter here for the database hostname can be either the FQDN or localhost. Similarly, if you entered
grant all on activity_monitor.* TO 'amon_user' IDENTIFIED BY 'amon_password';
the value you enter here for the database hostname can be either the FQDN or localhost.