Opened 18 years ago
Last modified 10 years ago
#10566 new defect
mysql5 mysql_upgrade doesn't work after upgrading to 5.0.24 — at Version 3
Reported by: | opendarwin-2006@… | Owned by: | jberry@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.3.2 |
Keywords: | Cc: | jberry@…, markd@… | |
Port: | mysql5, mysql5-devel |
Description (last modified by jberry@…)
I understand you're supposed to run mysql_upgrade after you upgrade to a new version of MySQL. But after upgrading to MySQL 5.0.24, mysql_upgrade doesn't seem to work anymore.
(I have /opt/local/bin, /opt/local/sbin and /opt/local/lib/mysql5/bin in my PATH.)
$ mysql_upgrade5 Can't find program '/opt/local/bin/mysqlcheck' Please restart with --basedir=mysql-install-directory $ mysql_upgrade Can't find program '/opt/local/bin/mysqlcheck' Please restart with --basedir=mysql-install-directory $ mysql_upgrade --basedir=/opt/local/lib/mysql5/ Can't find data directory. Please restart with --datadir=path-to-data-dir $ mysql_upgrade --basedir=/opt/local/lib/mysql5/ --datadir=/Users/rschmidt/mysql/data/ [snipped usage message for mysqlcheck] Could not find file mysql_fix_privilege_tables.sql Please use --basedir to specify the directory where MySQL is installed $
I don't know what to specify now. And it seems to me like I shouldn't have to specify anything -- that it should already know where its parts are. In 5.0.22 the script worked fine without specifying anything extra, but I read in the release notes that between 5.0.22 and 5.0.24 they rewrote mysql_upgrade and changed it from a shell script to a C program. I'm guessing that has something to do with this problem.
Change History (3)
comment:1 Changed 18 years ago by markd@…
Cc: | jberry@… markd@… added |
---|
comment:3 Changed 18 years ago by jberry@…
Description: | modified (diff) |
---|---|
Status: | new → assigned |
Probably the upgrade scrip gets confused, because of the way in which we rename the mysql binaries with a 5 at the end. The script probably needs to get upgraded with these.
Did 5.2.4a fix this?