maria db server not starting up

dear community,

i try to start the mysql server, but no chance got an error:
root@web01:~# systemctl status mariadb.service
● mariadb.service - MariaDB database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mysql.service.d
└─limits.conf
Active: failed (Result: exit-code) since Sat 2022-01-01 20:19:39 CET; 13s ago
Process: 24163 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 24073 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VA
Process: 24062 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 24054 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 24163 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"

Jän 01 20:19:35 web01 systemd[1]: Starting MariaDB database server...
Jän 01 20:19:36 web01 mysqld[24163]: 2022-01-01 20:19:36 3070323136 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_
Jän 01 20:19:36 web01 mysqld[24163]: 2022-01-01 20:19:36 3070323136 [Note] /usr/sbin/mysqld (mysqld 10.1.26-MariaDB-0+deb9u1) starting as process 24163 ...
Jän 01 20:19:39 web01 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jän 01 20:19:39 web01 systemd[1]: Failed to start MariaDB database server.
Jän 01 20:19:39 web01 systemd[1]: mariadb.service: Unit entered failed state.
Jän 01 20:19:39 web01 systemd[1]: mariadb.service: Failed with result 'exit-code'.

var/log/mysql.log:

-01-01 20:19:36 3070323136 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
2022-01-01 20:19:36 3070323136 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2022-01-01 20:19:36 3070323136 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2022-01-01 20:19:36 3070323136 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-01 20:19:36 3070323136 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-01 20:19:36 3070323136 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-01-01 20:19:36 3070323136 [Note] InnoDB: Compressed tables use zlib 1.2.8
2022-01-01 20:19:36 3070323136 [Note] InnoDB: Using Linux native AIO
2022-01-01 20:19:36 3070323136 [Note] InnoDB: Using generic crc32 instructions
2022-01-01 20:19:36 3070323136 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2022-01-01 20:19:36 3070323136 [Note] InnoDB: Completed initialization of buffer pool
2022-01-01 20:19:36 3070323136 [Note] InnoDB: Highest supported file format is Barracuda.
2022-01-01 20:19:36 3070323136 [Note] InnoDB: 128 rollback segment(s) are active.
2022-01-01 20:19:36 3070323136 [Note] InnoDB: Waiting for purge to start
2022-01-01 20:19:36 3070323136 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.1 started; log sequence number 216230178490
2022-01-01 20:19:36 2453666624 [Note] InnoDB: Dumping buffer pool(s) not yet started
2022-01-01 20:19:36 3070323136 [Note] Plugin 'FEEDBACK' is disabled.
2022-01-01 20:19:36 3070323136 [Note] Recovering after a crash using tc.log
2022-01-01 20:19:36 3070323136 [ERROR] Can't init tc log
2022-01-01 20:19:36 3070323136 [ERROR] Aborting


can anybody helps me?

thank you so much

 

Me too

 

i has found the solution. if the tc.log file is there, then i get this error.
solved through
rm /var/lib/mysql/tc.log

thank you