You will then use CM to configure you "other" host, once its started...  dont pre-install any packages on it. ... View more

Ok so at this point I need to clarify, there is no valid reason to install the openJDK, generally speaking we only support the oracle JDK.   IMHO there is something that has taken place up to this point that is preventing proper installation, perhaps things failed initially as the VM you are using failed to finish critical DB setup steps due to not having enough memory.   IMHO really starting over with a fresh CentOS 6.4 or 6.5 VM makes sense at this point.   Once that VM is created make sure you have followed the "requirements" section of our installation guide with regard to the proper configuraiton of networking on your VM, I suggest setting up bridged networking in your VM software.   http://www.cloudera.com/content/cloudera/en/documentation/cloudera-manager/v5-latest/Cloudera-Manager-Installation-Guide/cm5ig_cm_requirements.html   Then download the simple installler and follow the path A installation steps, using the embedded postgres DB.  This is detailed here in the section titled " Download and Run the Cloudera Manager Server Installer"  http://www.cloudera.com/content/cloudera/en/documentation/cloudera-manager/v5-latest/Cloudera-Manager-Installation-Guide/cm5ig_install_path_A.html   ... View more

No, that should not be necessary. Are there error messages in the cloudera manager logs? Exceptions maybe? ... View more

Ok at this point I would suggest reviewing the "requirements" section, here.   http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM5/latest/Cloudera-Manager-Installation-Guide/cm5ig_cm_requirements.html   Also realize you need memory for CDH, so running the VM at a minimum of 4GB memory is necessary. The issue you are seeing is because there is not enough memory, Cloudera Manager and CDH are memory intensive applicaitons.   The JAVA_HOME error message you are seeing is due to this (the message is a false indication of the problem, as I stated in my previous note.     ... View more

OK so realize NONE of this should be necessary, and this is not normal to need to configure things this way.  It is not necessary to have to set JAVA_HOME.   I think we need to focus on this part of the message, rather than the JAVA_HOME message which appears to be a false-positive error.   INFO [JvmPauseMonitor:debug.JvmPauseMonitor@236] Detected pause in JVM or host machine (e.g. a stop the world GC, or JVM not scheduled): paused approximately 1024ms: no GCs detected.   How much memory is configured for your VM you are attempting to run things on?  How much physical memory does the system you are running the VM on have?   It appears the 1.7 openJDK has been installed as well, which is alongside of the oracle JDK on the system.   What do you get for the following commands on the system:   # ls -l /usr/java # yum list installed "*jdk*" Thanks Todd           ... View more

you can set "JAVA_HOME" in /etc/defaults/cloudera-scm-server   add to the end of the file   export JAVA_HOME=/usr/java/jdk1.7.0_55 ... View more

Why are you using such an outdated RHEL release in the first place?   Please see response from our team in the message entitled:   Re: Cloudera Manager fails to install on RHEL 5.x ... View more

make sure forward and reverse lookup are working correctly on all nodes (per discussion here)   http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM5/latest/Cloudera-Manager-Installation-Guide/cm5ig_cm_requirements.html#cmig_topic_4_3_3_unique_1   Make sure you deployed client configurations through CM after enabling kerberos and restarting services too (probably not the issue, but important to remember)   If management services were not down when you enabled kerberos, it might be necessary to kill them, try to stop them and all cluster services first, and then check if they came down clean with a ps -ef | grep java | grep cloudera ... View more

Specifically the networking and security discussion here (along with the requirements for everything else in the parent section of the documentation to this link).   http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM5/latest/Cloudera-Manager-Installation-Guide/cm5ig_cm_requirements.html#cmig_topic_4_3_3_unique_1   Make sure the hostname is fully qualified domain name and not just hostname.   Make sure the hostname value is not present on the loopback (127.0.0.1) line of the /etc/hosts file   check if you are getting the fqdn for hostname (without the -f).  vi /etc/sysconfig/network to double check what the system has   python -c "import socket; print socket.getfqdn(); print socket.gethostbyname(socket.getfqdn())"    and then to verify    getent hosts (ip address returned).   The python command resolves both forward and reverse, the getent hosts (ip address returns) verifies it back to you.   Make sure iptables and selinux are disabled. (/etc/sysconfig/selinux)    Verify what the 'agents' have configured for the CM host in /etc/cloudera-scm-agent/config.ini   There are also many forum posts for CM that discuss agent issues as well to search through.   Todd     ... View more