Solution for MySQL / MariaDB Start Issue on MacOS

mysq-mariadb-macos-start-issue.md

Solution for MySQL / MariaDB Start Issue on MacOS

Errors

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)

Solution

• Stop MySQL / MariaDB.
• Go to /usr/local/var/mysql
• Delete ib_logfile0 & ib_logfile1 files.
• Try to start now, It should work 😎

/opt/homebrew/etc/my.cnf

Thanks, after spending a whole day - finally found it here - /opt/homebrew/var/mysql

thanks a lot, you save my day

After updating to macOS Sonoma 14 the connection with 127.0.0.1 was not working anymore (localhost was working correct).

I added this:

[mysqld]
bind-address = 127.0.0.1
skip-name-resolve = 1

at the bottom of /opt/homebrew/etc/my.cnf and ran the command brew services restart mariadb to fix it.

Thank you!! You are a lifesaver. this worked for me

/Applications/XAMPP/xamppfiles/var/mysql

Thank you. not been able to do anything for 3days

Excelent!! That fixed the problem for me. Thanks

⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐⭐

In my case, i needed to re-create log files, without the files i got the error InnoDB: File ./ib_logfile0 was not found

⚠️ Warning: this solution is destructive and deletes all your current data(bases).

On macOS Sonoma 14.6. The only thing that worked for me, was to completely wipe the current installation of mariadb.

1. cd /opt/homebrew/var
2. rm -rf mysql
3. brew uninstall mariadb --force
4. brew install mariadb
5. brew services restart mariadb
6. brew services ->
   

@musa11971 Thank you very much! It helped! Only mariadb started after the command:

mysql.server start

Had the same issue and reinstalling didn't solved it. (M3 Pro, MacOS 14.7)

I stumbled upon this and it helped in my case:

launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.mariadb.plist
launchctl load ~/Library/LaunchAgents/homebrew.mxcl.mariadb.plist

Deleting the data files (ib_logfile0 and 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:

The redo log was created with MariaDB 10.5.12. You must start up and shut down MariaDB 10.7 or earlier.

Installing the earlier version instead made it work again. I have not researched how to do the upgrade safely.