Error locking mutex 22

Error locking mutex 22
pure virtual method called
terminate called without an active exception
07:12:30 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61528535 K bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f69080a5530
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong…
stack_bottom = 7f66409eae30 thread_stack 0x40000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 250992651

Can you give more information? What is the OS? What MySQL version? Where any queries being ran, backup in progress? Please provide many more details.


DB version - 5.7.34-log
server version - RHEL 7.9
No Backups - mysqldump completed 1 hour before the crash.
Imperva agent is running on the server for security monitoring.

You can see from the stacktrace all the Imperva code-injection. There’s no way to predict how MySQL will behave when some other code injects itself into normal operations. I suggest removing Imperva from your mysql and observe MySQL’s stability.