We use Zabbix Monitoring. We separated the application and the db server.
I think last month, the permanent mariadb service is restarting and I'm viewing the log file, Innodb has been rolled back.
I don't understand why you are doing this. But we were struck by a huge problem.
How can I find the solution of the error or the bug that occurred?
END OF INNODB MONITOR OUTPUT
InnoDB: ###### Diagnostic info printed to the standard error stream
2021-03-15 7:50:42 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the serv
er because it appears to be hung.
210315 7:50:42 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Server version: 10.4.17-MariaDB-log
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 698828 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0