The default install script looks for /var/mysql/mysql.sock, which is not where OS X 10.4.11 and MySQL installer for 4.1.18 were installing the socket. To get it to work, I had to:
sudo mkdir /var/mysql
sudo ln -s /tmp/mysql.sock /var/mysql/mysql.sock

..in order to proceed. I'm also filing this as a code bug, I suggest both teams hit it (with a sledgehammer), so that install *and* install docs cover this.

Comments

Noyz’s picture

Component: Installation » Correction/Clarification

Changed the component to reflect the new component categorization. See http://drupal.org/node/301443

tgeller’s picture

ronabop, could you post a link to the page you're referring to? That'll be a big help. Thanks!

MGParisi’s picture

Assigned: Unassigned » MGParisi

I am going to set this to fixed. No info was provided by the original poster, its a year old issue, and its admittedly an issue with out of date software.

In addition the OP can now fix it himself. However I will even assign it to me if I can get the details on what page to fix.

MGParisi’s picture

Status: Active » Fixed

oops fixed

jhodgdon’s picture

Status: Fixed » Active

I did a search on mysql.sock to try and figure out which page(s) this might relate to. It looks like there are several pages that correctly address this issue, and some that don't.

Pages I think probably/possibly need editing to fix this issue:
- http://drupal.org/node/22674 (see comments that probably need to be incorporated)
- http://drupal.org/node/68133
- http://drupal.org/node/129202
- http://drupal.org/node/66187
- http://drupal.org/node/22676 (see comments that probably need to be incorporated)

I am not a MacOS user, nor do I have any knowledge about MySQL sockets, so maybe someone else can figure out how to edit those pages correctly. Meanwhile, I'm setting this issue back to Active, because it doesn't appear that it is fixed.

MGParisi’s picture

Assigned: MGParisi » Unassigned

I am taking myself of the assigned person on this ticket I am not a Mac user.

jhodgdon’s picture

Status: Active » Fixed

All of the above pages seem to now have the text fixed or a comment with this information in it. We aren't using Documentation issue reports to report problems with Community Documentation pages any more, so this is good enough and I'm marking this fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.