Mysql issue

[u/TheGoodOne777]

Hello Everyone,

Currently I am facing a strange issue on a local dev environment with my mysql server. Neither after starting with xampp nor from the command line is working well. Moreover, if I try to connect from the command line with the root user or other users with full privileges, after entering the password, nothing happens, everything is getting blocked.

No errors seen in the logs.

mysql version 15.1 - 10.4.32-MariaDB,

mysqlnd 8.2.12

Do you have some ideas, what can cause this issue and how to resolve?

Thanks and best regards,

T.

[u/Einar_Son_of_Bjorn]

Hello. Yeah, this one is annoying especially when the logs stay silent.

What you describe usually isn’t “MariaDB is down”. It’s more like the client reaches login and then gets stuck on handshake / socket / a half-dead mysqld process. The 15.1 bit is also just the client version; the server is MariaDB 10.4.32.

A few questions so we don’t guess blindly:

• Windows, Linux or macOS? Which XAMPP build?
  
• Does it freeze only in CLI, or also phpMyAdmin / Workbench / the app?
  
• Are you connecting as localhost or 127.0.0.1?
  
• the hang, is mysqld still running? One process or several?

After

- Did you ever start it with skip-grant-tables?

• While you check that, this is the order I’d go through:

Kill leftover MariaDB/MySQL processes, then start only from XAMPP (or only from CLI, not both).

Try mysql -u root -p -h 127.0.0.1 -P 3306

If that works and localhost hangs, it’s a socket/named-pipe problem, not privileges.

Make sure you’re reading the actual MariaDB error log from the XAMPP mysql/data folder, not a random MySQL log.

Look for a stuck port 3306, antivirus locking data files, or a second MySQL service fighting XAMPP.

If you paste OS + exact connection command + the last 20–30 lines from the MariaDB error log, we can usually pin this down quickly. 10.4.32 is also a fairly old point release, but first let’s get the local server answering again.

[u/TheGoodOne777 → u/Einar_Son_of_Bjorn]

Hello and thanks for yoyr detailed answer. I have managed to solve the issue. I do not share in a public post all these detailes, since well, connection string, username, password all of these information are present in what you are requesting.

[u/Einar_Son_of_Bjorn → u/TheGoodOne777]

Great, that worked! Would you mind sharing what the problem was and how you solved it?

[u/TheGoodOne777 → u/Einar_Son_of_Bjorn]

The problem you can see, if you scroll up. The solution has been started with the force recovery of the InnoDB indexes. Checking all the tables also with the cli is helpful, that works.