Skip to main content

Bonjour,

Architecture avec un central + 2 pollers, tous en 22.10.

Suite à l’upgrade de 21.04 à 22.10, j’ai des erreurs récurrentes dans gorgoned.log pour lesquelles je ne trouve pas d’infos et des downtime bien vus dans l’IHM mais qui ne sortent pas de la vue “unhandled problems”.

gorgoned.log central :

2023-11-14 17:01:53 - DEBUG - 1proxy] choose node target '10' for node '10'
2023-11-14 17:01:53 - DEBUG - 1proxy] choose node target '9' for node '9'
2023-11-14 17:01:53 - DEBUG - 1proxy] Send message: channel = control] naction = PING] atoken = ] Ntarget = 10~~10] rdata = {}]
2023-11-14 17:01:53 - DEBUG - 1proxy] Send message: channel = 9] action = GETLOG] ttoken = ] Otarget = 9~~9] tdata = {"ctime":"1699977601.66832"}]
2023-11-14 17:01:53 - DEBUG - 1core] JWK thumbprint = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2023-11-14 17:01:53 - DEBUG - 1core] Message received - aSETLOGS] e7ae4b31b5542816937bf6b5c42146a398170a5cf1c5378b350034cdd98cae1da12f10f325032ea0d639d1bfd8ab49415c7cadcdf1cb4f3ae056a301037df5551] a] {"data":{"action":"getlog","id":"9","result":"]},"code":0}
2023-11-14 17:01:53 - INFO - 0proxy] Received setlogs for '9'
:q


2023-11-14 17:01:54 - ERROR - 1proxy] container 2: Receiving DIE: FATAL: rsa_decrypt_key_ex failed: Invalid input packet. at /usr/share/perl5/vendor_perl/gorgone/class/clientzmq.pm line 182.
2023-11-14 17:01:54 - ERROR - 1proxy] Send message problem for '10': Decoding issue: FATAL: rsa_decrypt_key_ex failed: Invalid input packet. at /usr/share/perl5/vendor_perl/gorgone/class/clientzmq.pm line 182.

2023-11-14 17:01:54 - DEBUG - 1core] Message received - aPUTLOG] v] ] {"etime":1699977714,"data":{"message":"Send message problem for '10': Decoding issue: FATAL: rsa_decrypt_key_ex failed: Invalid input packet. at /usr/share/perl5/vendor_perl/gorgone/class/clientzmq.pm line 182.\n"},"instant":null,"token":"","code":1}
2023-11-14 17:01:54 - DEBUG - 1core] Message received - aPONGRESET] b8ffce00ca19b22fb9f0bce5cddbc20d52e21a4a34ac69127a397e5d85f500d01382c1a0ec115bb8339dafd4e2eabc72da9e3ce513981ccead2c7332d88f11b4] c] { "data": { "id": 10 } }
2023-11-14 17:01:54 - INFO - 0proxy] PongReset received from '10'
 

gorgoned.log first poller:

2023-11-14 16:18:45 - ERROR - no such column: mtime
2023-11-14 16:18:46 - ERROR - no such column: mtime
2023-11-14 16:18:46 - ERROR - 1core] cannot load gorgone_identity
2023-11-14 16:19:43 - ERROR - no such column: mtime
2023-11-14 16:19:44 - ERROR - no such column: mtime
2023-11-14 16:19:44 - ERROR - 1core] cannot load gorgone_identity
2023-11-14 16:20:00 - ERROR - table gorgone_identity has no column named mtime
2023-11-14 16:20:01 - ERROR - table gorgone_identity has no column named mtime
2023-11-14 16:20:36 - ERROR - table gorgone_identity has no column named mtime
2023-11-14 16:20:37 - ERROR - table gorgone_identity has no column named mtime
2023-11-14 16:21:52 - ERROR - table gorgone_identity has no column named mtime

 

Quelque chose m’échappe, auriez vous une piste pour moi ?

Merci

Le problème est identifié et corrigé semble t’il.

La structure de la base locale sqllite /var/lib/centreon-gorgone/history.sdb sur le first poller fautif n’a pas été mise à jour lors de l’upgrade 21.04=>22.10.

Voici les opérations nécessaires au rétablissement du bon fonctionnement de gorgoned:

  • systemctl stop gorgoned
  • mv /var/lib/centreon-gorgone/history.sdb /var/lib/centreon-gorgone/history.sdb.old
  • systemctl start gorgoned

Merci aux personnes qui ont pris du temps pour lire ce ticket.

 


Bonjour @rurien,
Merci d’avoir partagé la solution, je sûr que ceci aidera quelqu’un qui a un problème similaire,


Reply