MySQL Bugs: #12137: start failure after upgrade

Bug #12137	start failure after upgrade
Submitted:	24 Jul 2005 6:45	Modified:	25 Jul 2005 7:21
Reporter:	Gilbert Wilson	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	4.1.13	OS:	MacOS (OS X 10.4.2)
Assigned to:		CPU Architecture:	Any

Description:
After upgrading from MySQL 4.1.11 to 4.1.13 I am unable to start MyQSL. System log shows that the startup command ran correctly, but the server will not start. I have uninstalled 4.1.13 and reinstalled 4.1.11 and now neither one will work all though 4.1.11 had been running on OS 10.4-OS 10.4.2 since converting from OS 10.3.9 some months ago. Starting MySQL manually I get the following---Starting mysqld daemon with databases from /usr/local/mysql/data
STOPPING server from pid file /usr/local/mysql/data/HAL9000.local.pid
050723 22:23:40  mysqld ended--- I have also tried using the startup item. I have received the following  message after attempting to connect.---/usr/local/mysql/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/tmp/mysql.sock' (61)'
Check that mysqld is running and that the socket: '/tmp/mysql.sock' exists!
 Checking the socket shows the symbolic link as follows---/tmp gil$ ls -la
total 32
drwxrwxrwt   8 root      wheel  272 Jul 23 21:15 .
drwxr-xr-x   6 root      wheel  204 Jul 23 18:27 ..
-rw-------   1 gil       wheel    0 Jul 23 18:31 ClassicScanComplete
srwxrwxrwx   1 mysql     wheel    0 Jul 23 18:54 mysql.sock
-rw-------   1 nobody    wheel   12 Jul 23 20:56 objc_sharing_ppc_4294967294
-rw-------   1 gil       wheel   72 Jul 23 21:15 objc_sharing_ppc_501
-rw-------   1 security  wheel   24 Jul 23 20:56 objc_sharing_ppc_92
-rw-------   1 gil       wheel   12 Jul 23 18:28 objc_sharing_ppc_99                                                    However I don't know where it points to. I am sure that this problem has something to do with changes made by Apple to the operating system and have asked for help on their support pages but perhaps you will be able to offer more help here Thanks in advance ---Gil

How to repeat:
I don't know if it can be repeated

I have been able to retrieve the following error from MySQL  after failure to start        050724 12:36:51  mysqld started
050724 12:36:51 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/mysql/data/ is case insensitive
050724 12:36:51  InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name ./ibdata1
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.
050724 12:36:51  mysqld ended

thanks   Gil

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.mysql.com/documentation/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

Additional info:

Have a closer look in the error log you posted:

050724 12:36:51  InnoDB: Operating system error number 13 in a file
operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name ./ibdata1
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.

Check the permissions of the InnoDB data directory.