Tiger killed mysql

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Tiger killed mysql

jc-15
OS X 10.4, Lasso 8.0.4.

When upgrading to Tiger on my development machine (PB) I somehow  
managed to kill mysql in the process.

I've tried reinstalling from a fresh download but I keep getting the  
same error:

ERROR 2002 (HY000): Can't connect to local MySQL server through  
socket '/tmp/mysql.sock' (2)

The user mysql still exists and the directory /tmp have these access  
rights: drwxrwxrwt. Actually /tmp is a symbolic link to /private/tmp  
but that shouldn't matter. And in tmp there of course is no mysql.sock.

The Tiger upgrade was done with the Archive option. Lasso works  
perfectly after being reinstalled.

For the moment I'm clueless.

HDB
JC

--
------------------------------
Lasso Support: http://support.omnipilot.com/
Search the list archives: http://www.listsearch.com/lassotalk.lasso
Manage your list subscription:  
http://www.listsearch.com/lassotalk.lasso?manage
Reply | Threaded
Open this post in threaded view
|

Re: Tiger killed mysql

Olivier Miossec

JC ?crit:

> OS X 10.4, Lasso 8.0.4.
>
> When upgrading to Tiger on my development machine (PB) I somehow  
> managed to kill mysql in the process.
>
> I've tried reinstalling from a fresh download but I keep getting the  
> same error:
>
> ERROR 2002 (HY000): Can't connect to local MySQL server through  
> socket '/tmp/mysql.sock' (2)
>
> The user mysql still exists and the directory /tmp have these access  
> rights: drwxrwxrwt. Actually /tmp is a symbolic link to /private/tmp  
> but that shouldn't matter. And in tmp there of course is no mysql.sock.
>
> The Tiger upgrade was done with the Archive option. Lasso works  
> perfectly after being reinstalled.
>
> For the moment I'm clueless.
>
> HDB
> JC


You can modify privilege in /private/tmp

You can also use your own directory

Or only use TCP/IP (you will need to comment socket line in my.cnf)

It's seem to me that it's just an authorisation probleme


---
Olivier Miossec
AIM/ichat omiossec
--
http://www.lasso-developpeur.net
--

--
------------------------------
Lasso Support: http://support.omnipilot.com/
Search the list archives: http://www.listsearch.com/lassotalk.lasso
Manage your list subscription:  
http://www.listsearch.com/lassotalk.lasso?manage
Reply | Threaded
Open this post in threaded view
|

Re: Tiger killed mysql

Fletcher Sandbeck
In reply to this post by jc-15
On 5/23/05 at 4:22 PM by [hidden email] (JC):

>OS X 10.4, Lasso 8.0.4.
>
>When upgrading to Tiger on my development machine (PB) I somehow  
>managed to kill mysql in the process.
>
>I've tried reinstalling from a fresh download but I keep getting the  
>same error:
>
>ERROR 2002 (HY000): Can't connect to local MySQL server through  
>socket '/tmp/mysql.sock' (2)
>
>The user mysql still exists and the directory /tmp have these access  
>rights: drwxrwxrwt. Actually /tmp is a symbolic link to /private/tmp  
>but that shouldn't matter. And in tmp there of course is no mysql.sock.
>
>The Tiger upgrade was done with the Archive option. Lasso works  
>perfectly after being reinstalled.
>
>For the moment I'm clueless.

MySQL is located in /usr/local/ by default, usually with a configuration file at /etc/my.conf.  When you perform an "Archive and Install" both of these locations will be archived into the Previous Systems folder.  Re-installing MySQL would restore the default state of MySQL, but would not restore any of your solution databases or custom configuration.

If you stop MySQL and then merge over your databases and your configuration file from the respective locations in the Previous Systems folder, then everything will probably be back the way it was before you upgraded.

Also, don't delete the Previous Systems folder until you are absolutely sure you have gotten everything you need out of it.  Your Apache Web server root, fonts, and all sorts of settings and preference files that you may need may be found in there.

I'm not sure why the conventional wisdom dictates an Archive and Install when upgrading to a new version of Mac OS X.  It seems guaranteed to cause issues like this since a lot of software installs components into portions of the OS that are archived and reset.  I always try to do an install in place and then fall back on an Archive and Install only if I start to see issues with the computer.

[fletcher]
--
Fletcher Sandbeck                         [hidden email]
Lasso Product Specialist              [hidden email]
OmniPilot, Software Inc.                http://www.omnipilot.com

--
------------------------------
Lasso Support: http://support.omnipilot.com/
Search the list archives: http://www.listsearch.com/lassotalk.lasso
Manage your list subscription:  
http://www.listsearch.com/lassotalk.lasso?manage