CM/CDH 5.14 mirror issue

[#1]

Hi ,

Is there any probnlem in 5.14 mirror ,dwonload are getting fail frequently 

https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.14.0/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 503"
Trying other mirror.

Is this ok [y/N]: y
Downloading Packages:
https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.14.0/RPMS/x86_64/cloudera-manager-daemons-5.14...: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 503"
Trying other mirror.

Error Downloading Packages:
cloudera-manager-daemons-5.14.0-1.cm5140.p0.25.el6.x86_64: failure: RPMS/x86_64/cloudera-manager-daemons-5.14.0-1.cm5140.p0.25.el6.x86_64.rpm from cloudera-manager: [Errno 256] No more mirrors to try.

[#2]

Hi @MSharma,

I wonder if you hit a temporary outage. I just tried and it seems that the servers are up and I can download the fiels.  Can you try again now and let us know if you still have an issue?

Thanks!

[#3 · Accepted solution]

Correct the network issue. Or use the following workaround: Create a temporary local repository as per the following KB article: [1] Deploying a Custom Patch Parcel Using Cloudera Manager https://cloudera-portal.force.com/articles/KB_Article/Deploying-a-Custom-Patch-Parcel-Using-Cloudera...

[#4]

I am facing same issue with 5.14.1.

Installing cloudera-manager-agent package...

BEGIN yum list installed cloudera-manager-agent 
Loaded plugins: fastestmirror, langpacks 
Error: No matching Packages to list 
END (1)

[#5]

Can you please let us know the OS and version and the contents of your /cloudera-manager repo file?

cat /etc/redhat-release

cat /etc/yum.repos.d/cloudera-manager.repo

Also, the full error if possible.

[#6]

Hi,

Please find the details below.

[root@ansible-master ~]# cat /etc/centos-release
CentOS Linux release 7.2.1511 (Core)
[root@ansible-master ~]# cat /etc/yum.repos.d/cloudera-manager.repo
[cloudera-manager]
name = Cloudera Manager, Version 5.14.1
baseurl = https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.14.1/
gpgkey = https://archive.cloudera.com/redhat/cdh/RPM-GPG-KEY-cloudera
gpgcheck = 1

below logs I get from /var/log/cloudera-scm-agent

0)) shut down
[23/Feb/2018 20:19:14 +0000] 23021 MainThread _cplogging INFO [23/Feb/2018:20:19:14] ENGINE Stopped thread '_TimeoutMonitor'.
[23/Feb/2018 20:19:14 +0000] 23021 MainThread _cplogging INFO [23/Feb/2018:20:19:14] ENGINE Bus STOPPED
[23/Feb/2018 20:19:14 +0000] 23021 MainThread _cplogging INFO [23/Feb/2018:20:19:14] ENGINE Bus STOPPING
[23/Feb/2018 20:19:14 +0000] 23021 MainThread _cplogging INFO [23/Feb/2018:20:19:14] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('ansible-node2', 9000)) already shut down
[23/Feb/2018 20:19:14 +0000] 23021 MainThread _cplogging INFO [23/Feb/2018:20:19:14] ENGINE No thread running for None.
[23/Feb/2018 20:19:14 +0000] 23021 MainThread _cplogging INFO [23/Feb/2018:20:19:14] ENGINE Bus STOPPED
[23/Feb/2018 20:19:14 +0000] 23021 MainThread _cplogging INFO [23/Feb/2018:20:19:14] ENGINE Bus EXITING
[23/Feb/2018 20:19:14 +0000] 23021 MainThread _cplogging INFO [23/Feb/2018:20:19:14] ENGINE Bus EXITED
[23/Feb/2018 20:19:14 +0000] 23021 MainThread agent INFO Agent exiting; caught signal 15

[#7]

If the installation of the agent package is not succeeding, you should not have an agent log.

Can you please run the follwoing and post the resilts?

rpm -qa 'cloudera-manager-*'

[#8]

Please find the details below.

[root@ansible-node2 cloudera-scm-agent]# rpm -qa | grep cloudera
cloudera-manager-daemons-5.14.1-1.cm5141.p0.1.el7.x86_64
cloudera-manager-agent-5.14.1-1.cm5141.p0.1.el7.x86_64
[root@ansible-node2 cloudera-scm-agent]#

Below are the latest contents from log files.

[24/Feb/2018 00:15:50 +0000] 13669 MainThread agent ERROR Error, CM server guid updated, expected 93c963d9-3566-4f25-847a-faffb020866b, received ba4e4402-6ab3-4cdc-a403-39415df12824
[24/Feb/2018 00:15:55 +0000] 13669 MainThread agent INFO CM server guid: 93c963d9-3566-4f25-847a-faffb020866b
[24/Feb/2018 00:15:55 +0000] 13669 MainThread agent INFO Using parcels directory from server provided value: /opt/cloudera/parcels
[24/Feb/2018 00:15:55 +0000] 13669 MainThread parcel INFO Agent does create users/groups and apply file permissions
[24/Feb/2018 00:15:55 +0000] 13669 MainThread parcel_cache INFO Using /opt/cloudera/parcel-cache for parcel cache
[24/Feb/2018 00:15:55 +0000] 13669 MainThread agent ERROR Error, CM server guid updated, expected 93c963d9-3566-4f25-847a-faffb020866b, received ba4e4402-6ab3-4cdc-a403-39415df12824
[24/Feb/2018 00:16:00 +0000] 13669 MainThread agent INFO CM server guid: 93c963d9-3566-4f25-847a-faffb020866b
[24/Feb/2018 00:16:00 +0000] 13669 MainThread agent INFO Using parcels directory from server provided value: /opt/cloudera/parcels
[24/Feb/2018 00:16:00 +0000] 13669 MainThread parcel INFO Agent does create users/groups and apply file permissions
[24/Feb/2018 00:16:00 +0000] 13669 MainThread parcel_cache INFO Using /opt/cloudera/parcel-cache for parcel cache
[24/Feb/2018 00:16:00 +0000] 13669 MainThread agent ERROR Error, CM server guid updated, expected 93c963d9-3566-4f25-847a-faffb020866b, received ba4e4402-6ab3-4cdc-a403-39415df12824
[24/Feb/2018 00:16:05 +0000] 13669 MainThread agent INFO CM server guid: 93c963d9-3566-4f25-847a-faffb020866b
[24/Feb/2018 00:16:05 +0000] 13669 MainThread agent INFO Using parcels directory from server provided value: /opt/cloudera/parcels
[24/Feb/2018 00:16:05 +0000] 13669 MainThread parcel INFO Agent does create users/groups and apply file permissions
[24/Feb/2018 00:16:05 +0000] 13669 MainThread parcel_cache INFO Using /opt/cloudera/parcel-cache for parcel cache
[24/Feb/2018 00:16:05 +0000] 13669 MainThread agent ERROR Error, CM server guid updated, expected 93c963d9-3566-4f25-847a-faffb020866b, received ba4e4402-6ab3-4cdc-a403-39415df12824

[#9]

Thank you for the information. This does not appear to be the same issue as initiated in this thread.

However, the error is clear:

"ERROR Error, CM server guid updated, expected 93c963d9-3566-4f25-847a-faffb020866b, received ba4e4402-6ab3-4cdc-a403-39415df12824"

There is a 'cm_guid' file that is used by the Cloudera Manager (CM) server to know which host belong to it. It appears that this host may have been part of a different CM cluster or the database was recently changed. This keeps users from inadvertently pointing the agent ot another CM instance.

In any case, the solution is to:

1. Archive/remove the /var/lib/cloudera-scm-agent/cm_guid file.

2. Restart the agent:

sudo service cloudera-scm-agent restart

3. Run the Host inspector, from the Hosts page in CM and verisfy that all hosts are functioning. If other hosts fail, they too may be in this state.