# Percona MySQL 8.4.8 Loop Crashing (Audit related?)

**URL:** <https://forums.percona.com/t/percona-mysql-8-4-8-loop-crashing-audit-related/40699>\
**Category:** Percona Distribution for MySQL\
**Created:** [April 22, 2026, 8:43am UTC](https://forums.percona.com/t/percona-mysql-8-4-8-loop-crashing-audit-related/40699 "2026-04-22T08:43:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rafaelpastre](https://avatars.discourse-cdn.com/v4/letter/r/8797f3/32.png) [@rafaelpastre](https://forums.percona.com/u/rafaelpastre)\
**Post date:** [April 22, 2026, 8:44am UTC](https://forums.percona.com/t/percona-mysql-8-4-8-loop-crashing-audit-related/40699/1 "2026-04-22T08:44:00Z")

</div>

My Percona for MySQL 8.4.8 started loop crashing after going Live, and just came back online after removing audit related parameters from my.cnf.

Any idea guys?

After hashing out the follwing variables, the instance came up Online.

audit\_log\_syslog\_ident = ‘db11b-sldg-mt1’  
audit\_log\_handler = FILE  
audit\_log\_policy = ALL  
audit\_log\_format = JSON  
audit\_log\_file = /var/log/mysql/audit.log  
audit\_log\_rotate\_on\_size = 224M  
audit\_log\_rotations = 6  
audit\_log\_strategy = PERFORMANCE  
audit\_log\_buffer\_size = 10485760  
audit\_log\_exclude\_accounts = ‘app\_infinity@10.16.21.%,zabbix@%,monitoring@localhost,replication@%’

Crashing errors:

2026-04-14T07:34:18.145737Z 10 [System] [MY-014001] [Repl] Replica receiver thread for channel ‘’: connected to source ‘replication@10.16.31.111:3306’ with server\_uuid=1371fdb8-3422-11f1-9e35-0050568f6283, server\_id=31111. Starting replication from file ‘mysql-bin.000039’, position ‘469792571’.  
\*\*\* buffer overflow detected \*\*\*: terminated  
2026-04-22T05:52:27Z UTC - mysqld got signal 6 ;  
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.  
BuildID[sha1]=cd066220e6a3b6f9e15998b712397a960cfc8f88  
Server Version: 8.4.8-8 Percona Server (GPL), Release 8, Revision 1c288264

Thread pointer: 0x0  
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 = 0 thread\_stack 0x80000  
#0 0x562a4fb4167c  
#1 0x562a4fb41acb  
#2 0x7f3e30c6846f  
#3 0x7f3e30cc1554  
#4 0x7f3e30c683bd  
#5 0x7f3e30c4f901  
#6 0x7f3e30c50b89  
#7 0x7f3e30d3e2f8  
#8 0x7f3e30d3dc63  
#9 0x7f3e30d3f364  
#10 0x7f3e18493434  
#11 0x7f3e184966b3  
#12 0x7f3e18493878  
#13 0x7f3e30cbf4a4  
#14 0x7f3e30d31f8b  
#15 0xffffffffffffffff  
Please help us make Percona Server better by reporting any  
bugs at [https://bugs.percona.com/](https://bugs.percona.com/)

You may download the Percona Server operations manual by visiting  
[http://www.percona.com/software/percona-server/](http://www.percona.com/software/percona-server/). You may find information  
in the manual which will help you identify the cause of the crash.  
2026-04-22T05:52:27.000000Z 0 [System] [MY-013951] [Server] 2026-04-22T05:52:27Z UTC - mysqld got signal 6 ;  
2026-04-22T05:52:27.000001Z 0 [System] [MY-013951] [Server] Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.  
2026-04-22T05:52:27.000002Z 0 [System] [MY-013951] [Server] BuildID[sha1]=cd066220e6a3b6f9e15998b712397a960cfc8f88  
2026-04-22T05:52:27.000003Z 0 [System] [MY-013951] [Server] Server Version: 8.4.8-8 Percona Server (GPL), Release 8, Revision 1c288264  
2026-04-22T05:52:27.000004Z 0 [System] [MY-013951] [Server] Thread pointer: 0x0  
2026-04-22T05:52:27.000005Z 0 [System] [MY-013951] [Server] Attempting backtrace. You can use the following information to find out  
2026-04-22T05:52:27.000006Z 0 [System] [MY-013951] [Server] where mysqld died. If you see no messages after this, something went  
2026-04-22T05:52:27.000007Z 0 [System] [MY-013951] [Server] terribly wrong…  
2026-04-22T05:52:27.000008Z 0 [System] [MY-013951] [Server] stack\_bottom = 0 thread\_stack 0x80000  
2026-04-22T05:52:27.000009Z 0 [System] [MY-013951] [Server] #0 0x562a4fb4167c  
2026-04-22T05:52:27.000010Z 0 [System] [MY-013951] [Server] #1 0x562a4fb41acb  
2026-04-22T05:52:27.000011Z 0 [System] [MY-013951] [Server] #2 0x7f3e30c6846f  
2026-04-22T05:52:27.000012Z 0 [System] [MY-013951] [Server] #3 0x7f3e30cc1554  
2026-04-22T05:52:27.000013Z 0 [System] [MY-013951] [Server] #4 0x7f3e30c683bd  
2026-04-22T05:52:27.000014Z 0 [System] [MY-013951] [Server] #5 0x7f3e30c4f901  
2026-04-22T05:52:27.000015Z 0 [System] [MY-013951] [Server] #6 0x7f3e30c50b89  
2026-04-22T05:52:27.000016Z 0 [System] [MY-013951] [Server] #7 0x7f3e30d3e2f8  
2026-04-22T05:52:27.000017Z 0 [System] [MY-013951] [Server] #8 0x7f3e30d3dc63  
2026-04-22T05:52:27.000018Z 0 [System] [MY-013951] [Server] #9 0x7f3e30d3f364  
2026-04-22T05:52:27.000019Z 0 [System] [MY-013951] [Server] #10 0x7f3e18493434  
2026-04-22T05:52:27.000020Z 0 [System] [MY-013951] [Server] #11 0x7f3e184966b3  
2026-04-22T05:52:27.000021Z 0 [System] [MY-013951] [Server] #12 0x7f3e18493878  
2026-04-22T05:52:27.000022Z 0 [System] [MY-013951] [Server] #13 0x7f3e30cbf4a4  
2026-04-22T05:52:27.000023Z 0 [System] [MY-013951] [Server] #14 0x7f3e30d31f8b  
2026-04-22T05:52:27.000024Z 0 [System] [MY-013951] [Server] #15 0xffffffffffffffff  
2026-04-22T05:52:27.000025Z 0 [System] [MY-013951] [Server] Please help us make Percona Server better by reporting any  
2026-04-22T05:52:27.000026Z 0 [System] [MY-013951] [Server] bugs at [https://bugs.percona.com/](https://bugs.percona.com/)  
2026-04-22T05:52:27.000027Z 0 [System] [MY-013951] [Server] You may download the Percona Server operations manual by visiting  
2026-04-22T05:52:27.000028Z 0 [System] [MY-013951] [Server] [http://www.percona.com/software/percona-server/](http://www.percona.com/software/percona-server/). You may find information  
2026-04-22T05:52:27.000029Z 0 [System] [MY-013951] [Server] in the manual which will help you identify the cause of the crash.  
2026-04-22T05:52:31.216119Z 0 [System] [MY-015015] [Server] MySQL Server - start.  
2026-04-22T05:52:31.216156Z 0 [Warning] [MY-010139] [Server] Changed limits: max\_open\_files: 10000 (requested 16594)  
2026-04-22T05:52:31.216160Z 0 [Warning] [MY-010142] [Server] Changed limits: table\_open\_cache: 4895 (requested 8192)  
2026-04-22T05:52:31.490831Z 0 [Warning] [MY-010097] [Server] Insecure configuration for --secure-log-path: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.  
2026-04-22T05:52:31.490921Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.8-8) starting as process 94305  
2026-04-22T05:52:31.501986Z 0 [System] [MY-013951] [Server] A backtrace was processed and added to the main error-log in the appropriate format.  
2026-04-22T05:52:31.508834Z 0 [Warning] [MY-013907] [InnoDB] Deprecated configuration parameters innodb\_log\_file\_size and/or innodb\_log\_files\_in\_group have been used to compute innodb\_redo\_log\_capacity=6710886400. Please use innodb\_redo\_log\_capacity instead.  
2026-04-22T05:52:31.512251Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.  
2026-04-22T05:53:07.627100Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.  
2026-04-22T05:53:07.929843Z 0 [Warning] [MY-000000] [Server] Plugin audit\_log reported: ‘‘audit\_log’ is deprecated and will be removed in a future release. Please use ‘audit\_log\_filter’ instead.’  
2026-04-22T05:53:07.938863Z 0 [Warning] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we’re sending the information to the error-log instead: MY-001287 - ‘validate password plugin’ is deprecated and will be removed in a future release. Please use validate\_password component instead  
\*\*\* buffer overflow detected \*\*\*: terminated  
2026-04-22T05:53:08Z UTC - mysqld got signal 6 ;  
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.  
BuildID[sha1]=cd066220e6a3b6f9e15998b712397a960cfc8f88  
Server Version: 8.4.8-8 Percona Server (GPL), Release 8, Revision 1c288264

Thread pointer: 0x0  
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 = 0 thread\_stack 0x80000  
#0 0x556e477a967c  
#1 0x556e477a9acb  
#2 0x7ff49086846f  
#3 0x7ff4908c1554  
#4 0x7ff4908683bd  
#5 0x7ff49084f901  
#6 0x7ff490850b89  
#7 0x7ff49093e2f8  
#8 0x7ff49093dc63  
#9 0x7ff49093f364  
#10 0x7ff47800d434  
#11 0x7ff4780106b3  
#12 0x7ff47800d878  
#13 0x7ff4908bf4a4  
#14 0x7ff490931f8b  
#15 0xffffffffffffffff  
Please help us make Percona Server better by reporting any  
bugs at [https://bugs.percona.com/](https://bugs.percona.com/)

You may download the Percona Server operations manual by visiting  
[http://www.percona.com/software/percona-server/](http://www.percona.com/software/percona-server/). You may find information  
in the manual which will help you identify the cause of the crash.  
2026-04-22T05:53:08.000000Z 0 [System] [MY-013951] [Server] 2026-04-22T05:53:08Z UTC - mysqld got signal 6 ;  
2026-04-22T05:53:08.000001Z 0 [System] [MY-013951] [Server] Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.  
2026-04-22T05:53:08.000002Z 0 [System] [MY-013951] [Server] BuildID[sha1]=cd066220e6a3b6f9e15998b712397a960cfc8f88  
2026-04-22T05:53:08.000003Z 0 [System] [MY-013951] [Server] Server Version: 8.4.8-8 Percona Server (GPL), Release 8, Revision 1c288264  
2026-04-22T05:53:08.000004Z 0 [System] [MY-013951] [Server] Thread pointer: 0x0  
2026-04-22T05:53:08.000005Z 0 [System] [MY-013951] [Server] Attempting backtrace. You can use the following information to find out  
2026-04-22T05:53:08.000006Z 0 [System] [MY-013951] [Server] where mysqld died. If you see no messages after this, something went  
2026-04-22T05:53:08.000007Z 0 [System] [MY-013951] [Server] terribly wrong…  
2026-04-22T05:53:08.000008Z 0 [System] [MY-013951] [Server] stack\_bottom = 0 thread\_stack 0x80000  
2026-04-22T05:53:08.000009Z 0 [System] [MY-013951] [Server] #0 0x556e477a967c  
2026-04-22T05:53:08.000010Z 0 [System] [MY-013951] [Server] #1 0x556e477a9acb  
2026-04-22T05:53:08.000011Z 0 [System] [MY-013951] [Server] #2 0x7ff49086846f  
2026-04-22T05:53:08.000012Z 0 [System] [MY-013951] [Server] #3 0x7ff4908c1554  
2026-04-22T05:53:08.000013Z 0 [System] [MY-013951] [Server] #4 0x7ff4908683bd  
2026-04-22T05:53:08.000014Z 0 [System] [MY-013951] [Server] #5 0x7ff49084f901  
2026-04-22T05:53:08.000015Z 0 [System] [MY-013951] [Server] #6 0x7ff490850b89  
2026-04-22T05:53:08.000016Z 0 [System] [MY-013951] [Server] #7 0x7ff49093e2f8  
2026-04-22T05:53:08.000017Z 0 [System] [MY-013951] [Server] #8 0x7ff49093dc63  
2026-04-22T05:53:08.000018Z 0 [System] [MY-013951] [Server] #9 0x7ff49093f364  
2026-04-22T05:53:08.000019Z 0 [System] [MY-013951] [Server] #10 0x7ff47800d434  
2026-04-22T05:53:08.000020Z 0 [System] [MY-013951] [Server] #11 0x7ff4780106b3  
2026-04-22T05:53:08.000021Z 0 [System] [MY-013951] [Server] #12 0x7ff47800d878  
2026-04-22T05:53:08.000022Z 0 [System] [MY-013951] [Server] #13 0x7ff4908bf4a4  
2026-04-22T05:53:08.000023Z 0 [System] [MY-013951] [Server] #14 0x7ff490931f8b  
2026-04-22T05:53:08.000024Z 0 [System] [MY-013951] [Server] #15 0xffffffffffffffff  
2026-04-22T05:53:08.000025Z 0 [System] [MY-013951] [Server] Please help us make Percona Server better by reporting any  
2026-04-22T05:53:08.000026Z 0 [System] [MY-013951] [Server] bugs at [https://bugs.percona.com/](https://bugs.percona.com/)  
2026-04-22T05:53:08.000027Z 0 [System] [MY-013951] [Server] You may download the Percona Server operations manual by visiting  
2026-04-22T05:53:08.000028Z 0 [System] [MY-013951] [Server] [http://www.percona.com/software/percona-server/](http://www.percona.com/software/percona-server/). You may find information  
2026-04-22T05:53:08.000029Z 0 [System] [MY-013951] [Server] in the manual which will help you identify the cause of the crash.  
2026-04-22T05:53:12.051458Z 0 [System] [MY-015015] [Server] MySQL Server - start.  
2026-04-22T05:53:12.051491Z 0 [Warning] [MY-010139] [Server] Changed limits: max\_open\_files: 10000 (requested 16594)  
2026-04-22T05:53:12.051495Z 0 [Warning] [MY-010142] [Server] Changed limits: table\_open\_cache: 4895 (requested 8192)  
2026-04-22T05:53:12.331887Z 0 [Warning] [MY-010097] [Server] Insecure configuration for --secure-log-path: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.  
2026-04-22T05:53:12.331993Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.8-8) starting as process 94459  
2026-04-22T05:53:12.336863Z 0 [System] [MY-013951] [Server] A backtrace was processed and added to the main error-log in the appropriate format.  
2026-04-22T05:53:12.341936Z 0 [Warning] [MY-013907] [InnoDB] Deprecated configuration parameters innodb\_log\_file\_size and/or innodb\_log\_files\_in\_group have been used to compute innodb\_redo\_log\_capacity=6710886400. Please use innodb\_redo\_log\_capacity instead.  
2026-04-22T05:53:12.344236Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.  
2026-04-22T05:53:20.739493Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.  
2026-04-22T05:53:20.964534Z 0 [Warning] [MY-000000] [Server] Plugin audit\_log reported: ‘‘audit\_log’ is deprecated and will be removed in a future release. Please use ‘audit\_log\_filter’ instead.’  
\*\*\* buffer overflow detected \*\*\*: terminated  
2026-04-22T05:53:20Z UTC - mysqld got signal 6 ;

Audit log plugin is still installed and the service is up and running.

| audit\_log | ACTIVE | AUDIT | audit\_log.so | GPL |

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [April 22, 2026, 4:09pm UTC](https://forums.percona.com/t/percona-mysql-8-4-8-loop-crashing-audit-related/40699/2 "2026-04-22T16:09:50Z")

</div>

If you are using the audit\_log\_plugin, then you should stop and convert to the audit log component. The plugin does not have active development, whereas the component is the current GA code.

> **[Percona Server for MySQL - Audit log plugin](https://docs.percona.com/percona-server/8.4/audit-log-plugin.html)**
>
> Do not attempt to use audit log filter variables, options, or configuration syntax with the deprecated audit log plugin. Doing so can lead to startup failures, unexpected behavior, or data loss.

---

<div class="post-metadata">

**Author:** ![rafaelpastre](https://avatars.discourse-cdn.com/v4/letter/r/8797f3/32.png) [@rafaelpastre](https://forums.percona.com/u/rafaelpastre)\
**Post date:** [April 23, 2026, 7:08am UTC](https://forums.percona.com/t/percona-mysql-8-4-8-loop-crashing-audit-related/40699/3 "2026-04-23T07:08:25Z")

</div>

Hi Matthew. Thank you for you reply.

I have disable the audit log plugin from all our servers here.

Just for curiosity, the only server I had the crash was the one I had the “audit\_log\_strategy = PERFORMANCE” set.

All the others I still had the plugin enabled and fully working, but they did not have the audit\_log\_strategy set.