Skip to main content

In order to make the installation of Centreon easier, regardless of the operating system used, we have decided to unify the RPM and APT repositories into a single repository.

Thus, from May 2023, the yum.centreon.com and apt.centreon.com repositories become packages.centreon.com.

 

First of all, don't worry: redirections have been put in place so that the supported Centreon platforms can continue to have updates, without it being necessary to change the configuration of the repositories.

 

But beware, these redirects will only remain active for six months: this is the period you have to reconfigure your platforms so that they use packages.centreon.com. We show you how to do it below.

 

Why this change?

  • A single repository regardless of the Linux distribution.
  • Differentiate between supported and outdated versions, a new repository will be created to archive unsupported versions.
  • Group the Centreon Plugins and Monitoring Connectors, which are independent of the version of Centreon, in repositories dedicated to them.
  • Facilitate our package deliveries (.rpm and .deb)
  • Facilitate the support of future operating systems.

 

Which platforms are affected?

 

Centreon platforms whose software version is greater than or equal to 21.10 must be reconfigured within the next six months in order to continue to benefit from updates.

 

Centreon platforms whose version is older than 21.10 are not concerned because they no longer receive updates.

 

When updating a platform from a version prior to 21.10 to a later version, it is necessary to modify the configuration of the repositories.

 

This concerns both open-source software editions and commercial editions.

 

How to update the repositories on my Centreon platforms?
 

The update procedure differs depending on the operating system of the platform.

 

Update your RPM repositories (RHEL / Oracle Linux / Alma Linux 7 & 8)

  • Open-source software edition: update of Standard & Centreon Plugins repositories

rm /etc/yum.repos.d/centreon.repo
dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/22.10/el8/centreon-22.10.repo
dnf clean all --enablerepo=*

Replace 22.10 with your major version of Centreon (twice in the link).

Replace el8 with your version of the operating system (el8 for version 8, otherwise el7).

 

If you want to update Centreon packages:

dnf update centreon\*

  • Commercial software editions

Contact our support team for updates to Monitoring Connectors repositories (formerly Plugin Packs) and commercial extensions.

 

Update your APT repositories (Debian 11)

  • Open-source software edition: update of Standard & Centreon Plugins repositories

echo "deb https://packages.centreon.com/apt-standard-22.10-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon.list
echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list
apt update

Replace 22.10 with your major version of Centreon.

 

If you want to update Centreon packages:

apt upgrade centreon

  • Commercial software editions

Contact our support team for updates to Monitoring Connectors repositories (formerly Plugin Packs) and commercial extensions.

Hi,

This is quite wrong to include the last ligne (dnf update centreon-\*),  at least without a clear separation from the lines above. Because AFAIK it’s not part of the update of the repositories, but it is an “upgrade” of every Centreon’s packages, which is definitively a different action. One may want to update the list of available repositories, in prevision of the next upgrade of Centreon’s packages, or to install a particular package, without the desire for an upgrade. Especially considering the high probability to break things the Centreon upgrades represent since a couple of years. 

The Yum “update” command is blatantly badly named. So badly named that it is now (in dnf) depreciated in favor of “upgrade”, which is far more meaningful of what this command does.

Same remark for Debian, where here only the apt update is necessary but the apt upgrade is not, or even something you want to avoid.
 

I’m glad I wasn’t too tired to blindly run all the indicated commands, as I was clearly close of a shitty end of week if I’d run this command on a production server… I guess I should even apply the sacred rule which say, “Thou do not even connect to a production server on friday afternoun”. ^^

 

Hi @Stéphane thank you for your feedback.

Terms & ConditionsCookie settings