Support Questions

Find answers, ask questions, and share your expertise

Not able to access Cloudera Manager Web UI

Explorer

Hi,

 

I have successfully installed Cloudera Manager on RHEL 7 Azure VM but I'm not able to access the web ui. I have tried after adding 7180 port as inbound port in Network Security Group in azure portal.

1 ACCEPTED SOLUTION

Expert Contributor

@tanishq1197 

 

When you see this log entry, the Cloudera Manager Admin Console is ready:

INFO WebServerImpl:com.cloudera.server.cmf.WebServerImpl: Started Jetty server

 

Try to access the CM API instead, you should use the login credentials 

curl -u <username>:password http://<cm_host>:<port>/api/v19/clusters

 

Are you able to reach out to the CM server from your desktop?

#ping cmserverhost

#telnet cmserverhost port

 

 

View solution in original post

4 REPLIES 4

Explorer

I'm using Windows 7(firewall and proxy disabled) and accessing the RHEL 7 VM through putty. I'm getting connection refused on using curl command. 

 

Here's the output for service cloudera-scm-server status-

/etc/init.d/cloudera-scm-server: line 109: pstree: command not found
● cloudera-scm-server.service - LSB: Cloudera SCM Server
Loaded: loaded (/etc/rc.d/init.d/cloudera-scm-server; bad; vendor preset: disabled)
Active: active (exited) since Tue 2020-07-07 08:52:42 UTC; 19min ago
Docs: man:systemd-sysv-generator(8)
Process: 921 ExecStart=/etc/rc.d/init.d/cloudera-scm-server start (code=exited, status=0/SUCCESS)

Jul 07 08:52:37 vm2 systemd[1]: Starting LSB: Cloudera SCM Server...
Jul 07 08:52:37 vm2 cloudera-scm-server[921]: /etc/rc.d/init.d/cloudera-scm-server: line 109: pstree: command not found
Jul 07 08:52:37 vm2 su[963]: (to cloudera-scm) root on none
Jul 07 08:52:42 vm2 cloudera-scm-server[921]: Starting cloudera-scm-server: [ OK ]
Jul 07 08:52:42 vm2 systemd[1]: Started LSB: Cloudera SCM Server.

 

Here's the output for  netstat -na | grep 7180-

tcp 0 0 0.0.0.0:7180 0.0.0.0:* LISTEN

 

I have also checked  /var/log/cloudera-scm-server/cloudera-scm-server.log and there doesn't seem to be any errors. 

 

Any help is appreciated.

Explorer

Correction : curl output

 

curl -i http://vm2:7180 gives following output-

 

HTTP/1.1 200 OK
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Set-Cookie: CLOUDERA_MANAGER_SESSIONID=6zye6pcmlwjzmidtgt9x0ac1;Path=/;HttpOnly
Content-Type: text/html; charset=utf-8
Last-Modified: Sat, 18 May 2019 06:13:36 GMT
Content-Length: 63
Accept-Ranges: bytes
Cache-Control: max-age=3600,public
Server: Jetty(6.1.26.cloudera.4)

<head><meta http-equiv="refresh" content="0;url=/cmf/"></head>

Expert Contributor

@tanishq1197 

 

When you see this log entry, the Cloudera Manager Admin Console is ready:

INFO WebServerImpl:com.cloudera.server.cmf.WebServerImpl: Started Jetty server

 

Try to access the CM API instead, you should use the login credentials 

curl -u <username>:password http://<cm_host>:<port>/api/v19/clusters

 

Are you able to reach out to the CM server from your desktop?

#ping cmserverhost

#telnet cmserverhost port

 

 

New Contributor

For this u dont need to add any properties..

very simple just add the Inbound roles..

like Http,Https and most important 7180 port no u should add this inside Azure NSG (inbound rule)..

 

I have faced the same issue ..But Now i can get the cloudera Ui...

Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.