MySQL Bugs: #2058: Fresh install of 4.1.1 on Mac OS X Panther does not work

Bug #2058	Fresh install of 4.1.1 on Mac OS X Panther does not work
Submitted:	9 Dec 2003 9:01	Modified:	29 Mar 2004 23:02
Reporter:	Jim Winstead	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S1 (Critical)
Version:	4.1.1	OS:	MacOS (Mac OS X 10.3.1)
Assigned to:	Michael Widenius	CPU Architecture:	Any

Description:
After installing 4.1.1 on Panther, and manually running the mysql_install_db script, it is impossible 
to issue any queries using the mysql command-line client.

How to repeat:
Install 4.1.1 on Mac OS X Panther (using the package installer at least -- I did not test with the 
tar.gz package). Run 'scripts/mysql_install_db' manually to install the mysql database. Run 'chown 
-R mysql /usr/local/mysql/data' to fix the incorrect ownership (assuming mysql_install_db was run 
as root).

Connect with the 'mysql' client, and issue any query. Some examples after connecting as root and 
selecting the "mysql" database:

mysql> show variables;
ERROR: 
No query specified

mysql> select * from host;
ERROR 1096 (HY000): No tables used
mysql> 

Reportedly connecting with a 4.0 client works, and connecting using the bundled version of PHP 
(4.3.2, linked with the MySQL 3.23.59 client library) does work.

This should be tested on Jaguar (OS X 10.2) to determine if it is Panther (10.3) specific. MySQL's OS 
X build machine is Jaguar, and apparently this 4.1.1 build passed the test suite.

Following up on Matt's comment:

I just installed 4.1.1 from the PKG on my Mac OS X Jaguar iBook (10.2.8).
I see the same symptoms Jim describes for Panther.  I do find that
"SELECT 1" works, as does \s, and USE test, but queries such as
SHOW TABLES or CREATE TABLE fail.  Using a 4.0.16, 4.1.1, or 4.1.2
client that I built myself from source, I don't see any of these problems.

Additionally, I ran mysql_install_db *with* a --user=user_name
option, and the option apparently was ignored. mysql_install_db
created all files with root ownership. (The --user option was used
correctly by mysqld_safe, however.)

One more note:

mysqladmin variables and mysqladmin extended-status
work correctly, even though SHOW VARIABLES and SHOW
STATUS issued from the mysql client do not.

Bug #2230 has been marked as a duplicate of this one.

The same bug happens on Mac OS X 10.3.2.

It also happens with the tar.gz package (on Mac OS X 10.2.3)

Martin

Sorry -- should read 10.3.2

Martin

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Was fixed some time ago (by me). Fix will be in 4.1.2

I experienced the same bug. All afternoon. And after reading this bug report, I can go have a beer. 
Using the client from mysql 5.x also seems to work fine. Unfortunately, the Java mysql driver also 
seems to be failing to work with version 4.1.1, but I need to test this more . . .