Hi, could it be this bug : http://bugs.mysql.com/bug.php?id=21011
2006/8/31, Whisler, David <[EMAIL PROTECTED]>:
I've upgraded from 5.0.22 to 5.0.24 MySQL Server on Solaris 9 using the Solaris package utility (which means I de-installed 5.0.22 then installed 5.0.24 in the same location, environment, configuration). I'm having the following error when trying to execute the mysql_upgrade executable according to the directions. This may not be necessary given it's a minor upgrade, but still - it should work, right? Here's the error. ---------------------------------- $ mysql_upgrade -u=root -p --basedir=/u01/app/mysql --datadir=/u07/mysql/data -v Enter password: Running /u01/app/mysql/bin/mysqlcheck --defaults-extra-file=/u07/mysql/data/upgrade_defaults --check-upgrade --all-databases --auto-repair --user==root error: Found option without preceding group in config file: /u07/mysql/data/upgrade_defaults at line: 2 Fatal error in defaults handling. Program aborted Error executing '/u01/app/mysql/bin/mysqlcheck --defaults-extra-file=/u07/mysql/data/upgrade_defaults --check-upgrade --all-databases --auto-repair --user==root' ---------------------------------- What's the deal with the "upgrade_defaults" file that it's complaining about? This file doesn't exist anywhere on my server (does it create it automatically), and according to the instructions it should be using the options I setup on the command line (and if not, it should at least be using the "my.cnf" file that I've setup in the MYSQL base directory. Here's my mysql.cnf (Note, I added the [mysql_upgrade] group options to see if that made a difference - and it didn't). $ more my.cnf -------------------------------- [mysqld] basedir=/u01/app/mysql datadir=/u07/mysql/data #log #log-bin log-slow-queries [mysql_upgrade] basedir=/u01/app/mysql datadir=/u07/mysql/data ------------------------------- This is on my test box (I'm no dummy - or at least I like to think that), so no harm no foul. However, I'd like to upgrade my Production box, but am waiting for this to be resolved first. MySQL 5.0.24 seems to run fine without running this script, but then again - I like to play it safe. Any ideas? David Whisler
-- http://www.myspace.com/sakuradrop : forget the rest http://www.w-fenec.org/ Webzine rock/metal -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
