CentOS Update

Home » CentOS » CentOS Update
CentOS 5 Comments

Hello. Previously debian, ubuntu, opensuse, I’ve used. But I’m new to CentOS too. I do not install desktop environment. Servers want to learn. I can not update the system. I could not so I researched. I give the following command . “yum update”. I get the error. I’m working on a virtual machine. (I do not know English. Translation I wrote using.)

One of the configured repositories failed (hand), and yum does not have enough cached data to continue. At this point the only yum can do is fail safe thing. There are a few ways to work “fix” this:

  1. Contact the repository for the upstream 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 the Useful if you are using a new release distribution than is supported by the repository (and the for the previous release distribution packages still work).
  3. Disable the repository, so yum will not use it by default. When will the Yuma just ignore the repository until you enable it again or use permanently –enablerepo for temporary usage: yum-config-manager –disable hand
  4. Configure the repository failing to be skipped, if it is unavailable .

Note that yum will try to contact the repo. most commands when it runs, so will have to try and fail each time (and plenty of sunshine. Yum Will be much slower). If it is a very temporary problem, though, this is often a nice compromise:

yum-config-manager of –sav –setopt = el.skip_if_unavailabl true

Connot find a valid baseurl for repo: base / 7x86_64 “vi” with CentOS-Base.repo, CentOS-Debuginfo.repo, CentOS-Vault.repo, CentOS -Sources.repo files “enabled = 1” line as I did. But “soft repolist all” command when I type “status = 0” is displayed.

5 thoughts on - CentOS Update

  • Hi,

    Sounds to me like the repository files have been altered which is causing these errors.

    You could try “yum clean all; yum update –disablerepo=*hand*” just to see if you can get any sort of updates.

    If not, it sounds like your repository files have been modified in some way.

    Check your repository files, each repository should have a line similar to this:

    mirrorlist=http://mirrorlist.CentOS.org/?release=$releasever&arch=$basearch&repo=os

    If this line is present, but different (Excluding the repo= part), for example pointing at a non-CentOS domain and location it would mean that they have been modified which is causing these errors you are receiving.

    Hope this helps :-).

    Kind Regards, Jake Shipton (JakeMS)
    GPG Key: 0xE3C31D8F
    GPG Fingerprint: 7515 CC63 19BD 06F9 400A DE8A 1D0B A5CF E3C3 1D8F

  • Dear list, I have an issue updating a CentOS 7.9 machine.

    A simple “yum update” exists with this error:

    # yum update
    –> Running transaction check
    —> Package kernel.x86_64 0:3.10.0-1160.36.2.el7 will be erased
    –> Finished Dependency Resolution ERROR: update failed. Check the log file for details
    … Protected multilib versions: libsss_idmap-1.16.5-10.el7_9.11.x86_64 !libsss_idmap-1.16.5-10.el7_9.10.i686
    Error: Protected multilib versions:
    libsss_nss_idmap-1.16.5-10.el7_9.11.x86_64 !libsss_nss_idmap-1.16.5-10.el7_9.10.i686

    Trying to update excluding all i686 packages reveal the true issue: an unmet dependency of

    # yum update –exclude=”*.i686″ libsss_idmap Resolving Dependencies
    –> Running transaction check
    —> Package libsss_idmap.x86_64 0:1.16.5-10.el7_9.10 will be updated
    –> Processing Dependency: libsss_idmap = 1.16.5-10.el7_9.10 for package: sssd-client-1.16.5-10.el7_9.10.x86_64
    —> Package libsss_idmap.x86_64 0:1.16.5-10.el7_9.11 will be an update
    –> Finished Dependency Resolution Error: Package: sssd-client-1.16.5-10.el7_9.10.x86_64 (@updates)
    Requires: libsss_idmap = 1.16.5-10.el7_9.10

    Basically, yum tries to update libsss_idmap to a too new version, not allowed in for sssd-client. I do not use sssd so I can simply uninstall the packages, but I am curious about the unmet dependency.

    Anyone has the same issue?
    Regards.

  • Il 2021-12-03 15:46 Johnny Hughes ha scritto:

    It is an Azure CentOS instance, which is pre-configured for using ex-OpenLogic mirrors:

    # CentOS-Base.repo baseurl=http://olcentgbl.trafficmanager.net/CentOS/$releasever/os/$basearch/

    I updated sssd-client and the libsssd dependencies by using an official CentOS mirrors.

    Thank you for pointing me to a mirror issue!
    Regards.