Reply
aks
New Contributor
Posts: 4
Registered: ‎04-16-2018

Automating cloudera manager install not working

Hi ,

 

I was trying to install Cloudera manager on Ubuntu 
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial.

 

With help of below url.

1. wget http://archive.cloudera.com/cdh5/one-click-install/precise/amd64/cloudera-manager-repository_5.0_all...
2. dpkg -i cloudera-manager-repository_5.0_all.deb

 

**************

3. wget http://archive.cloudera.com/cm5/installer/latest/cloudera-manager-installer.bin
4. chmod u+x cloudera-manager-installer.bin
5. ./cloudera-manager-installer.bin

 

Once i had done all the above four staps for installing the cloudera on ubuntu, not able to open cloudera-manager gui with port 7180. 

 

After that i stop the firewall but still not able to open, beacuse there is not any service which is runing on 7180 port number.

 

----------

Thanks

Amit

 

Expert Contributor
Posts: 127
Registered: ‎01-08-2018

Re: Automating cloudera manager install not working

Have you checked that Cloudera manager has been started?

# systemctl status cloudera-scm-server

and

# systemctl status cloudera-scm-server-db

The last one is for the embeded DB (skip it, if you have configured an external db)

 

The output of this command will give you a brief description of the status.

You can try to start it  and check the logs under "/var/log/cloudera-scm-server/"

 

aks
New Contributor
Posts: 4
Registered: ‎04-16-2018

Re: Automating cloudera manager install not working

Both services are started
And in log only have details of services are started .
Highlighted
Expert Contributor
Posts: 127
Registered: ‎01-08-2018

Re: Automating cloudera manager install not working

How did you check that no process is running on port 7180? Can you post the command and the output?

Also, if your /etc/hosts file is not correct, the Cloudera Manager may not start (you said that logs are ok), just take a second look.

aks
New Contributor
Posts: 4
Registered: ‎04-16-2018

Re: Automating cloudera manager install not working

root@ip-172-16-10-10:~# netstat -tunlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1341/sshd
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 20690/postgres
tcp 0 0 0.0.0.0:7432 0.0.0.0:* LISTEN 28976/postgres
tcp6 0 0 :::22 :::* LISTEN 1341/sshd
tcp6 0 0 :::7432 :::* LISTEN 28976/postgres
udp 0 0 0.0.0.0:68 0.0.0.0:* 962/dhclient
root@ip-172-16-10.10:~#
---
/etc/host file

root@ip-172-16-10-10::~# cat /etc/hosts
127.0.0.1 localhost

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
root@ip-172-16-10.10:~#
Expert Contributor
Posts: 127
Registered: ‎01-08-2018

Re: Automating cloudera manager install not working

Based on your prompt "root@ip-172-16-10-10" I see that you have defined a hostname "ip-172-16-10-10".

This hostname/IP is not in your /etc/hosts file. Run "hostname -f" to get the full hostname and add the following in your /etc/hosts file.

172.16.10.10     {full hostname} {hostname alias, probably ip-172-16-10-10}

aks
New Contributor
Posts: 4
Registered: ‎04-16-2018

Re: Automating cloudera manager install not working

[ Edited ]

root@ip-172-16-10-10:~# hostname -f
ip-172-16-10-10.us-west-2.compute.internal
root@ip-172-16-10-10:~# cat /etc/hosts
127.0.0.1 localdomain localhost
172.16.10.10 ip-172-16-10-10.us-west-2.compute.internal ip-172-16-10-10

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
root@ip-172-16-10-10:~# netstat -tunlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1162/sshd
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 1334/postgres
tcp 0 0 0.0.0.0:7432 0.0.0.0:* LISTEN 1372/postgres
tcp6 0 0 :::22 :::* LISTEN 1162/sshd
tcp6 0 0 :::7432 :::* LISTEN 1372/postgres
udp 0 0 0.0.0.0:68 0.0.0.0:* 996/dhclient
root@ip-172-16-10-10:~# systemctl status cloudera-scm-server
● cloudera-scm-server.service - LSB: Cloudera SCM Server
Loaded: loaded (/etc/init.d/cloudera-scm-server; bad; vendor preset: enabled)
Active: active (exited) since Tue 2018-04-17 10:24:38 UTC; 19h ago
Docs: man:systemd-sysv-generator(8)
Process: 1217 ExecStart=/etc/init.d/cloudera-scm-server start (code=exited, status=0/SUCCESS)
Tasks: 0
Memory: 0B
CPU: 0

Apr 17 10:24:33 ip-172-16-10-10 systemd[1]: Starting LSB: Cloudera SCM Server...
Apr 17 10:24:33 ip-172-16-10-10 su[1307]: Successful su for cloudera-scm by root
Apr 17 10:24:33 ip-172-16-10-10 su[1307]: + ??? root:cloudera-scm
Apr 17 10:24:33 ip-172-16-10-10 su[1307]: pam_unix(su:session): session opened for user cloudera-scm by (uid=0)
Apr 17 10:24:38 ip-172-16-10-10 cloudera-scm-server[1217]: Starting cloudera-scm-server: * cloudera-scm-server started
Apr 17 10:24:38 ip-172-16-10-10 systemd[1]: Started LSB: Cloudera SCM Server.
root@ip-172-16-10-10:~# systemctl status cloudera-scm-server-db.service
● cloudera-scm-server-db.service - LSB: Cloudera SCM Server's Embedded DB
Loaded: loaded (/etc/init.d/cloudera-scm-server-db; bad; vendor preset: enabled)
Active: active (running) since Tue 2018-04-17 10:24:33 UTC; 19h ago
Docs: man:systemd-sysv-generator(8)
Process: 1173 ExecStart=/etc/init.d/cloudera-scm-server-db start (code=exited, status=0/SUCCESS)
Tasks: 6
Memory: 37.6M
CPU: 9.373s
CGroup: /system.slice/cloudera-scm-server-db.service
├─1372 /usr/lib/postgresql/9.5/bin/postgres -D /var/lib/cloudera-scm-server-db/data -k /var/run/cloudera-scm-server-db
├─1377 postgres: checkpointer process
├─1378 postgres: writer process
├─1379 postgres: wal writer process
├─1380 postgres: autovacuum launcher process
└─1381 postgres: stats collector process

Apr 17 10:24:33 ip-172-16-10-10 systemd[1]: Starting LSB: Cloudera SCM Server's Embedded DB...
Apr 17 10:24:33 ip-172-16-10-10 runuser[1341]: pam_unix(runuser:session): session opened for user cloudera-scm by (uid=0)
Apr 17 10:24:33 ip-172-16-10-10 runuser[1341]: pam_unix(runuser:session): session closed for user cloudera-scm
Apr 17 10:24:33 ip-172-16-10-10 runuser[1360]: pam_unix(runuser:session): session opened for user cloudera-scm by (uid=0)
Apr 17 10:24:33 ip-172-16-10-10 runuser[1360]: pam_unix(runuser:session): session closed for user cloudera-scm
Apr 17 10:24:33 ip-172-16-10-10 runuser[1368]: pam_unix(runuser:session): session opened for user cloudera-scm by (uid=0)
Apr 17 10:24:33 ip-172-16-10-10 runuser[1368]: pam_unix(runuser:session): session closed for user cloudera-scm
Apr 17 10:24:33 ip-172-16-10-10 cloudera-scm-server-db[1173]: * Cloudera manager database started
Apr 17 10:24:33 ip-172-16-10-10 systemd[1]: Started LSB: Cloudera SCM Server's Embedded DB.
root@ip-172-16-10-10:~#

Expert Contributor
Posts: 127
Registered: ‎01-08-2018

Re: Automating cloudera manager install not working

According to the output of "systemctl status cloudera-scm-server" the service is down.

Have you checked both "cloudera-scm-server.out" and "cloudera-scm-server.log"?

Can you provide those files?

Announcements