Support Questions
Find answers, ask questions, and share your expertise

Who agreed with this topic

cloudera manager repo always points to the internet

Rising Star

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?
 
 
Who agreed with this topic