Be aware that depending on your Centreon installation and the packages that are present, this procedure may not work (we are investigating this bug). In all cases, make sure you have a snapshot of your machine before starting the procedure.
If the Debian upgrade wants to remove Centreon packages, answer NO, stop the procedure and contact our support team to provide them with the output of the following command:
apt list --installed > /tmp/installed_packages.log
With the upcoming release of Centreon 24.10, support for Debian 11 will officially come to an end. If you're running Centreon on Debian 11 and want to upgrade to version 24.10, you need to migrate to Debian 12 first. This guide will walk you through the steps to ensure a smooth in-place upgrade of your operating system from Debian 11 (Bullseye) to Debian 12 (Bookworm). You can also refer to Debian’s official documentation.
Pre-Migration Checklist
Before you begin, make sure to take the following precautions:
Back up essential data: Ensure you have recent backups of all critical data and configurations.
Check for system requirements: Verify that your hardware and software meet the compatibility requirements for Debian 12.
Read the release notes: Review the official Debian release notes for Debian 12 to understand any new features, deprecated functionalities, and important considerations.
Inform stakeholders: Notify any impacted users or stakeholders about the planned upgrade and any expected downtime during the process.
Step-by-Step Migration Guide
Step 1: Upgrade Centreon to version 24.04.x
Update or upgrade your Centreon to the latest minor 24.04.x version.
Step 2: Update Current System
Ensure your current Debian 11 system is updated to the latest package versions. Your version of Debian must be Debian 11.11:
apt update apt upgrade apt dist-upgrade
Reboot your system to ensure all updates are applied:
sudo reboot
Step 3: Update APT Sources
In the source list, replace any occurrences of bullseye with bookworm:
sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list.d/centreon*
Step 4: Perform the Upgrade
Update the APT package lists to the new Debian 12 sources:
sudo apt update
Upgrade the existing package without installing new ones:
Check that Debian only wants to upgrade or replace Centreon packages. If it wants to remove Centreon packages, answer NO, stop the procedure and contact our support team to provide them with the output of the following command:
apt list --installed > /tmp/installed_packages.log
This process will take some time, so please be patient as all packages are upgraded to their Debian 12 versions. Follow any on-screen prompts to accept changes or confirm the installation of new packages.
Step 5: Clean Up
After the upgrade is complete, clean up any unnecessary packages and dependencies:
sudo apt autoremove sudo apt autoclean
Reboot your system to finalize the upgrade process:
sudo reboot
Step 6: Verify the Upgrade
Once your system reboots, verify that the upgrade was successful by checking the Debian version:
lsb_release -a
The output should indicate that your system is now running Debian 12 (Bookworm).
Post-Migration Considerations
After upgrading to Debian 12, here are a few additional steps to ensure everything is functioning correctly:
Verify that all services and applications are working as expected.
Check for any package-specific migration instructions or additional configuration steps in the release notes.
Monitor system logs for any errors or warnings that may need attention.
Thank you for using Centreon and for your continued dedication to maintaining a robust and secure monitoring environment!
Page 1 / 1
Hello,
I've followed the manual to update, and now when I restart the pollers, only the central poller restarts, not the others.
Do you know what could be causing this?
Thanks, best regards.
Hello,
this is what the gorgoned log on the central server says
2024-11-12 13:33:04 - ERROR - [legacycmd] Cannot process message type 'SENDCBCFGthrowing it away. 2024-11-12 13:33:49 - ERROR - [legacycmd] Cannot process message type 'SENDCBCFGthrowing it away.
and tcpdump on port 5556 on the poller shows no activity.
Thanks, best regards.
Hi @dmembibre can you cehck the status of gorgoned process on your distant poller?
Hi @Laurent ,
Can you enable debug mode on both gorgoned process via /etc/sysconfig/gorogned file and restart them.
Then try to export configuration through UI and check /var/log/centreon-gorgone/gorgoned.log files.
Indeed, the Gorgoned proxy module was not starting, and the log during the Gorgoned startup showed this:
2024-11-14 06:28:47 - INFO - core] Module 'proxy' cannot be loaded: Base class package "Libssh::Session" is empty. (Perhaps you need to 'use' the module which defines that package first, or make that module available in @INC (@INC contains: /usr/bin /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl). at /usr/share/perl5/gorgone/modules/core/proxy/sshclient.pm line 23. BEGIN failed--compilation aborted at /usr/share/perl5/gorgone/modules/core/proxy/sshclient.pm line 23. Compilation failed in require at /usr/share/perl5/gorgone/modules/core/proxy/class.pm line 30. BEGIN failed--compilation aborted at /usr/share/perl5/gorgone/modules/core/proxy/class.pm line 30. Compilation failed in require at /usr/share/perl5/gorgone/modules/core/proxy/hooks.pm line 31. BEGIN failed--compilation aborted at /usr/share/perl5/gorgone/modules/core/proxy/hooks.pm line 31. Compilation failed in require at /usr/share/perl5/gorgone/class/core.pm line 429.
I fixed it by doing the following: apt-get install libssh-dev and cpanm Libssh::Session
This stopped working after the upgrade from Debian 11 to 12. I understand that the gorgone package might be missing some dependency, right? Also, during the Debian upgrade on the poller, the gorgone package was removed, so I had to reinstall it.
Additionally, the VMware plugin is also encountering errors with libraries. Can't locate VMware/VIRuntime.pm in @INC (you may need to install the VMware::VIRuntime module)
Hi,
I fixed the error of VMware plugin by doing the following: