Thank you for the quick response.... yet again! ... 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

If you use CM you don't need to use the Hue safety valve. Make sure the Trift Server is added and started Make sure in the Hue configuration that the HBase service and the HBase thrift service are checked Restart Hue and that's it! Romain ... View more

Not an issue Mshirley, many thanks for your comments.   To be honest, I didn't check the cloudera-scm-agent logs after the restart so cannot say whether there were any errors reported. I'll keep that in mind next time onwards.   Also, /opt/cloudera/parcels directory contained 2 files - one was named CDH (a link to the CDH5.3 directory, I suppose) and the actual CDH5.3xxxx directory (sorry, cannot recollect the exact name) which contained the /lib /bin and several other parcel directories . And yes, we did try deactivating the old parcel before downloading the new one. Unfortunately, nothing worked.   Around the same time, we also did a reboot and noticed that one of the nodes did not come up. As a result, we were forced to do the re-installation again.  ... View more