HI,

Seems to have the same here ​on IT100 (for my personal needs but a first lab before testing in our DEV env.).

20/05 21:30 Upgrade from 21.10 to 22.04

29/05 15:56 Last entry in centreon_storage.logs 

… so one day without any entry in “centreon_storage.logs“ and of course no entry in “Monitoring  >  Event Logs” since 29/05 15:56…

For me rebooting solve (for now) the issue...

rebooting or restart CBD seems to solve the issue too.

but after few minutes the same symptoms occured.

This seems to happen during the loss of communication with the DB, especially during the execution of the DB backup in LVM mode.

Hello @Pascal ,

Thank you for your feedback.
I’m going to try to reproduce.
Do you have the same issue with the table data_bin on centreon_storage database ?

Regards,

Hi Kriko,

The table data_bin seems good.

This morning, the backup took place at 3:30 a.m. and no problem came up. The logs table has data.

Can you send me the log /var/log/centreon-broker/central-broker-master.log for double check ? :)

Hello, I sent you a private message with the link to download my logs.

Thank you.
I see nothing revelant in the logs for the moment.

Hi,

The problem seems to be present again.

The last entry in the logs table is dated June 1st at 01:13:30.

MariaDB [(none)]> SELECT FROM_UNIXTIME(ctime) FROM centreon_storage.logs ORDER BY ctime DESC LIMIT 5;
+----------------------+
| FROM_UNIXTIME(ctime) |
+----------------------+
| 2022-06-01 01:13:30  |
| 2022-05-31 19:16:30  |
| 2022-05-31 13:14:30  |
| 2022-05-31 08:06:37  |
| 2022-05-31 08:06:37  |
+----------------------+
5 rows in set (0.002 sec)

The data_bin table is OK.

MariaDB [(none)]> SELECT FROM_UNIXTIME(ctime) FROM centreon_storage.data_bin WHERE ctime > 1654038810 ORDER BY ctime desc LIMIT 5;
+----------------------+
| FROM_UNIXTIME(ctime) |
+----------------------+
| 2022-06-01 15:09:04  |
| 2022-06-01 15:09:04  |
| 2022-06-01 15:09:03  |
| 2022-06-01 15:09:03  |
| 2022-06-01 15:09:03  |
+----------------------+
5 rows in set (0.346 sec)

I stopped ntp proc on my Central. The probe goes critical, I receive a notification but no entry in the logs table.

The centreon-engine logs report error probes (SOFT) around 6am not present too.

Last log on /var/log/centreon-broker/central-broker-master.log

>2022-05-31T03:30:10.599+02:00]  core]  error] failover: global error: could not store service status:  MySQL server has gone away
>2022-06-01T03:30:10.518+02:00]  core]  error] failover: global error: could not store service status:  MySQL server has gone away
>2022-06-01T03:30:12.891+02:00]  sql]  error] mysql_connection: could not insert data in data_bin:  MySQL server has gone away
>2022-06-01T03:30:12.891+02:00]  sql]  error] mysql_connection: could not update metrics:  MySQL server has gone away

I do not restart cbd in case you wish to have more information.