2025-05-20 13:25:28 27547146 [Warning] Aborted connection 27547146 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets)
2025-05-20 13:25:28 27547145 [Warning] Aborted connection 27547145 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets)
2025-05-20 13:56:13 27552204 [Warning] Aborted connection 27552204 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got timeout reading communication packets)
250521  5:24:24 [ERROR] mysqld got signal 11 ;
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.11.5-MariaDB-log source revision: 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c
key_buffer_size=67108864
read_buffer_size=131072
max_used_connections=480
max_threads=802
thread_count=499
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1831964 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7eeae8000c58
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 = 0x7eeea9d95b98 thread_stack 0x49000
2025-05-21  5:24:27 29069863 [Warning] Aborted connection 29069863 to db: 'unconnected' user: 'unauthenticated' host: '10.76.24.82' (This connection closed normally without authentication)             
/usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55a5d46ca12e]
mysys/stacktrace.c:216(my_print_stacktrace)[0x55a5d41c35b5]
/lib64/libpthread.so.0(+0x12cf0)[0x7f1769afbcf0]
sql/sql_yacc.yy:13278(MYSQLparse(THD*))[0x55a5d41570c8]
sql/sql_parse.cc:10394(parse_sql(THD*, Parser_state*, Object_creation_ctx*, bool))[0x55a5d3f7981a]
sql/sql_parse.cc:7988(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x55a5d3f75a1a]
sql/sql_parse.cc:1896(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x55a5d3f7f6e6]
sql/sql_parse.cc:1407(do_command(THD*, bool))[0x55a5d3f80dab]
sql/sql_connect.cc:1416(do_handle_one_connection(CONNECT*, bool))[0x55a5d4094977]
sql/sql_connect.cc:1318(handle_one_connection)[0x55a5d4094cbd]
perfschema/pfs.cc:2204(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x55a5d43cac9d]
/lib64/libpthread.so.0(+0x81ca)[0x7f1769af11ca]
/lib64/libc.so.6(clone+0x43)[0x7f1768e41e73]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7eeae8010ad0): Insert Into ActiveSessions(NASIP,NASIdentifier,NASPort,AcctSessionId,AcctMultiSessionId,AlepoSessionId,NASIndex,ParentSessionId,UserIndex,UserID,GroupIndex,MainGroupIndex,NetworkServiceName,UplinkSpeed,DownlinkSpeed,SpeedHint,Service,UserIP,StartDateTime,SessionExpiryTime,CallerId,CalledStationId,LastUpdateTime,ExternalChargingIdentifier,PreCleanupAction,RadiusServerName,UniqueUserSessionId,NASPortType,SessionTimeout,NASPortId,Class,FramedInterfaceId,FramedIPv6Prefix,BillingSystemCorrelationId,UserSpeed,FramedIPv6Address,ChargingSystemCorrelationId,DelegateIPv6Prefix,FramedPool,FilterID) Values('203.135.19.117','HWI-KHI-PKCP-NPE-N4X16-1',3930066317,'HWI-KHI072413469000001bd1c6AAABEN','','HWI-KHI072413469000001bd1c6AAABEN03158761159VDSL',3201,'',49272031,'03158761159VDSL',404,404,'','','','',1201,3065130430,'2025-05-21 05:24:24','2025-05-21 06:31:14','9c:6f:52:1d:b1:5b','','2025-05-21 05:24:24','',0,'AAA3-ILB','',13,0,'10.138.8.58-S3-KHI-TsraChkLND-H-M eth 0/1/0/21:10','','','','','672_10Mbps_5Mbps','','','','','priority_4')    

Connection ID (thread ID): 15109639
Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off,hash_join_cardinality=off

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            8388608              unlimited            bytes
Max core file size        unlimited            unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             2061710              2061710              processes
Max open files            32768                32768                files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       2061710              2061710              signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0
Max realtime priority     0                    0       
Max realtime timeout      unlimited            unlimited            us
Core pattern: /var/coredumps/core.%e.%p  

Kernel version: Linux version 4.18.0-477.13.1.el8_8.x86_64 (mockbuild@x86-vm-08.build.eng.bos.redhat.com) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-18) (GCC)) #1 SMP Thu May 18 10:27:05 EDT 2023

2025-05-21  5:25:47 0 [Note] Starting MariaDB 10.11.5-MariaDB-log source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 1354619
2025-05-21  5:25:47 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2025-05-21  5:25:47 0 [Note] InnoDB: Number of transaction pools: 1
2025-05-21  5:25:47 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2025-05-21  5:25:47 0 [Note] InnoDB: Using Linux native AIO
2025-05-21  5:25:47 0 [Note] InnoDB: Initializing buffer pool, total size = 150.000GiB, chunk size = 2.344GiB
2025-05-21  5:25:47 0 [Note] InnoDB: Completed initialization of buffer pool
2025-05-21  5:25:48 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2025-05-21  5:25:50 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=75861037278575
2025-05-21  5:25:51 0 [Note] InnoDB: End of log at LSN=75861139704608
2025-05-21  5:25:51 0 [Note] InnoDB: 30 transaction(s) which must be rolled back or cleaned up in total 30 row operations to undo
2025-05-21  5:25:51 0 [Note] InnoDB: Trx id counter is 251415345910
2025-05-21  5:25:51 0 [Note] InnoDB: To recover: 115423 pages
2025-05-21  5:26:01 0 [Note] InnoDB: Last binlog file './db1-binary.395973', position 132537689
2025-05-21  5:26:01 0 [Note] InnoDB: 128 rollback segments are active.
2025-05-21  5:26:01 0 [Note] InnoDB: Starting in background the rollback of recovered transactions  