Check command are in lock mode after import
gerpion opened this issue · 1 comments
BUG REPORT INFORMATION
Prerequisites
The opened issue, must be code related. GitHub is not meant for support. Feel free to check the CONTRIBUTING section for more details.
Versions
For the RPM based systems
-- Copy/Paste the result of the following command --
$ rpm -qa | grep centreon | egrep -v "(plugin|pack)" | sort
centreon-22.04.2-2.el7.centos.noarch
centreon-auto-discovery-server-22.04.0-1.el7.centos.noarch
centreon-awie-22.04.0-1.el7.centos.noarch
centreon-broker-22.04.0-13.el7.x86_64
centreon-broker-cbd-22.04.0-13.el7.x86_64
centreon-broker-cbmod-22.04.0-13.el7.x86_64
centreon-broker-core-22.04.0-13.el7.x86_64
centreon-broker-graphite-22.04.0-13.el7.x86_64
centreon-broker-influxdb-22.04.0-13.el7.x86_64
centreon-broker-storage-22.04.0-13.el7.x86_64
centreon-central-22.04.2-2.el7.centos.noarch
centreon-clib-22.04.0-13.el7.x86_64
centreon-common-22.04.2-2.el7.centos.noarch
centreon-connector-22.04.0-13.el7.x86_64
centreon-connector-perl-22.04.0-13.el7.x86_64
centreon-connector-ssh-22.04.0-13.el7.x86_64
centreon-database-22.04.2-2.el7.centos.noarch
centreon-engine-22.04.0-13.el7.x86_64
centreon-engine-daemon-22.04.0-13.el7.x86_64
centreon-engine-extcommands-22.04.0-13.el7.x86_64
centreon-gorgone-22.04.0-9.el7.centos.noarch
centreon-gorgone-centreon-config-22.04.0-9.el7.centos.noarch
centreon-license-manager-22.04.0-1.el7.centos.noarch
centreon-license-manager-common-22.04.0-1.el7.centos.noarch
centreon-perl-libs-22.04.2-2.el7.centos.noarch
centreon-poller-22.04.2-2.el7.centos.noarch
centreon-pp-manager-22.04.0-2.el7.centos.noarch
centreon-release-22.04-3.el7.centos.noarch
centreon-trap-22.04.2-2.el7.centos.noarch
centreon-web-22.04.2-2.el7.centos.noarch
centreon-widget-engine-status-22.04.0-5.el7.centos.noarch
centreon-widget-global-health-22.04.0-5.el7.centos.noarch
centreon-widget-graph-monitoring-22.04.0-5.el7.centos.noarch
centreon-widget-grid-map-22.04.0-5.el7.centos.noarch
centreon-widget-hostgroup-monitoring-22.04.0-5.el7.centos.noarch
centreon-widget-host-monitoring-22.04.0-5.el7.centos.noarch
centreon-widget-httploader-22.04.0-5.el7.centos.noarch
centreon-widget-live-top10-cpu-usage-22.04.0-5.el7.centos.noarch
centreon-widget-live-top10-memory-usage-22.04.0-5.el7.centos.noarch
centreon-widget-servicegroup-monitoring-22.04.0-5.el7.centos.noarch
centreon-widget-service-monitoring-22.04.0-5.el7.centos.noarch
centreon-widget-single-metric-22.04.0-5.el7.centos.noarch
centreon-widget-tactical-overview-22.04.0-5.el7.centos.noarch
For the deb based systems
-- Copy/Paste the result of the following command --
$ dpkg -l | grep centreon
Operating System
CentOS, Debian ...
centos 7.9
Browser used
- Google Chrome
- Firefox
- Internet Explorer IE11
- Safari
Version: --
Additional environment details (AWS, VirtualBox, physical, etc.):
Description
I had a centreon 19.04 and i have installed the last 22.04 on a new server.
I used the import/export plugin to get my configuration into the new centreon.
Now the check command i created myself on the 19.04 are in lock mode in the new 22.04.
Some plugin have their parameter changed and i'm unable to change it.
Is there a way to unlock them ?
Steps to Reproduce
Please describe precisely the steps to reproduce the encountered issue.
- I logged in Centreon
- I reached the Custom View
- And so on...
Describe the received result
Describe the expected result
Logs
PHP error logs
For version using PHP 7.2 or 7.3 on centOs 8 or PHP 8
tail -f /var/log/php-fpm/centreon-error.log
For version using PHP 7.3 on centOs 7
tail -f /var/opt/rh/rh-php73/log/php-fpm/centreon-error.log
For version using PHP 7.2 on centOs 7
tail -f /var/opt/rh/rh-php72/log/php-fpm/centreon-error.log
centreon-engine logs (if needed)
tail -f /var/log/centreon-engine/centengine.log
centreon-broker logs (if needed)
tail -f /var/log/centreon-broker/central-broker-master.log
centreon gorgone logs for Centreon >= 20.4 (if needed)
tail -f /var/log/centreon-gorgone/gorgoned.log
centcore logs for Centreon <= 19.10.x (if needed)
tail -f /var/log/centreon/centcore.log
Additional relevant information (e.g. frequency, ...)
Hello,
Well i found the solution in doing an update in the database.