Attempting to connect to Cloudera Manager

[#1]

Hi, Cloud Manager is struck with below message. Please do the needful.

"Attempting to connect to Cloudera Manager... By default, the Cloudera QuickStart VM runs Cloudera's Distribution including Apache Hadoop (CDH) under Linux's service and configuration management. If you wish to migrate to Cloudera Manager, you must run one of the following commands. To use Cloudera Express (free), run Launch Cloudera Express on the Desktop. This requires at least 8 GB of RAM and at least 2 virtual CPUs. To begin a 60-day trial of Cloudera Enterprise with advanced management features, run Launch Cloudera Enterprise (trial) on the Desktop. This requires at least 10 GB of RAM and at least 2 virtual CPUs. Be aware that after rebooting, it may take several minutes before Cloudera Manager has started all of the services it manages and is ready to accept connects from clients."

Thanks inadvance.

[#2]

Hi @PaniG,

Can you provide what kind of resources the VM has assigned to it as well as the overall system resources? For instance a common issue is allocating too many of the system resources to the VM to meet requirements. For instance a system with 8GB of RAM cannot allocate 8 GB to the VM as it needs to reserve some of it to run the operating system.  

[#3]

Hi Jervis,

Thanks for your reply

Please find the below screenshot for assigned system resources.

.

------

when i check with netstat for 7180, it is showing nothing.

[root@quickstart ~]# netstat -nap |grep 7180
[root@quickstart ~]# .

------

cloudera-scm-server status :

[root@quickstart ~]# sudo service cloudera-scm-server status
cloudera-scm-server (pid 5376) is running...
[root@quickstart ~]#

-------

I tried from curl

curl 12.0.0.1:7180
curl: (7) couldn't connect to host

------

[root@quickstart ~]# cat /etc/hosts
# This file is generated by /usr/bin/cloudera-quickstart-ip, which is invoked
# by /etc/init.d/cloudera-quickstart-init. If you wish to change the way that
# /etc/hosts is generated, you may edit /etc/init.d/cloudera-quickstart-init
# and hard-code a different IP address as a parameter to
# /usr/bin/cloudera-quickstart-ip, or you may comment out that line and manage
# /etc/hosts yourself.

127.0.0.1 localhost localhost.domain
10.0.2.15 quickstart.cloudera quickstart

-----

root@quickstart ~]# hostname -f
quickstart.cloudera

------

[root@quickstart ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:27:9D:13:B8
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3669 errors:0 dropped:0 overruns:0 frame:0
TX packets:2636 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3371537 (3.2 MiB) TX bytes:243202 (237.5 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:3356 errors:0 dropped:0 overruns:0 frame:0
TX packets:3356 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1332086 (1.2 MiB) TX bytes:1332086 (1.2 MiB)

Thanks,

Pani.

[#4]

Ah, I was hoping for a simple fix. I get lucky some times and it is a resource allocation issue. At this point we will have to wait for someone more experienced to chime in. 

[#5]

Hi Everyone,

This is Venkata Surya Prakash, I am new to this cloudera community channel as well as to this technology. I have seen the above query regarding the connection issues of Cloudera Manager, When I see that, I just recollected all my tries on fixing the same issue when I was a bootcamper.

And here are the steps when you face this issue:

• Firstly, Make sure that you open the Terminal and execute the following commands;

  • [cloudera@quickstart ~]$ mysql -uroot -pcloudera

    Welcome to the MySQL monitor.  Commands end with ; or \g.

    Your MySQL connection id is 234

    Server version: 5.1.73 Source distribution

    Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.

    Oracle is a registered trademark of Oracle Corporation and/or its

    affiliates. Other names may be trademarks of their respective

    owners.

    Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

    mysql> CREATE USER 'oozie'@'localhost' IDENTIFIED BY 'cloudera';

    Query OK, 0 rows affected (0.00 sec)

    mysql> GRANT ALL PRIVILEGES ON *.* TO 'oozie'@'localhost' WITH GRANT OPTION;

    Query OK, 0 rows affected (0.00 sec)

    mysql> CREATE USER 'cm'@'localhost' IDENTIFIED BY 'cloudera';

    Query OK, 0 rows affected (0.00 sec)

    mysql> GRANT ALL PRIVILEGES ON *.* TO 'cm'@'localhost' WITH GRANT OPTION;

    Query OK, 0 rows affected (0.00 sec)

• Secondly, close the whole setup i.e, The cloudera instance from the VMware and even close your VMware, as it is always recommended to start a new session soon after some amendments to the instance.
• Thirdly, start your cloudera setup in VMware and execute the below command in the Terminal.
  • sudo /home/cloudera/cloudera-manager --force --express (Note: If you use enterprise addison then replace --express with --enterprise)
  • After executing the above command, have some patinece and watch the terminal (CDH will shutdown and automatically restarts on it own). You will get a success!!! message.
• Finally, copy the URL just below the success!! message and paste in the mozilla browser, and then hit enter. It will ask for logins both the username and passwords are: cloudera. Thats all, and wait for a few seconds cloudera manager will bootup.

Please find the attached images.