On trying to start mysql.server start
./usr/local/bin/mysql.server: line 264: kill: (12262) - No such process ERROR!
On trying to connect mysql -uroot
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
/usr/local/var/mysqlib_logfile0 & ib_logfile1 files.
@musa11971 Perfect!
Hi all, I’ve been following this thread and noticed several people facing issues with brew MariaDB. This led me to develop SnapDB, a macOS database management tool that fully supports MariaDB (including dependency-free installation, management, and configuration). If anyone here is still searching for a workaround, feel free to check it out—it might save you some time. Happy to answer questions!
There are many cases for mariadb or any other service to stop working properly on the computer.
causes
They can be the specific cause in this type of problems and for that a generic question in the communities to it does not always lead you to the answer/solution valid since the causes are several/different.
In my case I have followed the guidelines above but it did not solve the problem. And one of those was to execute the process of direct call to mariadb and its handler that uses the socket by default, this when executed tells you which threads and dependencies it has, it draws you technically where everything happens, besides showing you how it works.
# mysqld
preview it is important to see
# mysqld --verbose --help | grep “socket”
To locate exactly where your configurations are in the system and what values they are taking.
My specific case was a memory error and a break when initializing services and dependencies which broke everything and had no service and could not schedule a three hours!!!
It is solved by making a backup of the tc.log file (same path in #coment) delete the last one and run
# mysqld
so that the instances in mysql.servers regenerate the paths and processes to regenerate the path and be able to start the service with the correct configuration without breaking or forcing any process to act arbitrarily because that is the workflow where there is a problem you have to investigate to solve it and start everything again well.
Do yourself a favor as a developer read the warnings that the prompt returns and the errors that cause them, it will help you a lot.
Happy code.
Deleting the data files (
ib_logfile0and others) works, but the important question is WHY.In my case the error occurred after upgrading MariaDB. Looking at the error log, INNODB was complaining that the logfiles had been created by a previous version:
Installing the earlier version instead made it work again. I have not researched how to do the upgrade safely.