I solved the issue. The logs weren't showing because the SELinux is enabled  - I don't know where's the relation between them. Once I enabled them I saw the reason for hte failure. In my previous attempts to run the server I have run it as root directly from a low level script (that doesn't set java memory correctly) and it failed it OutOfMemory. This caused creation of a *.hprof file owned by root. Then on the consecutive try to run the server it wasn't able to read the hprof file (again why the server need to read the heap dump?!) and that's why it was failing. The solution was to move/remove the *.hprof from /usr/share/cmf ... View more

Hi, I've faced the same issue except the fact I am nott able to resolve it in any way. I hit the issue when I upgraded the ClouderaManager from 5.3.2 to latest (5.4.3). I followed the procedure described at http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_ag_upgrade_cm5.html and after the upgrade I am not able to start the cloudera-scm-server. It starts and when I check its status it says "cloudera-scm-server dead but pid file exists". I remove "/var/run/cloudera-scm-server.pid" and try to start the server again and then it starts, and if I check the status - "cloudera-scm-server dead but pid file exists". I checked the cloudera-scm-server-db is running and I was able to connect with "psql -U scm -p 7432 -h localhost" and all the data is there. The cloudera-scm-agent is also running without any issue. I cannot diagnose what's causing the issues since there's isnt't even a single log entry neither in /var/log/cloudera-scm-server/cloudera-scm-server.out, nor in /var/log/cloudera-scm-server/cloudera-scm-server.log. I run tail -f for both of the files and not a single line during server start. I would be grateful if someone can help me since I am stuck in the middle of an upgrade.   ... View more