How to solve MariaDB memory issue


Suddenly, MariaDB stopped working and was unable to start. The logs reffer to some memory issue related to InnoDB. After several hours trying to solve it reading some forums and sources of information, the mysql sever is still down, unable to start.

Maybe this terminal output can help.

mariadb.service - MariaDB 10.1.37 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
Active: failed (Result: exit-code) since Fri 2019-03-08 19:35:41 UTC; 18s ago
Docs: man:mysqld(8)
Process: 14298 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION 
Process: 14186 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bi
Process: 14182 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exi
Process: 14178 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exit
Main PID: 14298 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"

Mar 08 19:35:40 blaudat-debian-s-3vcpu-1gb-fra1-01 systemd[1]: Starting MariaDB 10.1.37 database ser
Mar 08 19:35:41 blaudat-debian-s-3vcpu-1gb-fra1-01 mysqld[14298]: 2019-03-08 19:35:41 13967806592249
Mar 08 19:35:41 blaudat-debian-s-3vcpu-1gb-fra1-01 systemd[1]: mariadb.service: Main process exited,
Mar 08 19:35:41 blaudat-debian-s-3vcpu-1gb-fra1-01 systemd[1]: Failed to start MariaDB 10.1.37 datab
Mar 08 19:35:41 blaudat-debian-s-3vcpu-1gb-fra1-01 systemd[1]: mariadb.service: Unit entered failed 
Mar 08 19:35:41 blaudat-debian-s-3vcpu-1gb-fra1-01 systemd[1]: mariadb.service: Failed with result 

Thank you very much in advance.

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

THANK YOU @etr !!!


thank you very much !!!

Hiii, I found the solution… :)

Delete the file /var/lib/mysql/tc.log reboot the system and start maria db again. Also ensure there is enough space in /var and /tmp if you’re using separate partition for them.

It seems that the /var partition got full and so mariadb failed to create tc.log file and ended up creating a 0 bit file which is causing the problem.

Hope it helps!

Very nice of you, jarland.

I’m going to read this article and insisting to find some solutions.

Hope to confirm in a short time.