Cannot connect to Cloudera Manager, not listening on port 7180

Here's what to look for, and a possible solution - give it more memory...

Check the status of the cloudera-scm-server service using [depending on your flavour of linux]

$ sudo service cloudera-scm-server status

OR

$ sudo systemctl status cloudera-scm-server

Look for the status - Active: active (running) But if you find - Active: active (exited)you may have a problem during the startup of the cloudera-scm-server.

In which case, look at the log files for cloudera-scm-server

$sudo ls -l /var/log/cloudera-scm-server$sudo cat /var/log/cloudera-scm-server/cloudera-scm-server.out JAVA_HOME=/usr/java/jdk1.7.0_67-clouderaJava HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x000000078dc58000, 265809920, 0) failed; error='Cannot allocate memory' (errno=12)## There is insufficient memory for the Java Runtime Environment to continue.# Native memory allocation (malloc) failed to allocate 265809920 bytes for committing reserved memory.# An error report file with more information is saved as:# /tmp/hs_err_pid831.log[ec2-user@ip-172-31-31-166 ~]$ sudo tail -100 /var/log/cloudera-scm-server/cloudera-scm-server.outJAVA_HOME=/usr/java/jdk1.7.0_67-clouderaJava HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x000000078dc58000, 265809920, 0) failed; error='Cannot allocate memory' (errno=12)

Use the command top to indicate how much memory is available to your system.

Possible solution - have a look at this discussion at Cloudera forum

In this case the java heap size was too small.

As we see that heap was exhausted, assuming this is not a memory leak or something of the sort, Cloudera Manager may need more heap to operate. This can be configured in: /etc/default/cloudera-scm-server You could, for instance, change "-Xmx2G" to "-Xmx3G" or "-Xmx4G" If the problem still happens, perhaps the heap dumps will yeild some clues.

I'd suggest you tail the logs. If you are using the free tier, cloudera manager will take a while to come up... possibly up to 5 minutes or more after you start the cloudera-scm-server.
The logs should show if there are any errors, possibly issues with memory allocation since the free tier servers have limited memory available. The little snippet of log entries looks fine and typical - it will go through a long list of processes before the UI comes up on 7180.

Also while that is going on, run top or even free -g to see how much resources are being used - particularly memory.

I was having the exact same issue, cannot hit the CM login using public DNS or IP on port 7180.

Following steps will help you :

iptables stopped (service iptables stop)  SELinux disabled (got to /etc/selinux/config and disbaled the selinux)   curl/wget localhost:7180 works (check the curl status)  ufw allow 7180  service httpd status should be running.  check va/log/cloudera-scm-server log : if any error found then troubleshoot the error      cloudera-scm-server status (should be running state)netstat -nap | grep 7180 returns  (if running other service then kill it)

telnet localhost 7180 (should be connected)