I am building a cluster with 3 nodes. the cloudera manager is able to successfully install everything on 2 nodes but one of them fails   When I click on details I can see   Configuring Cloudera Manager Agent... BEGIN grep server_host=155.17.148.40 /etc/cloudera-scm-agent/config.ini END (1) BEGIN sed -e 's/\(server_host=\).*/\1155.17.148.40/' -i /etc/cloudera-scm-agent/config.ini END (0) scm agent configured Starting Cloudera Manager Agent... BEGIN /sbin/service cloudera-scm-agent status | grep running END (1) BEGIN /sbin/service cloudera-scm-agent start Starting cloudera-scm-agent: [FAILED] END (1) agent logs: BEGIN tail -n 50 /var/log/cloudera-scm-agent//cloudera-scm-agent.out | sed 's/^/>>/' >>/usr/lib64/cmf/agent/src/cmf/agent.py:24: DeprecationWarning: the sha module is deprecated; use the hashlib module instead >> import sha >>/usr/lib64/cmf/agent/src/cmf/parcel.py:15: DeprecationWarning: the sets module is deprecated >> from sets import Set >>[17/Dec/2014 14:13:31 +0000] 9557 MainThread agent INFO SCM Agent Version: 5.2.1 >>[17/Dec/2014 14:13:31 +0000] 9557 MainThread agent ERROR Could not determine hostname or ip address; proceeding. >>Traceback (most recent call last): >> File "/usr/lib64/cmf/agent/src/cmf/agent.py", line 1854, in parse_arguments >> ip_address = socket.gethostbyname(fqdn) >>gaierror: [Errno -3] Temporary failure in name resolution >>usage: agent.py [-h] [--agent_dir AGENT_DIR     ... View more

I successfully installed the cloudera manager on my 1 server. I went into the http://nn1work:7180/cmf and am trying to build my cluster.   I choose the parcel based installation and it tries to install the software on my data nodes.   I get an error    validating format of repository file /tmp/scm_prepare_node.E7pvzQG6/repos/rhel6/cloudera-manager.repo  installing repository file /tmp/scm_prepare_node.E7pvzQG6/repos/rhel6/cloudera-manager.repo repository file /tmp/scm_prepare_node.E7pvzQG6/repos/rhel6/cloudera-manager.repo installed Refreshing package metadata... BEGIN yum clean all Loaded plugins: fastestmirror Cleaning repos: cloudera-manager Cleaning up Everything Cleaning up list of fastest mirrors END (0) BEGIN rm -Rf /var/cache/yum/x86_64 END (0) BEGIN yum makecache Loaded plugins: fastestmirror http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.2.1/repodata/repomd.xml: [Errno 12] Timeout on http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.2.1/repodata/repomd.xml: (28, 'connect() timed out!') Trying other mirror. Error: Cannot retrieve repository metadata (repomd.xml) for repository: cloudera-manager. Please verify its path and try again END (1) Installing cloudera-manager-agent package... BEGIN yum list installed cloudera-manager-agent Loaded plugins: fastestmirror Error: No matching Packages to list END (1) BEGIN yum info cloudera-manager-agent Loaded plugins: fastestmirror Determining fastest mirrors http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.2.1/repodata/repomd.xml: [Errno 12] Timeout on http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.2.1/repodata/repomd.xml: (28, 'connect() timed out!') Trying other mirror. Error: Cannot retrieve repository metadata (repomd.xml) for repository: cloudera-manager. Please verify its path and try again END (1) cloudera-manager-agent must have Version=5.2.1 and Build=109, exiting closing logging file descriptor   I can open the /etc/yum.repos.d/cloudera-manager.repo file and I can see that it is pointing to the internet. I edit this file and make the baseurl point to my local repository and then retry the failed install.   what the cloudera does is that it overwrites my cloudera-manager.repo file with a new one which is again pointing to the internet.   why is it doing that? how can I make the install use my customer cloudera repo rather than the one on the internet?     ... View more

My cloudera manager machine will not have access to the internet.   I have downloaded all the parcel files and manually uploaded them into the /opt/cloudera/parcels directory   [root@nn1work parcels]# pwd /opt/cloudera/parcels [root@nn1work parcels]# ll total 2995116 -rw-r--r-- 1 root root 1535130392 Dec 16 09:51 CDH-5.2.1-1.cdh5.2.1.p0.12-el5.parcel -rw-r--r-- 1 root root 1531811730 Dec 16 09:53 CDH-5.2.1-1.cdh5.2.1.p0.12-el6.parcel -rw-r--r-- 1 root root 42559 Dec 16 11:12 manifest.json [root@nn1work parcels]#     Now when I run my cloudera manager and try to build a cluster using parcels it says    Note: No parcels found from the configured repositories. Try adding a Custom Repository under More Options. Otherwise, you may only proceed with Use Packages.   When I click on more options I can see       So you can see that the directory for parcels is correct. but still it says no parcels can be found. Why?? ... View more

Hello,   I have download all cloudera rpms and the postgressql rpms in a directory   cloudera-manager-agent-5.2.1-1.cm521.p0.109.el6.x86_64.rpm cloudera-manager-daemons-5.2.1-1.cm521.p0.109.el6.x86_64.rpm cloudera-manager-server-5.2.1-1.cm521.p0.109.el6.x86_64.rpm cloudera-manager-server-db-2-5.2.1-1.cm521.p0.109.el6.x86_64.rpm postgresql-8.4.20-1.el6_5.x86_64.rpm postgresql-plperl-8.4.20-1.el6_5.x86_64.rpm postgresql-contrib-8.4.20-1.el6_5.x86_64.rpm postgresql-plpython-8.4.20-1.el6_5.x86_64.rpm postgresql-devel-8.4.20-1.el6_5.x86_64.rpm postgresql-pltcl-8.4.20-1.el6_5.x86_64.rpm postgresql-docs-8.4.20-1.el6_5.x86_64.rpm postgresql-server-8.4.20-1.el6_5.x86_64.rpm postgresql-libs-8.4.20-1.el6_5.x86_64.rpm postgresql-test-8.4.20-1.el6_5.x86_64.rpm postgresql-odbc-08.04.0200-1.el6.x86_64.rpm     Now I have done a createrepo on this and am running Python -M SimpleHTTPServer. I also have set my cloudera-manager.repo file to point this HTTP Server   I was succeful in doing   sudo yum install oracle-j2sdk1.7 sudo yum install cloudera-manager-daemons cloudera-manager-server     but when I try to install the database by   sudo yum install cloudera-manager-server-db-2   it says    --> Finished Dependency Resolution Error: Package: cloudera-manager-server-db-2-5.2.1-1.cm521.p0.109.el6.x86_64 (cloudera-manager) Requires: postgresql-server >= 8.4 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest   but you can see that I have copied the postgresql* rpms in the same directory. So why doesn't it just use them?     ... View more