OVH Community

Welcome to your community space. Ask questions, search for information, post content, and interact with other OVH Community members.

Plesk server update error - Help


#1

Hi all,

I have a dedicated server with plesk installed. Some time ago the updates fails with the following error:

INFO: pum is called with arguments: ['--list', '--repo-info', '--json']

2020-07-20 03:32:21 ERROR: failure: repodata/repomd.xml from kolab-16: [Errno 256] No more mirrors to try.
ttps://mirror.kolabenterprise.com/plesk-17/kolab-16/el7/release/x86_64/repodata/repomd.xml: [Errno 14] curl#58 - "SSL peer rejected your certificate as expired."
2020-07-20 03:32:21 ERROR: Exited with returncode 1.

Looking around I have found that the baseurl for yum is under ovh mirror (ttp://centos.mirrors.ovh.net), dont know if the problem is here.

When I put in console # yum list available | grep erna, got this text:

https://mirror.kolabenterprise.com/plesk-17/kolab-16/el7/release/x86_64/repodata                                                                                        /repomd.xml: [Errno 14] curl#58 - "SSL peer rejected your certificate as expired                                                                                        ."

Intentando con otro espejo.

One of the configured repositories failed (Enterprise Linux 7 Kolab 16 Packages ),
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=kolab-16 ...

 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 kolab-16
    or
        subscription-manager repos --disable=kolab-16

 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=kolab-16.skip_if_unavailable=true

failure: repodata/repomd.xml from kolab-16: [Errno 256] No more mirrors to try.
https://mirror.kolabenterprise.com/plesk-17/kolab-16/el7/release/x86_64/repodata /repomd.xml: [Errno 14] curl#58 - “SSL peer rejected your certificate as expired .”

What can I do?
Thanks