MySQL Bugs: #96966: I can't start mysql from the preferences pane on mac osx

Bug #96966	I can't start mysql from the preferences pane on mac osx
Submitted:	23 Sep 2019 3:35	Modified:	25 Nov 2019 14:12
Reporter:	Daniel Bruce	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S3 (Non-critical)
Version:	8.0.17	OS:	MacOS (10.14.6)
Assigned to:		CPU Architecture:	x86
Tags:	datadir, MySQL, mysql preferences pane

Description:
I can't start mysql server from the preferences pane in mac OSX when I change the data directory folder to the one I was using before. Starting mysql from the preferences pane with the datadir pointed at the one installed with the program works just fine. One day when I was running a Python program that was connecting to mysql using pymysql, I suddenly got connection issues. I tried installing a newer version of mysql to see if that would solve the problem, but when I set the datadir to the location I had my old database at then I was unable to start mysql again from the preferences pane.

I wrote more about it here including the question, answer and comment on the answer I gave:
https://superuser.com/questions/1461116/why-cant-i-start-mysql-from-the-preferences-pane-o...

How to repeat:
This is going to be hard since you would need my data folder which seems to be corrupted.

Suggested fix:
Please read the log file that I seem unable to make sense of and let me know what might be. Some key lines that lead me to this bug report are shown below:

InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace.

Hello Mr. Bruce,

Thank you for your bug report.

However, your problems are not with wrong datadir. I have studied carefully your log and the conclusion is rather easy and with several possibilities.

You could have problems with your RAM modules or with your disk. Hence, checking them with Apple service would be recommended. This seems least likely problem, since I am using iMac for the last 15 (fifteen) years.

However, there are other possible clauses. One of them is that you have manually copied (at least) some of your tables from one location to the other.

In any case, I would expect that your problems will go away if you restore your table from the backup.

Last, but not least, another possibility you have is that you gave erased any of the log tablespaces.

In any case, this is not our bug.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".