Comments on: MySQL 5.1.32 is now available

By: Guillaume Plessis

Guillaume Plessis — Thu, 09 Jul 2009 09:13:17 +0000

That’s an old Debian (therefore Dotdeb) compatibility setting. It will disapear in the next mysql-common package (upcoming 5.1.36?).

By: Chris Trahey

Chris Trahey — Thu, 09 Jul 2009 00:27:29 +0000

Thanks, Guillaume.
Sure thing, it’s in the .cnf file.
Is that default from the MySQL Distro, or a dotdeb thing?

By: Guillaume Plessis

Guillaume Plessis — Mon, 06 Jul 2009 09:02:28 +0000

@Chris Trahey : Please check that the “old-passwords” option is unset or set to 0 in your my.cnf (/etc/mysql/my.cnf, ~/.my.cnf)

By: Chris Trahey

Chris Trahey — Sun, 05 Jul 2009 02:19:09 +0000

I am having problems with the password() function… it is possible this is by design, but I couldn’t find documentation.
It is returning the same value as old_password() (16 byte). It is as if password() is aliased in this (dotdeb) release.

I have another machine running 5.1.33 community, and the issue is not present.

Is this something in the config I can change?
Thanks!

By: Michael Stubblefield

Michael Stubblefield — Wed, 08 Apr 2009 18:06:00 +0000

For everyone having problems with the upgrade:

If you keep your my.cnf file, you will get errors, causing an incomplete installation and possibly issues downgrading to mysql 5.0

To avoid this, backup your my.cnf file and overwrite it, then just go through and redo any changes you had made before.

If you have this problem and now your db is hosed and can’t revert to 5.0, and can’t install 5.1:

go into your my.cnf file. comment out the line (mentioned above):

skip-bdb

do this and retry install. Should work now.

By: Sébastien Ballesté-Antich

Sébastien Ballesté-Antich — Tue, 07 Apr 2009 10:04:16 +0000

I re-run /usr/bin/mysql_upgrade –force script and got these errors :
mysql.general_log
Error : You can’t use locks with log tables.
status : OK
mysql.slow_log
Error : You can’t use locks with log tables.
status : OK

I’m going to have a look for the second solution.

By: Guillaume Plessis

Guillaume Plessis — Tue, 07 Apr 2009 09:59:04 +0000

@Sébastien : Try to execute /usr/bin/mysql_upgrade or try to upgrade to the fresh 5.1.33.

By: Sébastien Ballesté-Antich

Sébastien Ballesté-Antich — Tue, 07 Apr 2009 09:49:58 +0000

@Guilllaume,
Thanks, I did on both master and slave:

STOP SLAVE;
SET SQL_LOG_BIN=0;
SET GLOBAL general_log = ‘OFF’;
USE mysql;
ALTER TABLE general_log MODIFY COLUMN server_id INTEGER UNSIGNED NOT NULL;
SET GLOBAL general_log = ‘ON’;
SET SQL_LOG_BIN=1;
START SLAVE;

But got always the same error.
Is it a good idead to re-run the upgrade script ? Where is it located ?

By: Guillaume Plessis

Guillaume Plessis — Tue, 07 Apr 2009 09:23:07 +0000

@Sébastien : No idea, it seems strange. Try to “play” general_log, SLAVE STOP, SHOW SLAVE STATUS, SLAVE START…

http://bugs.mysql.com/bug.php?id=39133

By: Sébastien Ballesté-Antich

Sébastien Ballesté-Antich — Tue, 07 Apr 2009 09:10:04 +0000

After the upgrade to this version, I got this replication’s error :

> SHOW SLAVE STATUS;

Error ‘You cannot ‘ALTER’ a log table if logging is enabled’ on query. Default database: ‘mysql’. Query: ‘ALTER TABLE general_log MODIFY COLUMN server_id INTEGER UNSIGNED NOT NULL’

Any idea to fix ?