Troubleshooting Installation Problems

The KMS user is not part of the nfast group on the host(s) running the Navigator HSM KMS backed by Thales HSM role.

You might have SELinux enabled.

Disable SELinux by running sudo setenforce 0 on the Cloudera Manager Server host. To disable it permanently, edit /etc/selinux/config.

You need to do some manual cleanup.

See Uninstalling Cloudera Manager and Managed Software.

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;

For more information, see Install and Configure MySQL for Cloudera Software.

You might have SELinux or iptables enabled.

Check /var/log/cloudera-scm-server/cloudera-scm-server.log on the Server host and /var/log/cloudera-scm-agent/cloudera-scm-agent.log on the Agent hosts. Disable SELinux and iptables.

You might have network connectivity problems.

Hostname mapping or permissions are not set up correctly.

• For hostname configuration, see Configure Network Names.
• For permissions, make sure the values you enter into the wizard match those you used when you configured the databases. 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 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), or localhost. For example, if you entered

  grant all on activity_monitor.* TO 'amon_user'@'%' IDENTIFIED BY 'amon_password';

  the value you enter for the database hostname can be either the FQDN or localhost.

MySQL binlog format problem.

Set binlog_format=mixed in /etc/my.cnf. For more information, see this MySQL bug report. See also Step 4: Install and Configure Databases.

Java might not be installed or might be installed at a custom location.

See Configuring a Custom Java Home Location for more information on resolving this issue.

The MySQL thread stack is too small.

1. Update the thread_stack value in my.cnf to 256KB. The my.cnf file is normally located in /etc or /etc/mysql.
2. Restart the mysql service: $ sudo service mysql restart
3. Restart Activity Monitor.

The binlog_format is not set to mixed.

Modify the mysql.cnf file to include the entry for binlog format as specified in Install and Configure MySQL for Cloudera Software.

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 6 and CDH 6, then uninstall Cloudera Manager and CDH, and then attempt to install CDH 5 and Cloudera Manager 5, incorrect cached information might result in the installation of an incompatible version of the Oracle JDK.

Clear information in the yum cache:

1. Connect to the CDH host.
2. Execute either of the following commands:

   yum --enablerepo='*' clean all

   or

   sudo rm -rf /var/cache/yum/cloudera*

3. After clearing the cache, proceed with installation.

PostgreSQL versions 9 and higher require special configuration for Hive because of a backward-incompatible change in the default value of the standard_conforming_strings property. Versions up to PostgreSQL 9.0 defaulted to off, but starting with version 9.0 the default is on.

You have not granted execute permission to sys.dbms_crypto.

Run GRANT EXECUTE ON sys.dbms_crypto TO nav;, where nav is the user of the Navigator Audit Server database.