innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch.

2024-07-12  2:10:20 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/

240712  2:10:20 [ERROR] mysqld got signal 6 ;

Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.

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.6.18-MariaDB source revision: 887bb3f73555ff8a50138a580ca8308b9b5c069c

key_buffer_size=534773760

read_buffer_size=131072

max_used_connections=32

max_threads=152

thread_count=17

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 856886 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

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 = 0x0 thread_stack 0x40000

0x133d08c <my_print_stacktrace+0x3c> at /usr/local/libexec/mariadbd

0xccbe4f <handle_fatal_signal+0x27f> at /usr/local/libexec/mariadbd

0x8281594af <pthread_sigmask+0x53f> at /lib/libthr.so.3

0x828158a6b <pthread_setschedparam+0x83b> at /lib/libthr.so.3

0x7ffffffff923 <???> at ???

0x82c20e41a <__sys_thr_kill+0xa> at /lib/libc.so.7

0x82c187e64 <__raise+0x34> at /lib/libc.so.7

0x82c2386f9 <abort+0x49> at /lib/libc.so.7

0x12dd9d0 <wsrep_thd_is_local_transaction+0x1d0300> at /usr/local/libexec/mariadbd

0x12b7965 <wsrep_thd_is_local_transaction+0x1aa295> at /usr/local/libexec/mariadbd

0x12e060d <_ZN5tpool19thread_pool_generic13timer_generic3runEv+0x3d> at /usr/local/libexec/mariadbd

0x12e0f17 <_ZN5tpool4task7executeEv+0x27> at /usr/local/libexec/mariadbd

0x12deb56 <_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x76> at /usr/local/libexec/mariadbd

0x12e06e6 <_ZN5tpool19thread_pool_generic13timer_generic3runEv+0x116> at /usr/local/libexec/mariadbd

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains

information that should help you find out what is causing the crash.

Core pattern: %N.core

2024-07-12  2:10:23 0 [Note] Starting MariaDB 10.6.18-MariaDB source revision 887bb3f73555ff8a50138a580ca8308b9b5c069c as process 44023

2024-07-12  2:10:23 0 [Note] mariadbd: Aria engine: starting recovery

recovered pages: 0% 10% 23% 36% 52% 68% 78% 92% 100% (0.0 seconds); tables to flush: 1 0

 (0.0 seconds); 

2024-07-12 12:05:06 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/

240712 12:05:06 [ERROR] mysqld got signal 6 ;

Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.

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.6.18-MariaDB source revision: 887bb3f73555ff8a50138a580ca8308b9b5c069c

key_buffer_size=534773760

read_buffer_size=131072

max_used_connections=41

max_threads=152

thread_count=25

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 856886 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

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 = 0x0 thread_stack 0x40000

0x133d08c <my_print_stacktrace+0x3c> at /usr/local/libexec/mariadbd

0xccbe4f <handle_fatal_signal+0x27f> at /usr/local/libexec/mariadbd

0x8296ea4af <pthread_sigmask+0x53f> at /lib/libthr.so.3

0x8296e9a6b <pthread_setschedparam+0x83b> at /lib/libthr.so.3

0x7ffffffff923 <???> at ???

0x82c9c441a <__sys_thr_kill+0xa> at /lib/libc.so.7

0x82c93de64 <__raise+0x34> at /lib/libc.so.7

0x82c9ee6f9 <abort+0x49> at /lib/libc.so.7

0x12dd9d0 <wsrep_thd_is_local_transaction+0x1d0300> at /usr/local/libexec/mariadbd

0x12b7965 <wsrep_thd_is_local_transaction+0x1aa295> at /usr/local/libexec/mariadbd

0x12e060d <_ZN5tpool19thread_pool_generic13timer_generic3runEv+0x3d> at /usr/local/libexec/mariadbd

0x12e0f17 <_ZN5tpool4task7executeEv+0x27> at /usr/local/libexec/mariadbd

0x12deb56 <_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x76> at /usr/local/libexec/mariadbd

0x12e06e6 <_ZN5tpool19thread_pool_generic13timer_generic3runEv+0x116> at /usr/local/libexec/mariadbd

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains

information that should help you find out what is causing the crash.

Core pattern: %N.core

2024-07-12 12:05:09 0 [Note] Starting MariaDB 10.6.18-MariaDB source revision 887bb3f73555ff8a50138a580ca8308b9b5c069c as process 49358

2024-07-12 12:05:09 0 [Note] mariadbd: Aria engine: starting recovery

recovered pages: 0% 10% 23% 35% 51% 66% 76% 90% 100% (0.0 seconds); tables to flush: 2 1 0

 (0.0 seconds);

2024-07-12 15:11:55 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/

240712 15:11:55 [ERROR] mysqld got signal 6 ;

Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.

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.6.18-MariaDB source revision: 887bb3f73555ff8a50138a580ca8308b9b5c069c

key_buffer_size=534773760

read_buffer_size=131072

max_used_connections=62

max_threads=152

thread_count=46

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 856886 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

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 = 0x0 thread_stack 0x40000

0x133d08c <my_print_stacktrace+0x3c> at /usr/local/libexec/mariadbd

0xccbe4f <handle_fatal_signal+0x27f> at /usr/local/libexec/mariadbd

0x8298604af <pthread_sigmask+0x53f> at /lib/libthr.so.3

0x82985fa6b <pthread_setschedparam+0x83b> at /lib/libthr.so.3

0x7ffffffff923 <???> at ???

0x82c70b41a <__sys_thr_kill+0xa> at /lib/libc.so.7

0x82c684e64 <__raise+0x34> at /lib/libc.so.7

0x82c7356f9 <abort+0x49> at /lib/libc.so.7

0x12dd9d0 <wsrep_thd_is_local_transaction+0x1d0300> at /usr/local/libexec/mariadbd

0x12b7965 <wsrep_thd_is_local_transaction+0x1aa295> at /usr/local/libexec/mariadbd

0x12e060d <_ZN5tpool19thread_pool_generic13timer_generic3runEv+0x3d> at /usr/local/libexec/mariadbd

0x12e0f17 <_ZN5tpool4task7executeEv+0x27> at /usr/local/libexec/mariadbd

0x12deb56 <_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x76> at /usr/local/libexec/mariadbd

0x12e06e6 <_ZN5tpool19thread_pool_generic13timer_generic3runEv+0x116> at /usr/local/libexec/mariadbd

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains

information that should help you find out what is causing the crash.

Core pattern: %N.core

2024-07-12 15:11:57 0 [Note] Starting MariaDB 10.6.18-MariaDB source revision 887bb3f73555ff8a50138a580ca8308b9b5c069c as process 8742

2024-07-12 15:11:57 0 [Note] Starting MariaDB 10.6.18-MariaDB source revision 887bb3f73555ff8a50138a580ca8308b9b5c069c as process 8742

2024-07-12 15:11:57 0 [Note] InnoDB: Compressed tables use zlib 1.3.1

2024-07-12 15:11:57 0 [Note] InnoDB: Using transactional memory

2024-07-12 15:11:57 0 [Note] InnoDB: Number of pools: 1

2024-07-12 15:11:57 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions

2024-07-12 15:11:57 0 [Note] InnoDB: Initializing buffer pool, total size = 4294967296, chunk size = 134217728

2024-07-12 15:11:57 0 [Note] InnoDB: Completed initialization of buffer pool

2024-07-12 15:11:57 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=8323167881,8403345778

2024-07-12 15:11:58 0 [Note] InnoDB: 15 transaction(s) which must be rolled back or cleaned up in total 138688 row operations to undo

2024-07-12 15:11:58 0 [Note] InnoDB: Trx id counter is 33606

2024-07-12 15:11:58 0 [Note] InnoDB: To recover: 6144 pages

2024-07-12 15:11:58 0 [Note] InnoDB: 128 rollback segments are active.

2024-07-12 15:11:58 0 [Note] InnoDB: Rolled back recovered transaction 33604

2024-07-12 15:11:58 0 [Note] InnoDB: Starting in background the rollback of recovered transactions

2024-07-12 15:11:58 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"

2024-07-12 15:11:58 0 [Note] InnoDB: Creating shared tablespace for temporary tables

2024-07-12 15:11:58 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

2024-07-12 15:11:58 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.

2024-07-12 15:11:58 0 [Note] InnoDB: 10.6.18 started; log sequence number 8403353498; transaction id 33608

2024-07-12 15:11:58 0 [Note] InnoDB: Loading buffer pool(s) from /home/mysql/ib_buffer_pool

2024-07-12 15:11:58 0 [Note] Plugin 'FEEDBACK' is disabled.

2024-07-12 15:11:58 0 [Warning] 'innodb-buffer-pool-instances' was removed. It does nothing now and exists only for compatibility with old my.cnf files.

2024-07-12 15:11:58 0 [Warning] 'innodb-buffer-pool-instances' was removed. It does nothing now and exists only for compatibility with old my.cnf files.

2024-07-12 15:11:58 0 [Note] InnoDB: Buffer pool(s) load completed at 240712 15:11:58

2024-07-12 15:11:58 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.

2024-07-12 15:11:58 0 [Note] DDL_LOG: Crash recovery executed 15 entries

2024-07-12 15:11:58 0 [Note] Server socket created on IP: '192.168.22.95'.

2024-07-12 15:11:58 0 [Note] /usr/local/libexec/mariadbd: ready for connections.

Version: '10.6.18-MariaDB'  socket: '/var/db/mysql/mysql.sock'  port: 3306  FreeBSD Ports

2024-07-12 15:11:58 0 [Note] InnoDB: Rolled back recovered transaction 33362

2024-07-12 15:11:59 0 [Note] InnoDB: Rolled back recovered transaction 32862

2024-07-12 15:11:59 0 [Note] InnoDB: Rolled back recovered transaction 33594

2024-07-12 15:11:59 0 [Note] InnoDB: Rolled back recovered transaction 33593

2024-07-12 15:11:59 0 [Note] InnoDB: Rolled back recovered transaction 33597

2024-07-12 15:11:59 0 [Note] InnoDB: Rolled back recovered transaction 33589

2024-07-12 15:11:59 0 [Note] InnoDB: Rolled back recovered transaction 33573

2024-07-12 15:11:59 0 [Note] InnoDB: Rolled back recovered transaction 33592

2024-07-12 15:11:59 0 [Note] InnoDB: Rolled back recovered transaction 33599

2024-07-12 15:11:59 0 [Note] InnoDB: Rolled back recovered transaction 33591

2024-07-12 15:12:00 0 [Note] InnoDB: Rolled back recovered transaction 33050

2024-07-12 15:12:00 0 [Note] InnoDB: Rolled back recovered transaction 33596

2024-07-12 15:12:00 0 [Note] InnoDB: Rolled back recovered transaction 33595

2024-07-12 15:12:00 0 [Note] InnoDB: Rolled back recovered transaction 33489

2024-07-12 15:12:00 0 [Note] InnoDB: Rollback of non-prepared transactions completed

2024-07-12 15:12:37 29 [Note] InnoDB: Cannot close file ./db6068/IMPACT_IMPORT_EDT.ibd because of pending fsync

2024-07-12 15:12:43 12 [Warning] InnoDB: Could not free any blocks in the buffer pool! 259584 blocks are in use and 0 free. Consider increasing innodb_buffer_pool_size.

2024-07-12 15:22:58 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/

240712 15:22:58 [ERROR] mysqld got signal 6 ;

Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.

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.6.18-MariaDB source revision: 887bb3f73555ff8a50138a580ca8308b9b5c069c

key_buffer_size=534773760

read_buffer_size=131072

max_used_connections=31

max_threads=152

thread_count=31

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 856886 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

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 = 0x0 thread_stack 0x40000

0x133d08c <my_print_stacktrace+0x3c> at /usr/local/libexec/mariadbd

0xccbe4f <handle_fatal_signal+0x27f> at /usr/local/libexec/mariadbd

0x8284234af <pthread_sigmask+0x53f> at /lib/libthr.so.3

0x828422a6b <pthread_setschedparam+0x83b> at /lib/libthr.so.3

0x7ffffffff923 <???> at ???

0x82b80841a <__sys_thr_kill+0xa> at /lib/libc.so.7

0x82b781e64 <__raise+0x34> at /lib/libc.so.7

0x82b8326f9 <abort+0x49> at /lib/libc.so.7

0x12dd9d0 <wsrep_thd_is_local_transaction+0x1d0300> at /usr/local/libexec/mariadbd

0x12b7965 <wsrep_thd_is_local_transaction+0x1aa295> at /usr/local/libexec/mariadbd

0x12e060d <_ZN5tpool19thread_pool_generic13timer_generic3runEv+0x3d> at /usr/local/libexec/mariadbd

0x12e0f17 <_ZN5tpool4task7executeEv+0x27> at /usr/local/libexec/mariadbd

0x12deb56 <_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x76> at /usr/local/libexec/mariadbd

0x12e06e6 <_ZN5tpool19thread_pool_generic13timer_generic3runEv+0x116> at /usr/local/libexec/mariadbd

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains

information that should help you find out what is causing the crash.

Core pattern: %N.core

2024-07-12 15:23:00 0 [Note] Starting MariaDB 10.6.18-MariaDB source revision 887bb3f73555ff8a50138a580ca8308b9b5c069c as process 54066

2024-07-12 15:23:00 0 [Note] InnoDB: Compressed tables use zlib 1.3.1

2024-07-12 15:23:00 0 [Note] InnoDB: Using transactional memory

2024-07-12 15:23:00 0 [Note] InnoDB: Number of pools: 1

2024-07-12 15:23:00 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions

2024-07-12 15:23:00 0 [Note] InnoDB: Initializing buffer pool, total size = 4294967296, chunk size = 134217728

2024-07-12 15:23:00 0 [Note] InnoDB: Completed initialization of buffer pool

2024-07-12 15:23:00 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=12515738184,12595554214

2024-07-12 15:23:00 0 [Note] InnoDB: 8 transaction(s) which must be rolled back or cleaned up in total 1618 row operations to undo

2024-07-12 15:23:00 0 [Note] InnoDB: Trx id counter is 50147

2024-07-12 15:23:00 0 [Note] InnoDB: To recover: 5571 pages

2024-07-12 15:23:00 0 [Note] InnoDB: 128 rollback segments are active.

2024-07-12 15:23:00 0 [Note] InnoDB: Rolled back recovered transaction 50142

2024-07-12 15:23:00 0 [Note] InnoDB: Starting in background the rollback of recovered transactions

2024-07-12 15:23:00 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"

2024-07-12 15:23:00 0 [Note] InnoDB: Creating shared tablespace for temporary tables

2024-07-12 15:23:00 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

2024-07-12 15:23:00 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.

2024-07-12 15:23:00 0 [Note] InnoDB: 10.6.18 started; log sequence number 12595555320; transaction id 50149

2024-07-12 15:23:00 0 [Note] InnoDB: Loading buffer pool(s) from /home/mysql/ib_buffer_pool

2024-07-12 15:23:00 0 [Note] Plugin 'FEEDBACK' is disabled.

2024-07-12 15:23:00 0 [Warning] 'innodb-buffer-pool-instances' was removed. It does nothing now and exists only for compatibility with old my.cnf files.

2024-07-12 15:23:00 0 [Warning] 'innodb-buffer-pool-instances' was removed. It does nothing now and exists only for compatibility with old my.cnf files.

2024-07-12 15:23:00 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.

2024-07-12 15:23:00 0 [Note] InnoDB: Buffer pool(s) load completed at 240712 15:23:00

2024-07-12 15:23:00 0 [Note] DDL_LOG: Crash recovery executed 3 entries

2024-07-12 15:23:00 0 [Note] Server socket created on IP: '192.168.22.95'.

2024-07-12 15:23:00 0 [Note] /usr/local/libexec/mariadbd: ready for connections.

Version: '10.6.18-MariaDB'  socket: '/var/db/mysql/mysql.sock'  port: 3306  FreeBSD Ports

2024-07-12 15:23:00 0 [Note] InnoDB: Rolled back recovered transaction 50082

2024-07-12 15:23:00 0 [Note] InnoDB: Rolled back recovered transaction 50022

2024-07-12 15:23:00 0 [Note] InnoDB: Rolled back recovered transaction 50141

2024-07-12 15:23:00 0 [Note] InnoDB: Rolled back recovered transaction 50113

2024-07-12 15:23:00 0 [Note] InnoDB: Rolled back recovered transaction 50140

2024-07-12 15:23:00 0 [Note] InnoDB: Rolled back recovered transaction 50139

2024-07-12 15:23:00 0 [Note] InnoDB: Rolled back recovered transaction 50116

2024-07-12 15:23:00 0 [Note] InnoDB: Rollback of non-prepared transactions completed

2024-07-12 15:23:54 29 [Note] InnoDB: Cannot close file ./db10004/IMPACT_IMPORT_EDT.ibd because of 40 pending operations and pending fsync

2024-07-12 15:24:09 0 [Warning] InnoDB: Could not free any blocks in the buffer pool! 259584 blocks are in use and 0 free. Consider increasing innodb_buffer_pool_size.

2024-07-12 15:24:15 12 [Note] InnoDB: Cannot close file ./db5381/IMPACT_IMPORT_EDT.ibd because of pending fsync

2024-07-12 15:24:20 19 [Note] InnoDB: Cannot close file ./db5440/IMPACT_IMPORT_EDT.ibd because of pending fsync

2024-07-12 15:24:25 22 [Note] InnoDB: Cannot close file ./db5243/RESSOURCE.ibd because of pending fsync

2024-07-12 15:24:40 43 [Note] InnoDB: Cannot close file ./db6069/IMPACT_IMPORT_EDT.ibd because of pending fsync

2024-07-12 15:24:49 29 [Note] InnoDB: Cannot close file ./mysql/innodb_index_stats.ibd because of pending fsync

2024-07-12 15:24:57 49 [Note] InnoDB: Cannot close file ./mysql/innodb_table_stats.ibd because of pending fsync

2024-07-12 15:25:15 32 [Note] InnoDB: Cannot close file ./mysql/innodb_index_stats.ibd because of pending fsync

2024-07-12 15:25:28 35 [Note] InnoDB: Cannot close file ./db5587/IMPACT_IMPORT_EDT.ibd because of 68 pending operations and pending fsync

2024-07-12 15:25:35 39 [Note] InnoDB: Cannot close file ./mysql/innodb_table_stats.ibd because of 2 pending operations and pending fsync

2024-07-12 15:25:40 47 [Note] InnoDB: Cannot close file ./db3118/RESSOURCE.ibd because of pending fsync

2024-07-12 15:25:51 53 [Note] InnoDB: Cannot close file ./db7212/EVENEMENT.ibd because of pending fsync

2024-07-12 15:26:02 80 [Note] InnoDB: Cannot close file ./db5438/EVENEMENT.ibd because of 11 pending operations and pending fsync

2024-07-12 15:26:10 68 [Note] InnoDB: Cannot close file ./db5303/EVENEMENT.ibd because of pending fsync

2024-07-12 15:26:16 87 [Note] InnoDB: Cannot close file ./mysql/innodb_index_stats.ibd because of 3 pending operations and pending fsync

2024-07-12 15:26:21 87 [Note] InnoDB: Cannot close file ./mysql/innodb_table_stats.ibd because of 1 pending operations and pending fsync

2024-07-12 15:26:29 83 [Note] InnoDB: Cannot close file ./db5673/IMPACT_IMPORT_EDT.ibd because of 96 pending operations and pending fsync

2024-07-12 15:26:38 87 [Note] InnoDB: Cannot close file ./db115001/IMPACT_IMPORT_EDT.ibd because of pending fsync

2024-07-12 15:26:46 125 [Note] InnoDB: Cannot close file ./db5201/ACTIVITE.ibd because of pending fsync

2024-07-12 15:26:51 119 [Note] InnoDB: Cannot close file ./db5382/5382_PM_PROP.ibd because of 64 pending operations

2024-07-12 15:26:56 125 [Note] InnoDB: Cannot close file ./db5215/EVENEMENT.ibd because of pending fsync

2024-07-12 15:27:01 131 [Note] InnoDB: Cannot close file ./db5215/EVENEMENT.ibd because of 4 pending operations

2024-07-12 15:27:09 139 [Note] InnoDB: Cannot close file ./mysql/innodb_table_stats.ibd because of 3 pending operations

2024-07-12 15:27:14 163 [Note] InnoDB: Cannot close file ./mobilite/MOBILITE_JETON_AUTH.ibd because of pending fsync

2024-07-12 15:57:35 0 [Note] /usr/local/libexec/mariadbd (initiated by: unknown): Normal shutdown

2024-07-12 15:57:35 0 [Note] InnoDB: FTS optimize thread exiting.

2024-07-12 15:57:35 0 [Note] InnoDB: Starting shutdown...

2024-07-12 15:57:35 0 [Note] InnoDB: Dumping buffer pool(s) to /home/mysql/ib_buffer_pool

2024-07-12 15:57:35 0 [Note] InnoDB: Restricted to 64896 pages due to innodb_buf_pool_dump_pct=25

2024-07-12 15:57:35 0 [Note] InnoDB: Buffer pool(s) dump completed at 240712 15:57:35

2024-07-12 15:57:35 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"

2024-07-12 15:57:35 0 [Note] InnoDB: Shutdown completed; log sequence number 30535712276; transaction id 197395

2024-07-12 15:57:35 0 [Note] /usr/local/libexec/mariadbd: Shutdown complete

2024-07-12 15:57:49 0 [Note] Starting MariaDB 10.6.18-MariaDB source revision 887bb3f73555ff8a50138a580ca8308b9b5c069c as process 59359

2024-07-12 15:57:49 0 [Note] InnoDB: Compressed tables use zlib 1.3.1

2024-07-12 15:57:49 0 [Note] InnoDB: Using transactional memory

2024-07-12 15:57:49 0 [Note] InnoDB: Number of pools: 1

2024-07-12 15:57:49 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions

2024-07-12 15:57:49 0 [Note] InnoDB: Initializing buffer pool, total size = 4294967296, chunk size = 134217728

2024-07-12 15:57:49 0 [Note] InnoDB: Completed initialization of buffer pool

2024-07-12 15:57:49 0 [Note] InnoDB: 128 rollback segments are active.

2024-07-12 15:57:49 0 [Note] InnoDB: Creating shared tablespace for temporary tables

2024-07-12 15:57:49 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

2024-07-12 15:57:49 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.

2024-07-12 15:57:49 0 [Note] InnoDB: 10.6.18 started; log sequence number 30535712276; transaction id 197397

2024-07-12 15:57:49 0 [Note] Plugin 'FEEDBACK' is disabled.

2024-07-12 15:57:49 0 [Note] InnoDB: Loading buffer pool(s) from /home/mysql/ib_buffer_pool

2024-07-12 15:57:49 0 [Warning] 'innodb-buffer-pool-instances' was removed. It does nothing now and exists only for compatibility with old my.cnf files.

2024-07-12 15:57:49 0 [Warning] 'innodb-buffer-pool-instances' was removed. It does nothing now and exists only for compatibility with old my.cnf files.

2024-07-12 15:57:49 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.

2024-07-12 15:57:49 0 [Note] Server socket created on IP: '192.168.22.95'.

2024-07-12 15:57:49 0 [Note] /usr/local/libexec/mariadbd: ready for connections.

Version: '10.6.18-MariaDB'  socket: '/var/db/mysql/mysql.sock'  port: 3306  FreeBSD Ports

2024-07-12 15:57:51 0 [Note] InnoDB: Buffer pool(s) load completed at 240712 15:57:51