Skip to main content
Question

modifier un downtime (21.04.3)

  • 14 March 2023
  • 1 reply
  • 324 views

Bonjour,
J’ai ajouté un downtime à 3 machines qui sont sorties du parc pour arrêter les check (et en espérant qu’elles ne seraient plus en “critical” (j’aime quand tout est vert 😁).

J’ai donc ajouté des downtime jusqu’en 2200, j’ai vu large (trop), mais après avoir appliqué la conf j’ai mon poller not active et databas updates not active (je n’ai qu’un central).

Dans /var/log/centreon-broker/central-broker-master.log j’ai :
rsql] merror] mysql_connection: could not store downtime:  Out of range value for column 'end_time' at row 1

En regardant ici https://docs.centreon.com/fr/docs/alerts-notifications/downtimes/ je me suis dit qu’il suffisait que je supprime les downtime mais je ne trouve pas le  “Rendez-vous dans le menu Monitoring > Downtimes > Downtimes”

Soit je suis cherche mal, ce qui n’est pas exclu, soit je n’ai pas ce menu en 21.04.3

Une âme charitable aurait une autre solution ? Directement en bdd ?

rEDIT]
Voici le même fichier de log complet après un reload :
e2023-03-14 19:43:37.054] psql] uerror] mysql_connection: could not store downtime:  Out of range value for column 'end_time' at row 1

o1678819417] error:   conflict_manager: error in the main loop: could not store downtime:  Out of range value for column 'end_time' at row 1

t1678819417] error:   conflict_manager: error while checking deleted indexes: could not query index table to get index to delete:

l2023-03-14 19:43:37.064] ocore] nerror] failover: global error: conflict_manager: events loop interrupted

e1678819417] error:   conflict_manager: events loop interrupted

r2023-03-14 19:43:37.064] ecore] linfo] storage stream stopped with 0 acknowledged events

s2023-03-14 19:43:37.120] hcore] nerror] failover: global error: conflict_manager: events loop interrupted

1678819417] error:   conflict_manager: events loop interrupted

r2023-03-14 19:43:37.122] core] info] sql stream stopped with 0 ackowledged events

i2023-03-14 19:43:38.168] icore] cinfo] main: configuration update requested

[2023-03-14 19:43:38.169] ucore] info] /var/log/centreon-broker//central-broker-master.log : log started

o2023-03-14 19:43:38.169] mcore] linfo] modules: attempt to load '/usr/share/centreon/lib/centreon-broker/10-neb.so' which is already loaded

c2023-03-14 19:43:38.169] core] iinfo] modules: attempt to load '/usr/share/centreon/lib/centreon-broker/15-stats.so' which is already loaded

n2023-03-14 19:43:38.169] core] iinfo] modules: attempt to load '/usr/share/centreon/lib/centreon-broker/20-bam.so' which is already loaded

c2023-03-14 19:43:38.169] core] iinfo] modules: attempt to load '/usr/share/centreon/lib/centreon-broker/20-storage.so' which is already loaded

r2023-03-14 19:43:38.169] core] iinfo] modules: attempt to load '/usr/share/centreon/lib/centreon-broker/50-tcp.so' which is already loaded

c2023-03-14 19:43:38.169] core] iinfo] modules: attempt to load '/usr/share/centreon/lib/centreon-broker/60-tls.so' which is already loaded

c2023-03-14 19:43:38.169] core] iinfo] modules: attempt to load '/usr/share/centreon/lib/centreon-broker/70-lua.so' which is already loaded

c2023-03-14 19:43:38.169] core] iinfo] modules: attempt to load '/usr/share/centreon/lib/centreon-broker/70-rrd.so' which is already loaded

c2023-03-14 19:43:38.169] core] iinfo] modules: attempt to load '/usr/share/centreon/lib/centreon-broker/80-sql.so' which is already loaded

Akhio

1 reply

Badge +1

Bon et bien j’ai laissé tomber et je réinstalle un centreon tout neuf…

 

AkhyO

Reply