The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

yum update not working

Discussion in 'EasyApache' started by Nirjonadda, May 18, 2017.

Tags:
  1. Nirjonadda

    Nirjonadda Well-Known Member

    Joined:
    May 8, 2013
    Messages:
    341
    Likes Received:
    8
    Trophy Points:
    18
    cPanel Access Level:
    Website Owner
    Getting error with run yum update, Please let me know that fix.

    Code:
    [root@na ~]# yum clean all
    Loaded plugins: fastestmirror, tsflags, universal-hooks
    Cleaning repos: EA4 EA4-experimental cpanel-addons-production-feed MariaDB101
                  : base cpanel-plugins elasticsearch-5.x epel extras
                  : home_Jperkster_EA4_Mod_Cloudflare letsencrypt-cpanel
                  : rhscl-python33-epel-7-x86_64 updates
    Cleaning up everything
    Cleaning up list of fastest mirrors
    [root@na ~]# yum update
    Loaded plugins: fastestmirror, tsflags, universal-hooks
    EA4                                                      | 2.9 kB     00:00
    EA4-experimental                                         | 2.9 kB     00:00
    cpanel-addons-production-feed                            | 2.9 kB     00:00
    MariaDB101                                               | 2.9 kB     00:00
    base                                                     | 3.6 kB     00:00
    cpanel-plugins                                           | 2.9 kB     00:00
    elasticsearch-5.x                                        | 1.3 kB     00:00
    epel/x86_64/metalink                                     |  20 kB     00:00
    epel                                                     | 4.3 kB     00:00
    extras                                                   | 3.4 kB     00:00
    home_Jperkster_EA4_Mod_Cloudflare                        | 1.3 kB     00:00
    letsencrypt-cpanel                                       | 2.9 kB     00:00
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
    Trying other mirror.
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
    Trying other mirror.
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
    Trying other mirror.
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
    Trying other mirror.
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
    Trying other mirror.
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
    Trying other mirror.
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
    Trying other mirror.
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
    Trying other mirror.
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
    Trying other mirror.
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
    Trying other mirror.
    
    
     One of the configured repositories failed (Python 3.3 - epel-7-x86_64),
     and yum doesn't have enough cached data to continue. At this point the only
     safe 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. Run the command with the repository temporarily disabled
                yum --disablerepo=rhscl-python33-epel-7-x86_64 ...
    
         4. Disable the repository permanently, 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 rhscl-python33-epel-7-x86_64
            or
                subscription-manager repos --disable=rhscl-python33-epel-7-x86_64
    
         5. 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=rhscl-python33-epel-7-x86_64.skip_if_unavailable=true
    
    failure: repodata/repomd.xml from rhscl-python33-epel-7-x86_64: [Errno 256] No more mirrors to try.
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
    https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://www.softwarecollections.org/repos/rhscl/python33/epel-7-x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
    [root@na ~]#
    
    From cPanel Security Advisor


     
    #1 Nirjonadda, May 18, 2017
    Last edited by a moderator: May 20, 2017
  2. 24x7server

    24x7server Well-Known Member

    Joined:
    Apr 17, 2013
    Messages:
    1,399
    Likes Received:
    52
    Trophy Points:
    28
    Location:
    India
    cPanel Access Level:
    Root Administrator
    Hi,


    It appears DNS resolvers are not working on your server to resolve this domain path. Check if you are getting ping responses on softwarecollections.org and if you don't check the DNS resolver settings...
     
    #2 24x7server, May 20, 2017
    Last edited by a moderator: May 20, 2017
  3. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    37,064
    Likes Received:
    1,287
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    It looks like the "rhscl-python33-epel-7-x86_64" YUM repo isn't responding. This is not a standard YUM repo offered with CentOS. You'd need to move this .repo file from your /etc/yum.repos.d/ directory, or edit it to ensure it uses a valid mirror.

    Thank you.
     
Loading...

Share This Page