2025-08-10 17:22:39 1359654 [ERROR] mariadbd: Error writing file '(null)' (errno: 0 "Internal error/check (Not system error)")

2025-08-10 17:22:39 1359654 [ERROR] Could not use /data/HCL/mariadb/mariadb-binlog/Starhuab_Prd for logging (error 2). Turning logging off for the whole duration of the MariaDB server process. To turn it on again: fix the cause, shutdown the MariaDB server and restart it.

2025-08-10 17:22:39 1359654 [ERROR] Could not use /data/HCL/mariadb/mariadb-binlog/Starhuab_Prd.001773 for logging (error 0). Turning logging off for the whole duration of the MariaDB server process. To turn it on again: fix the cause, shutdown the MariaDB server and restart it.

2025-08-10 17:22:39 1359654 [ERROR] mariadbd: Error writing file '(null)' (errno: 0 "Internal error/check (Not system error)")

250810 17:22:39 [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.5.9-MariaDB-log

key_buffer_size=134217728

read_buffer_size=131072

max_used_connections=261

max_threads=5002

thread_count=263

It is possible that mysqld could use up to

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

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

2025-08-10 17:24:24 0 [Note] InnoDB: Transaction 206913230 in prepared state after recovery

2025-08-10 17:24:24 0 [Note] InnoDB: Transaction contains changes to 1 rows

2025-08-10 17:24:24 0 [Note] InnoDB: Transaction 206913226 in prepared state after recovery

2025-08-10 17:24:24 0 [Note] InnoDB: Transaction contains changes to 4 rows

2025-08-10 17:24:24 0 [Note] InnoDB: 7 transactions in prepared state after recovery

2025-08-10 17:24:24 0 [Note] Found 7 prepared transaction(s) in InnoDB

2025-08-10 17:24:24 0 [ERROR] Found 7 prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or tc.log file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.

2025-08-10 17:24:24 0 [ERROR] Aborting

250810 17:24:45 mysqld_safe mysqld from pid file /data/HCL/mariadb/pid/PRD_puawsapse1stardbs1001.pid ended

250810 18:35:26 mysqld_safe Starting mariadbd daemon with databases from /data/HCL/mariadb/data

2025-08-10 18:35:26 0 [Note] /data/HCL/mariadb/bin/mariadbd (mysqld 10.5.9-MariaDB-log) starting as process 224801 ...