MySQL Bugs: #63588: After installing version 5.5 cannot start mysql

Bug #63588	After installing version 5.5 cannot start mysql
Submitted:	4 Dec 2011 23:59	Modified:	19 Dec 2012 19:43
Reporter:	Jan Nemecek	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S2 (Serious)
Version:	5.5	OS:	MacOS
Assigned to:		CPU Architecture:	Any
Tags:	mysql.sock, socket, tmp

Description:
I had mysql version 5.1.50 on my MAC OS X. I try to upgrade to 5.5 (because the 5.1 version has some issues with foreign keys) so i just download and install version 5.5
After that now i cant run mysql. When i type command mysql -u root -p and then password i've got a message: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2).
How can i fix this? I try delete all files about mysql and install again clearly. Still doesn't work with the same error message. How can i completely uninstall mysql and install it again correctly? Or how can i fix that without reinstall?
And second question: how to upgrade mysql in the future, because i don't want to solving this kind of problems again.

Thank you

How to repeat:
Install mysql 5.1.50 on MAC OS X Snow Leopard (10.6.8).
Install mysql 5.5
Restart mysql service
Try to run mysql command line client.

What exact version, 5.5.x, you had installed? How exactly you tried to start MySQL server after upgrade?

The version is 5.5.18
After upgrade i try classic command line statement sudo /Library/StartupItems/MySQLCOM/MySQLCOM start - that works, but it's probably start the old version 5.1.50.
Then i try start service from System Preferences and that doesn't work.
Anyway, i fix the problem, deleted all files that is common with mysql and instaled clean mysql version 5.5.18.
But it's good to know how to find all mysql items to delete in simple way.

Have you followed the Manual instructions ?

https://dev.mysql.com/doc/refman/5.5/en/upgrading-from-previous-series.html

Thanks.

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".