478698 - checksetup.pl fails to connect to MySql 5.1

Status: RESOLVED DUPLICATE of bug 480001

(Bugzilla :: Installation & Upgrading, defect)

Description

[Jim Heedles]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Build Identifier: This is Bugzilla 3.2.2 on perl 5.8.9

After upgrading from MySql 5.0.67 to 5.1.31 all attempts to connect to the database resulted in "SESSION variable 'max_allowed_packet' is read-only. Use SET GLOBAL to assign the value".  The error occurred on line 113 of Bugzilla/DB/Mysql.pm.  The same result occurred in checksetup.pl after deleting the existing datbase and trying to create a blank one.

Setting the variable in MySql to the value Bugzilla wanted to use did not make a difference.

Reproducible: Always

Steps to Reproduce:
1. Upgrade to MySql 5.1.31
2. Run checksetup.pl
3.
Actual Results:  
...
Checking for           DBD-mysql (v4.00)   ok: found v4.005
There was an error connecting to MySQL:

    SESSION variable 'max_allowed_packet' is read-only. Use SET GLOBAL to assign the value

This might have several reasons:
...

Comment 1

[Max Kanat-Alexander]

Oh. Did you create the bugs user with the normal permissions specified in the "Configuration" section of the Bugzilla guide?

Is the server started with the --read-only switch (or otherwise made read-only)?

Comment 2

[Frédéric Buclin]

FYI, I have no problem using MySQL 5.1.30 on Windows, with the default config -> decreasing severity.

Comment 3

[Jim Heedles]

The bugzilla user was created with the normal permissions under mysql 5.0.xx and Bugzilla 3.0.5.  Adding all privs didn't change it.  Commenting out line 113 of
Bugzilla/DB/Mysql.pm lets Bugzilla work and I can create a bug.

The server is not started with read only.  

I still have the 5.0 tables and and switch back and forth between mysql 5.0.67 and 5.1.31.  Works fine under 5.0.67 with line 113 uncommented.