host status: Out of range value for column 'notification_number' in broker after fix 21.10.12
rmorandell-pgum opened this issue · 3 comments
Versions
centreon-21.10.13-2.el7.centos.noarch
centreon-auto-discovery-server-21.10.3-2.el7.centos.noarch
centreon-awie-21.10.0-1.el7.centos.noarch
centreon-base-config-centreon-engine-21.10.13-2.el7.centos.noarch
centreon-broker-21.10.3-3.el7.x86_64
centreon-broker-cbd-21.10.3-3.el7.x86_64
centreon-broker-cbmod-21.10.3-3.el7.x86_64
centreon-broker-core-21.10.3-3.el7.x86_64
centreon-broker-graphite-21.10.3-3.el7.x86_64
centreon-broker-influxdb-21.10.3-3.el7.x86_64
centreon-broker-storage-21.10.3-3.el7.x86_64
centreon-clib-21.10.3-3.el7.x86_64
centreon-common-21.10.13-2.el7.centos.noarch
centreon-connector-21.10.3-3.el7.x86_64
centreon-connector-perl-21.10.3-3.el7.x86_64
centreon-connector-ssh-21.10.3-3.el7.x86_64
centreon-database-21.10.13-2.el7.centos.noarch
centreon-engine-21.10.3-3.el7.x86_64
centreon-engine-daemon-21.10.3-3.el7.x86_64
centreon-engine-extcommands-21.10.3-3.el7.x86_64
centreon-fingerprint-21.04.0-2.el7.centos.x86_64
centreon-gorgone-21.10.3-1.el7.centos.noarch
centreon-gorgone-centreon-config-21.10.3-1.el7.centos.noarch
centreon-license-manager-21.10.0-1.el7.centos.noarch
centreon-license-manager-common-21.10.0-1.el7.centos.noarch
centreon-open-tickets-21.10.1-1.el7.centos.noarch
centreon-perl-libs-21.10.13-2.el7.centos.noarch
centreon-poller-centreon-engine-21.10.13-2.el7.centos.noarch
centreon-pp-manager-21.10.0-2.el7.centos.noarch
centreon-release-21.10-5.el7.centos.noarch
centreon-trap-21.10.13-2.el7.centos.noarch
centreon-web-21.10.13-2.el7.centos.noarch
centreon-widget-engine-status-21.10.0-2.el7.centos.noarch
centreon-widget-global-health-21.10.1-1.el7.centos.noarch
centreon-widget-graph-monitoring-21.10.0-2.el7.centos.noarch
centreon-widget-grid-map-21.10.0-2.el7.centos.noarch
centreon-widget-hostgroup-monitoring-21.10.0-2.el7.centos.noarch
centreon-widget-host-monitoring-21.10.0-2.el7.centos.noarch
centreon-widget-httploader-21.10.0-2.el7.centos.noarch
centreon-widget-live-top10-cpu-usage-21.10.0-2.el7.centos.noarch
centreon-widget-live-top10-memory-usage-21.10.0-2.el7.centos.noarch
centreon-widget-servicegroup-monitoring-21.10.0-2.el7.centos.noarch
centreon-widget-service-monitoring-21.10.1-1.el7.centos.noarch
centreon-widget-tactical-overview-21.10.0-2.el7.centos.noarch
Operating System
CentOS
Browser used
- Google Chrome
- Firefox
- Internet Explorer IE11
- Safari
Description
After the fix https://github.com/centreon/centreon/issues?q=notification_number what changes the column in DB to "signed" all old negative values with an fix script has been updated to 0. But it seems that the trigger of the problem that generates the "maybe" negative value on broker poller side still exists. Now the master broker probably has the problem to store negative values. From the Broker Log
[2022-10-16T23:05:47.108+02:00] [sql] [error] mysql_connection: could not store host status: Out of range value for column 'notification_number' at row 1
[2022-10-16T23:05:47.611+02:00] [sql] [error] conflict_manager: error in the main loop: could not store host status: Out of range value for column 'notification_number' at row 1
Version installed on the poller
centreon-broker-21.10.3-3.el7.x86_64
centreon-broker-cbmod-21.10.3-3.el7.x86_64
centreon-broker-core-21.10.3-3.el7.x86_64
centreon-broker-storage-21.10.3-3.el7.x86_64
centreon-clib-21.10.3-3.el7.x86_64
centreon-common-21.10.13-2.el7.centos.noarch
centreon-connector-21.10.3-3.el7.x86_64
centreon-connector-perl-21.10.3-3.el7.x86_64
centreon-connector-ssh-21.10.3-3.el7.x86_64
centreon-engine-21.10.3-3.el7.x86_64
centreon-engine-daemon-21.10.3-3.el7.x86_64
centreon-engine-extcommands-21.10.3-3.el7.x86_64
centreon-gorgone-21.10.3-1.el7.centos.noarch
centreon-gorgone-centreon-config-21.10.3-1.el7.centos.noarch
centreon-perl-libs-21.10.13-2.el7.centos.noarch
centreon-poller-centreon-engine-21.10.13-2.el7.centos.noarch
centreon-release-21.10-5.el7.centos.noarch
centreon-trap-21.10.13-2.el7.centos.noarch
I am experiencing the same issue with centreon-web-21.10.13-2.el7.centos.noarch
Patching as per https://thewatch.centreon.com/data-usage-and-visualization-38/centreon-22-04-01-service-check-results-not-visibles-in-web-interface-935 fixed the stalled broker.
This has re-surfaced in my env when upgrading from 21.10 to 22.10. i have temporrarily fixed this by changing the fileds from unsigned to signed:
ALTER TABLE centreon_storage.hosts MODIFY notification_number bigint(20) signed DEFAULT NULL;
ALTER TABLE centreon_storage.services MODIFY notification_number bigint(20) signed DEFAULT NULL;
Yes i did the same