Not the answer you need?
Register and ask your own question!

upgrading to PMM 1.1.0 beta

I heard that there is new beta version from PMM 1.1.0. I tried to install pmm-client using both yum repository and tarbal package and failed to do so, followed the below links.

Getting the below error from yum: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.

using tarbal:
I couldn't find pmm-client 1.1.0beta as mentioned in the installation document.

Can you please redirect me to the correct links where I can get the packages.

Thank you.


  • MykolaMykola Percona Percona Staff Role

    please don't use experimental repository, it is for publishing prototypes/proof-of-concept versions, usually experimental binaries never become beta, release candidate or GA version.

    to get pmm-client-1.1.0-1.beta rpm you need to disable experimental repository and enable testing repository.
    after that please type the following commands
    yum --enablerepo=* clean all
    yum install pmm-client
  • govindareddy20govindareddy20 Contributor Current User Role Beginner
    Getting the following error after running the above code given.

    Loaded plugins: priorities, update-motd, upgrade-helper
    amzn-main/2016.09 | 2.1 kB 00:00
    amzn-main/2016.09/group | 35 kB 00:00
    amzn-main/2016.09/primary_db | 3.5 MB 00:00
    amzn-updates/2016.09 | 2.3 kB 00:00
    amzn-updates/2016.09/group | 35 kB 00:00
    amzn-updates/2016.09/updateinfo | 364 kB 00:00
    amzn-updates/2016.09/primary_db | 565 kB 00:00
    datadog | 2.5 kB 00:00
    datadog/primary_db | 110 kB 00:00 [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
    Trying other mirror.

    One of the configured repositories failed (Percona-Experimental YUM repository - noarch),
    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. 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 percona-experimental-noarch

    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

    yum-config-manager --save --setopt=percona-experimental-noarch.skip_if_unavailable=true

    failure: repodata/repomd.xml from percona-experimental-noarch: [Errno 256] No more mirrors to try.
  • MykolaMykola Percona Percona Staff Role
    Hi govindareddy20,

    please disable experimental repository :(
    it is dangerous, you can install fully untested software from it !!

    you can disable experimental repo with the following commands
    yum-config-manager --disable percona-experimental-x86_64
    yum-config-manager --disable percona-experimental-noarch

    You can install pmm-client with the following commands
    yum --enablerepo=* clean all
    yum install --enablerepo=percona-testing-x86_64 pmm-client
    NB: code in testing repository has BETA quality
This discussion has been closed.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.