[email protected] Bottle Service - Unsafe Host Shutdown Corrupts InnoDB? #5389
-
Output of
|
Beta Was this translation helpful? Give feedback.
Replies: 15 comments 15 replies
-
I have had similar corruption on that version of MariaDB. After getting a backup of all the databases I emptied out my whole installation to try to get it working again. I found that stopping the service with "brew services stop [email protected]" claimed it had stopped but the process was still running and at 100% CPU. This meant that MariaDB couldn't then be restarted. I also tried version 10.6 which had the same issue. I have now installed the latest version of MariaDB (11.3.2). This does seem to stop the process correctly when stopping the service. So it's maybe an issue with the current 10.X versions? Output of brew config:
|
Beta Was this translation helpful? Give feedback.
-
It looks like this is an upstream bug (MDEV-34129 and MDEV-34254) and has a possible pending fix for the 10.11.x series in MariaDB/server#3253 |
Beta Was this translation helpful? Give feedback.
-
I have this problem as well. With 10.11, mariadbd fails to stop with the message "Signal handler thread did not exit in a timely manner. Continuing to wait for it to stop..". The only way to recover i've found is to completely remove mariadb, reinstall and re-import the databases. I have tried using I'm using macOS 14.5 on Apple silicon. |
Beta Was this translation helpful? Give feedback.
-
in case that's relevant, the issue does not happen with mysql 5.7 on the same system with the same database. |
Beta Was this translation helpful? Give feedback.
-
I updated my machine yesterday, and i think i have the same problem. I uninstalled mariabd and installed it again. I disabled the auto start. But it still crashes. This is really annoying. As i am not that good with mariadb, is there a solution for the moment? Can i go back to a previous version of mariadb? |
Beta Was this translation helpful? Give feedback.
-
I have now installed an older version. That is working for now. I will describe what i did. But please keep in mind, that i have this running here on my mac for testing purposes. I'm not responsible when something breaks! This will erase all of your database files. So this is only working, if you have a backup!
Brew says that the mecab files are still there, so i did a:
After that i removed other files too:
Then i restarted the mac.
To install mariadb i choosed an older version.
After the install brew mentions that this version is not in the path, because it is an older version. But brew tells me, that when i need this in my path (to work with it in the console) i can do a:
Important! I use zsh. If you use another terminal like bash, i hope brew will give you the right copy and paste command! Restart the terminal so that you can use the command mysql
here you have to type in your account password, that you use for your mac user! If you typed in your password correct, you will enter this mysql command thingy... Here i did:
Important! Replace newrootpassword with your own password. You can choose a new pasword for the mysql root user. Then write exit to leave the mysql console
After that i imported back my databases with phpmyadmin. And did a whole restart of the system. And it works for me again! I hope this helps for now. 🖖 |
Beta Was this translation helpful? Give feedback.
-
I am having the same problem with MariaDB latest 11.4.2 on macOS 14.5 on M1. |
Beta Was this translation helpful? Give feedback.
-
Having this issue as well... going to downgrade to an older version, similar to above... But @mazzelman just a FYI -- 10.10 is deprecated and not considered LTS. See MariaDB Server Releases for more info. I've gone ahead and downgraded to 10.6 (LTS). |
Beta Was this translation helpful? Give feedback.
-
@mikeho |
Beta Was this translation helpful? Give feedback.
-
I have the same problems in MariaDB 11.4.2 and 11.2.4. After starting MariaDB with:
I see the following processes:
Then, when I stop MariaDB with the following:
I get a conformation that MariaDB is stopped:
But if I check the running processes I still see these:
I can kill that process with kill -9. If I then restart MariaDB there is no InnoDB corruption. So this way I have a usable workaround. |
Beta Was this translation helpful? Give feedback.
-
I have the same problem on an M3 Apple with 11.4.2. |
Beta Was this translation helpful? Give feedback.
-
I upgraded to Sonoma (Apple M2) yesterday and that is where the problems started. FWIW, I have tried 11.4, 10.10 and 10.6 now and all seem to have the problem that I get a message about the showdown in the log:
but running
Even
And I think that is the root cause of the problem: the server process that is not stopping. Eventually, when the system is restarted, it will be force-stopped - which is bad for the data files. Or when trying to stop/restart the service (in particular with 11.4), it seems that the service script might not be checking properly if another deamon is already running which can then lead to a corrupted redo log. |
Beta Was this translation helpful? Give feedback.
-
I tried all LTS versions available in Homebrew, all are broken. My databases are big and always get corrupted on forced shutdown. Switched to Percona Server for now, but it is not available on ARM. Upd: I'm on Ventura. |
Beta Was this translation helpful? Give feedback.
-
Same here. I downgraded to 10.6. But process stays up when stopping as described above, kill -9 process pid works then. A soon fix would be very helpful. |
Beta Was this translation helpful? Give feedback.
It looks like this is an upstream bug (MDEV-34129 and MDEV-34254) and has a possible pending fix for the 10.11.x series in MariaDB/server#3253