Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Failed to upgrade hdp 2.5.3 to hdp 2.6.5.

Failed to upgrade hdp 2.5.3 to hdp 2.6.5.

Explorer

I am trying to upgrade HDP 2.5.3 to 2.6.5 and I am not sure if I am doing it right.

I have taken following step:

1. extracted hdp 2.6.5 , hdp-utils, hdp-gpl tar file in /var/www/html/hdp-2.6.

2. registered hdp 2.6.5 through ambari by providing base url for hdp 2.6, hdp-utils, hdp-gpl.

I have not created repo file and when I am trying to install HDP 2.6.5 , ambari-hdp-101.repo file is created in /etc/yum.repos.d.

3. installation of HDP 2.6.5 is getting failed with error

/var/lib/ambari-agent/data/errors-3368.txt

2018-09-11 12:23:28,785 - Package Manager failed to install packages. Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install mahout' returned 1.  

One of the configured repositories failed (MySQL Connectors Community),and yum doesn't have enough cached data to continue. At this point the onlysafe thing yum can do is fail. There are a few ways to work "fix" this:  

1. Contact the upstream for the repository and get them to fix the problem.  

2. Reconfigure the baseurl/etc. for the repository, to point to a working  upstream. This is most often useful if you are using a newer  distribution release than is supported by the repository (and the  packages for the previous distribution release still work). 

3. Disable the repository, so yum won't use it by default. Yum will then  just ignore the repository until you permanently enable it again or use  --enablerepo for temporary usage:  

yum-config-manager --disable mysql-connectors-community 

 4. Configure the failing repository to be skipped, if it is unavailable.  Note that yum will try to contact the repo. when it runs most commands,  so will have to try and fail each time (and thus. yum will be be much  slower). If it is a very temporary problem though, this is often a nice  compromise:   

yum-config-manager --save --setopt=mysql-connectors-community.skip_if_unavailable=true

failure: repodata/repomd.xml from mysql-connectors-community: [Errno 256] No more mirrors to try.

http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30177 milliseconds')

http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30045 milliseconds')

http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30192 milliseconds')

http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30052 milliseconds')

http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30203 milliseconds')

http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30037 milliseconds')

http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30179 milliseconds')

http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30041 milliseconds')

http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30180 milliseconds')

http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30050 milliseconds')
4 REPLIES 4
Highlighted

Re: Failed to upgrade hdp 2.5.3 to hdp 2.6.5.

Hi @Shobhna Dhami ,

One of the configured repositories failed (MySQL Connectors Community),and yum doesn't have enough cached data to continue. At this point the onlysafe thing yum can do is fail. There are a few ways to work "fix" this:

This looks like your repo is having issue and is hardly anything related to HDP or ambari.

Can you do a yum repolist command and see which repois having issue.

Remove the problamatic repo which i feel is from MYSQL from /etc/yum.repos.d/ and do a

yum clean all

and retry installation.also look out for storage space in your Node

Hope this helps.

Highlighted

Re: Failed to upgrade hdp 2.5.3 to hdp 2.6.5.

Explorer

Hi @Akhil S Naik ,

I removed the repository and now i am getting error.

I followed https://community.hortonworks.com/articles/102213/hdp-2603-package-installation-failing-with-error-i... and did all 3 steps but still getting same error.

2018-09-12 16:26:17,632 - Package Manager failed to install packages. Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install mahout' returned 1. Error: Package: hadoop_2_6_5_0_292-hdfs-2.7.3.2.6.5.0-292.x86_64 (HDP-2.6-repo-106)
           Requires: libtirpc-devel
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py", line 423, in install_packages
    retry_count=agent_stack_retry_count
  File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166, in __init__
    self.env.run()
  File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line 160, in run
    self.run_action(resource, action)
  File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line 124, in run_action
    provider_action()
  File "/usr/lib/ambari-agent/lib/resource_management/core/providers/package/__init__.py", line 57, in action_upgrade
    self.upgrade_package(package_name, self.resource.use_repos, self.resource.skip_repos)
  File "/usr/lib/ambari-agent/lib/resource_management/core/providers/package/yumrpm.py", line 269, in upgrade_package
    return self.install_package(name, use_repos, skip_repos, is_upgrade)
  File "/usr/lib/ambari-agent/lib/resource_management/core/providers/package/yumrpm.py", line 264, in install_package
    self.checked_call_with_retries(cmd, sudo=True, logoutput=self.get_logoutput())
  File "/usr/lib/ambari-agent/lib/resource_management/core/providers/package/__init__.py", line 266, in checked_call_with_retries
    return self._call_with_retries(cmd, is_checked=True, **kwargs)
  File "/usr/lib/ambari-agent/lib/resource_management/core/providers/package/__init__.py", line 283, in _call_with_retries
    code, out = func(cmd, **kwargs)
  File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 72, in inner
    result = function(command, **kwargs)
  File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 102, in checked_call
    tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy)
  File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 150, in _call_wrapper
    result = _call(command, **kwargs_copy)
  File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 303, in _call
    raise ExecutionFailed(err_msg, code, out, err)
ExecutionFailed: Execution of '/usr/bin/yum -d 0 -e 0 -y install mahout' returned 1. Error: Package: hadoop_2_6_5_0_292-hdfs-2.7.3.2.6.5.0-292.x86_64 (HDP-2.6-repo-106)
           Requires: libtirpc-devel
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py", line 487, in <module>
    InstallPackages().execute()
  File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 375, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py", line 153, in actionexecute
    raise Fail("Failed to distribute repositories/install packages")
resource_management.core.exceptions.Fail: Failed to distribute repositories/install packages
Highlighted

Re: Failed to upgrade hdp 2.5.3 to hdp 2.6.5.

Hi @Shobhna Dhami,

Are you able to upgrade now? This error also looks like in Yum packages. you can actually manually try this commands in the cluster and see if it succeeds.

Seeing the exception. i assume it will be resolved by running

yum install -y libtirpc-devel
Highlighted

Re: Failed to upgrade hdp 2.5.3 to hdp 2.6.5.

Rising Star

Please manually install that missing package libtirpc-devel on the nodes first and then try to proceed with the installation

yum install libtirpc-devel

Let me know how this goes

Don't have an account?
Coming from Hortonworks? Activate your account here