I installed Percona for MySQL server 8.4.8-8’s audit log filter component on mysql 8.4.8 community edition on Ubuntu 24.04. I then created a filter to log connections and admin commands (such as create/drop database, create/drop user etc.), and assigned it to 'user ‘%’. The filter use class general/query and references general_sql_command.str.
As long as I login to mysql client and issue some commands, like create user, I would lose connection to mysql server. The error log file shows ‘mysqld got signal 11’.
I re-assigned the filter to ‘root@locahost’ and the crash still occurs.
I believe it is a known bug. Just wonder if anyone else experiences the same issue and if there is a fix for it.
Hi @ixixijikewa ,
Welcome to Percona Community.
Would you like to share you error log around these crashes.
Thanks,
K
The log messages are below. It seems that when it crashed mysql server is automatically restarted.
2026-04-20T10:26:41Z UTC - mysqld got signal 11 ;
Signal SIGSEGV (Address not mapped to object) at address 0x0
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=0c6bffb1349580c40a08095e036e785c95967f88
Thread pointer: 0x7add7c008080
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 = 7add945f5bf0 thread_stack 0x100000
#0 0x653be1cb14d0
#1 0x7ade8d04532f
#2 0x7ade8d18b7dd
#3 0x653be2e76484
#4 0x7addaa100550
#5 0x653be1b09905
#6 0x653be1cb33ad
#7 0x653be1b06fe3
#8 0x653be1a5467b
#9 0x653be26c96df
#10 0x653be1b08f45
#11 0x653be1b092bb
#12 0x653be1cce4ad
#13 0x653be1b093ff
#14 0x653be1b736ec
#15 0x653be1b8cd24
#16 0x653be1b680e5
#17 0x653be1b68cac
#18 0x653be1cb2f56
#19 0x653be2cef91f
#20 0x7ade8d09caa3
#21 0x7ade8d129c6b
#22 0xffffffffffffffff
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7add7c0fa080): is an invalid pointer
Connection ID (thread ID): 10
Status: NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2026-04-20T20:26:42.152349+10:00 0 [System] [MY-015015] [Server] MySQL Server - start.
2026-04-20T20:26:42.459580+10:00 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.8) starting as process 840681
You might be hitting this bug Jira
Thanks. The mentioned bug refers to memcpy and was with mysql 8.0.45. In my case it’s mysql 8.4.8.
I have checked through copilot and it says the crash is intrinsic to mysql 8.4 evaluates general_sql_command.*.
Just wonder if someone has got audit log works with mysql 8.4.8 CE.
Hi @lxnguyen, I tried the same setup (ubuntu 24.04, mysql community 8.4.8) and it is also crashing for me when using the audit log filter component.
It crashes when first logging in with the mysql client or when executing a query with incorrect syntax:
mysql> select $$;
ERROR 2013 (HY000): Lost connection to MySQL server during query
No connection. Trying to reconnect...
Connection id: 10
Current database: *** NONE ***
2026-04-21T07:06:25.345475Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.4.8' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server - GPL.
2026-04-21T07:07:07Z UTC - mysqld got signal 11 ;
Signal SIGSEGV (Address not mapped to object) at address 0x0
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=0c6bffb1349580c40a08095e036e785c95967f88
Thread pointer: 0x76ab28000fd0
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 = 76ab94128bf0 thread_stack 0x100000
#0 0x5914e78e54d0 <unknown>
#1 0x76aba384532f <unknown> at sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
#2 0x76aba398b7dd __strlen_avx2 at sysdeps/x86_64/multiarch/strlen-avx2.S:76
#3 0x5914e8aaa484 <unknown>
#4 0x76ab94d607f3 _ZN16audit_log_filter14AuditLogFilter17set_extended_infoEP3THDP27Security_context_handle_impRNS_18AuditRecordGeneralE at /mnt/jenkins/workspace/ps8.0-autobuild-RELEASE/test/percona-server-8.4.8-8/components/audit_log_filter/audit_log_filter.cc:760
#5 0x76ab94d62540 _ZN16audit_log_filter14AuditLogFilter12notify_eventENS_19audit_event_class_tEPKv at /mnt/jenkins/workspace/ps8.0-autobuild-RELEASE/test/percona-server-8.4.8-8/components/audit_log_filter/audit_log_filter.cc:516
#6 0x5914e773d905 <unknown>
#7 0x5914e78e73ad <unknown>
#8 0x5914e773afe3 <unknown>
#9 0x5914e768867b <unknown>
#10 0x5914e82fd6df <unknown>
#11 0x5914e773cf45 <unknown>
#12 0x5914e773d2bb <unknown>
#13 0x5914e79024ad <unknown>
#14 0x5914e773d3ff <unknown>
#15 0x5914e77a76ec <unknown>
#16 0x5914e77c0d24 <unknown>
#17 0x5914e779c0e5 <unknown>
#18 0x5914e779ccac <unknown>
#19 0x5914e78e6f56 <unknown>
#20 0x5914e892391f <unknown>
#21 0x76aba389caa3 start_thread at ./nptl/pthread_create.c:447
#22 0x76aba3929c6b clone3 at sysdeps/unix/sysv/linux/x86_64/clone3.S:78
#23 0xffffffffffffffff <unknown>
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (76ab2800bb70): is an invalid pointer
Connection ID (thread ID): 10
Status: NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Please note that this audit log filter component is developed and validated for Percona Server for MySQL. Running it on MySQL Community Server is not an officially tested/supported combination, so compatibility issues can occur.
Hi @hai.nguyen, thanks. It confirms this is a real issue.