Bug #9458 Old privilege tables causes server to crash

• Submitted: 29 Mar 2005 16:09
• Modified: 27 Apr 2005 17:40
• Reporter: Max Mether
• Status: Can't repeat
• Category: MySQL Server
• Severity: S2 (Serious)
• Version: 5.0.3-max-beta
• OS: Linux (SuSE)
• Assigned to: Jim Winstead
• CPU Architecture: Any

[29 Mar 2005 16:09] Max Mether

Description:
When starting the 5.0.3 server using 4.1 privilege tables the server crashes during the startup (signal 11). 

The 5.0.2 server has no problems with the old privilege tables. 

How to repeat:
Start a 5.0.3 server using a 4.1 data directory

Suggested fix:
The 5.0.2 server works with the 4.1 privilege tables... 

I started the 5.0.2 server, ran mysql_fix_privileges, stopped the 5.0.2 server and then restarted 5.0.3. This worked without problems.

[27 Apr 2005 17:39] Jim Winstead

I was unable to repeat this using these steps:

1. Unpack mysql-standard-4.1.11-pc-linux-gnu-i686.tar.gz
2. (cd mysql-standard-4.1.11-pc-linux-gnu-i686/mysql-test; ./install_test_db --bin)
3. Unpack mysql-standard-5.0.4-beta-pc-linux-gnu-i686.tar.gz
4. (cd mysql-standard-5.0.4-beta-pc-linux-gnu-i686; ./bin/mysqld --no-defaults --basedir=. --datadir=../mysql-standard-4.1.11-pc-linux-gnu-i686/mysql-test/var/master-data --skip-innodb --skip-ndbcluster --skip-bdb &)

Connecting to the server started in the last step showed it was using the 4.1 mysql database.

(This should be double-checked with 5.0.4 regardless, since I believe there were some fixes in this area between 5.0.3 and 5.0.4.)

[27 Apr 2005 17:40] Jim Winstead

I forgot to add that I also tried to repeat this with 5.0.3, and could not.

[3 May 2005 16:21] Max Mether

Added .sql file with the non-working mysql db. 

This db works in 4.1.10 and 5.0.2. It does not work in 5.0.3. 

Havent tested with 4.1.11 or 5.0.4

[18 May 2005 13:11] Max Mether

Now tested it on 5.0.4-max and it worked, so the bug seemed to be fixed