MySQLd.log

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 959844 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...
terribly wrong...
2023-01-25 14:23:33 0 [ERROR] InnoDB: Page [page id: space=17110, page number=144] log sequence number 169286414473 is in the$
2023-01-25 14:23:33 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the I$
stack_bottom = 0x0 thread_stack 0x49000
2023-01-25 14:23:33 0 [ERROR] InnoDB: Page [page id: space=17110, page number=1] log sequence number 169281554651 is in the f$
2023-01-25 14:23:33 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the I$
2023-01-25 14:23:33 0 [ERROR] InnoDB: Page [page id: space=17110, page number=146] log sequence number 169289479260 is in the$
2023-01-25 14:23:33 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the I$
2023-01-25 14:23:33 0 [ERROR] InnoDB: Page [page id: space=17110, page number=3] log sequence number 169283713761 is in the f$
2023-01-25 14:23:33 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the I$
2023-01-25 14:23:33 0 [ERROR] InnoDB: Page [page id: space=17110, page number=415] log sequence number 169270030439 is in the$
2023-01-25 14:23:33 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the I$
2023-01-25 14:23:33 0 [ERROR] InnoDB: Page [page id: space=14302, page number=3] log sequence number 169293235532 is in the f$
2023-01-25 14:23:33 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the I$
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55f69f46836e]
/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x55f69eefc95f]
sigaction.c:0(__restore_rt)[0x7f630310c630]
:0(__GI_raise)[0x7f6302d65387]
:0(__GI_abort)[0x7f6302d66a78]
/usr/sbin/mysqld(+0x4f60e4)[0x55f69ec320e4]
/usr/sbin/mysqld(+0xaadf64)[0x55f69f1e9f64]
/usr/sbin/mysqld(+0x9bce02)[0x55f69f0f8e02]
/usr/sbin/mysqld(+0x9be565)[0x55f69f0fa565]
/usr/sbin/mysqld(+0x4f0c8a)[0x55f69ec2cc8a]
/usr/sbin/mysqld(+0xafa177)[0x55f69f236177]
/usr/sbin/mysqld(+0xb61cf3)[0x55f69f29dcf3]
/usr/sbin/mysqld(+0xa6ce18)[0x55f69f1a8e18]
pthread_create.c:0(start_thread)[0x7f6303104ea5]
/lib64/libc.so.6(clone+0x6d)[0x7f6302e2d9fd]
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:
Fatal signal 11 while backtracing

Messages Log File

 File: messages

Jan 25 04:07:37 serverhostname systemd: mariadb.service: main process exited, code=killed, status=11/SEGV
Jan 25 04:07:37 serverhostname systemd: Failed to start MariaDB 10.3.34 database server.
Jan 25 04:07:37 serverhostname systemd: Unit mariadb.service entered failed state.