Skip to main content
Version: 23.10

Known issues

Below is a list of known issues and/or bugs you may encounter. We try to provide workarounds. We apply fixes when necessary and are forever improving our software in order to solve any issues for future releases.

Anomaly Detection​

Limitations of Anomaly Detection services used as indicators in BAM​

When used as indicators in BAM, Anomaly Detection services:

  1. Are not supported by CLAPI or by the v1 API.
  2. Cannot be configured using the Configuration > Business activities > Indicators page. You must first create a Business activity on the Configuration > Business activities > Business activities page, then use the Anomaly Detection service in the business activity.

Workarounds​

  1. Use the v2 API.
  2. Create the business activity first, then use the Anomaly Detection service as an indicator within the business activity (see above).

The data exclusion feature is not yet available​

The feature that allows you to exclude some data from Anomaly Detection's model computation appears in the interface but is not implemented yet. You get the message "Not implemented yet" when trying to use the feature.

Workaround​

There is no workaround but the feature will be available in a coming version.

Centreon Web​

Environment variable not found: "hostCentreon"​

During a central server (or remote server) installation, an error message appears for a short time in the snackbar when accessing the wizard to complete the installation. The error message is the following:

The controller for URI "/centreon/api/latest/platform/versions" is not callable: Environment variable not found: "hostCentreon".

Workaround​

There is no workaround and this message does not prevent you from finalizing the installation.

You have reached the maximum of id into centreon_storage.index_data​

Workaround​

Play the following query into MariaDB:

In your monitoring database:

ALTER TABLE index_data MODIFY id bigint unsigned AUTO_INCREMENT;
ALTER TABLE metrics MODIFY index_id bigint unsigned;

In your configuration database:

ALTER TABLE ods_view_details MODIFY index_id bigint unsigned;
ALTER TABLE virtual_metrics MODIFY index_id bigint unsigned;

Depending on your metrics volumes, this operation could be more or less long.

Autologin does not work with some pages​

Description​

Autologin is currently not supported on the following pages:

  • Monitoring > Map (legacy excluded)
  • Monitoring > Resources Status
  • Configuration > Hosts > Discovery
  • Configuration > Business Activity > Business Views
  • Configuration > Business Activity > Business Activity

Workaround​

There is currently no workaround.

Centreon MBI​

You get some errors during daily import and statistic calculation​

Description​

After updating MBI, you get an error similar to the following during the statistic calculation.

[Tue Jun 1 18:28:26 2021] [FATAL] mod_bi_hgservicemonthavailability insertion execute error : Out of range value for column 'mtbf' at row 1
[Tue Jun 1 18:28:26 2021] [FATAL] Program terminated with errors

This is due to a column update issue in the database.

Workaround​

  1. You need to execute a script to update database columns, by entering this command on the central server:
php /usr/share/centreon/www/modules/centreon-bi-server/tools/updateColumnsToBigint.php
  1. Then follow this procedure to rebuild missing reporting data.

MBI does not work if databases have custom names​

Workaround​

There is currently no workaround.

The Report Parameters tab of a job is empty​

Description​

The Report Parameters tab of a job is empty (Reporting > Monitoring Business Intelligence > Jobs)

Workaround​

  • Go to the Configuration tab of the job
  • Select a different report design from the Report design list
  • Select the original report design
  • Go back to the Report Parameters tab

You have reached the maximum of id for servicemetric_id columns​

Description​

If you have a very large infrastructure, it is possible that the servicemetric_id column size has been reached.

Workaround​

Depending on your data volume, this operation could be more or less long.

  • Connect in the reporting server

  • Disable cron job in /etc/cron.d/centreon-bi-engine:

    #30 4 * * * root /usr/share/centreon-bi//bin/centreonBIETL -d >> /var/log/centreon-bi//centreonBIETL.log 2>&1

  • Execute the following queries in centreon_storage database:

    ALTER TABLE mod_bi_metricdailyvalue MODIFY servicemetric_id BIGINT(20) UNSIGNED NOT NULL;
    ALTER TABLE mod_bi_metrichourlyvalue MODIFY servicemetric_id BIGINT(20) UNSIGNED NOT NULL;
    ALTER TABLE mod_bi_metricmonthcapacity MODIFY servicemetric_id BIGINT(20) UNSIGNED NOT NULL;
    ALTER TABLE mod_bi_metriccentiledailyvalue MODIFY servicemetric_id BIGINT(20) UNSIGNED NOT NULL;
    ALTER TABLE mod_bi_metriccentilemonthlyvalue MODIFY servicemetric_id BIGINT(20) UNSIGNED NOT NULL;
    ALTER TABLE mod_bi_metriccentileweeklyvalue MODIFY servicemetric_id BIGINT(20) UNSIGNED NOT NULL;
    ALTER TABLE mod_bi_servicemetrics MODIFY id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT;

  • Enable cron job in /etc/cron.d/centreon-bi-engine :

    30 4 * * * root /usr/share/centreon-bi//bin/centreonBIETL -d >> /var/log/centreon-bi//centreonBIETL.log 2>&1

  • If the operation occurred during the usual launch of the scheduled task, run the following command indicating the correct start and end dates:

    /usr/share/centreon-bi/bin/centreonBIETL -rIEDP -s YYYY-MM-DD -e YYYY-MM-DD