The solution worked for me, and my issue was due to not completing the Cloudera Manager install in the one window. I thought that I could restart from where I left off, but had nothing but issues. I had tried to install Hive again and also Hue, but still had issues, so i suspect that there may have been issues prior to these, and there were dependencies.   The solution appears to be a good way to clean out and rebuild a cluster, for probably multiple type issues, and it does not really take that long to complete.  ... View more

You can stop the services with the following: (another option is just to use restart, I like stop, verify all processes are gone/down then do the start when needed.)     Cloudera Manager Server: (stop agent, stop the server, stop database if using local postgres default ) sudo /sbin/service cloudera-scm-agent stop sudo /sbin/service cloudera-scm-server stop sudo /sbin/service cloudera-scm-server-db stop   Do the reverse to start:   sudo /sbin/service cloudera-scm-server-db start sudo /sbin/service cloudera-scm-server start sudo /sbin/service cloudera-scm-agent start   On the other nodes of  your servers in the cluster just stop/restart the agent. sudo /sbin/service cloudera-scm-agent stop sudo /sbin/service cloudera-scm-agent start or sudo /sbin/service cloudera-scm-agent restart     You can do the following to get a status of the services as well.   sudo /sbin/service cloudera-scm-server-db status sudo /sbin/service cloudera-scm-server status sudo /sbin/service cloudera-scm-agent status   May want to do a ps -ef |grep cloudera-scm to verify all processes are stopped on each server. ... View more

Hi,   Im happy to set up a separate post, but was hoping you could pick this up here. Im having a similar problem with Spark and Hue on CDM.   I have a running CDM 5.7.1 cluster on Ubuntu 14.04, with all services working fine (apart from spark and impala).   It apears that the spark hostory servers and gateways are installed, but I cant activate Spark in Standalone or Spark on Yarn. In the parcels section I am getting errors across a number of services:   Error for parcel SPARK-0.9.0-1.cdh4.6.0.p0.98-trusty : Parcel not available for OS Distribution UBUNTU_TRUSTY. Error for parcel SOLR-1.3.0-1.cdh4.5.0.p0.9-trusty : Parcel not available for OS Distribution UBUNTU_TRUSTY. Error for parcel IMPALA-2.1.0-1.impala2.0.0.p0.1995-trusty : Parcel not available for OS Distribution UBUNTU_TRUSTY. Error for parcel ACCUMULO-1.4.4-1.cdh4.5.0.p0.65-trusty : Parcel not available for OS Distribution UBUNTU_TRUSTY. Having checked, this appears to mean that there isnt a Ubuntu Trusty version of the above parcels.   Can you confirm if this is the case.   If so, can I install the components via apt-get:   sudo apt-get install spark-core spark-master spark-worker spark-history-server spark-python as described in this link for CDM 5.4.x:   http://www.cloudera.com/documentation/enterprise/5-4-x/topics/cdh_ig_spark_install.html   Any guidance on this would be appreciated.   After installing spark, I'd like to activate the Hue Spark Notebook, but can see that in Hue app_blacklist is set to:   app_blacklist ['spark', 'zookeeper', 'security']   I have removed spark and zookeeper from the app_blacklist leaving 'security' and have restarted the Hue service, and refreshed Hue web UI, I can see only 'security' in the Hue.ini dump but still dont have any spark notebook available. This may be due to the dependency on Spark Parcels being installed.   If I have to re-install the cluster onto Linux RedHat to activate the Spark Parcels that could be a possibility, but I'd prefer to get everything working on ubuntu 14.04 first if possible.   Any guidance on which route to take would be appreciated.   Regards   natdacruz        ... View more

Sidharth,   Please create a new thread for a new issue, re-using an old thread could lead to strange comments when people make assumptions based on irrelevant information.   For your issue: EPERM means that the OS is not allowing you to create the NM recovery DB and you have recovery turned on. Check the access to the recovery DB directory that you have configured.   Wilfred ... View more

I followed the steps to upgrade the CM-Version and solved the "problem".   http://www.cloudera.com/documentation/enterprise/5-5-x/topics/cm_ag_upgrade_cm5.html?scroll=cmig_topic_9_4   Thank you, Darren! ... View more

It worked.   Thanks Darren! ... View more

I ran into this error, and it was caused by running out of heap size for Nodemanager.  I increased the heap, and Yarn came up without errors.   ... View more

Hi Darren, We had a similar problem while installing Cloudera Manager 5.5. The cloudera-scm-server process was failing  after a few seconds. The scm-server.out file indicated that the log4j file was not available. We uninstalled CM and tried re-installing it again; however, the problem persisted. As per your suggestion, we manually created a file log4j.properties and added the contents. We then 1) Stopped cloudera-scm-server-db 2) restarted postgresql 3) started cloudera-scm-server-db 4) started cloudera-scm-server   and it worked!! We were immediately able to access CM via the browser. Thanks a lot for your help.   Regards, Yogesh ... View more