Bug #63328 Performance_Schema fails to load
Submitted: 19 Nov 2011 15:57 Modified: 19 Nov 2011 16:26
Reporter: Peter Laursen (Basic Quality Contributor) Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Performance Schema Severity:S2 (Serious)
Version:5.5.18 OS:Windows (7/64 bit)
Assigned to: CPU Architecture:Any

[19 Nov 2011 15:57] Peter Laursen
Description:
P_S does not load and this docs page does not help:

http://dev.mysql.com/doc/refman/5.5/en/performance-schema-quick-start.html

"For example, use these lines in your my.cnf file: 
[mysqld]
performance_schema

 When the server starts, it sees performance_schema and attempts to initialize the Performance Schema. To verify successful initialization, use this statement: 
mysql> SHOW VARIABLES LIKE 'performance_schema';
+--------------------+-------+
| Variable_name      | Value |
+--------------------+-------+
| performance_schema | ON    |
+--------------------+-------+

 A value of ON means that the Performance Schema initialized successfully and is ready for use. A value of OFF means that some error occurred. Check the server error log for information about what went wrong."

I certainly had P_S running with an beta 5.5 a year back or so. 

I am not sure if 5.5.18 is officially released.  But it is available here (from where I took it): ftp://ftp.easynet.be/mysql/Downloads/MySQL-5.5/mysql-5.5.18-winx64.zip 

(using the .zip because of this annoying bug: http://bugs.mysql.com/bug.php?id=56889.)

How to repeat:
But I get: 

my.ini:
********
...
[mysqld]
port=3307
lower_case_table_names = 2
performance_schema
basedir=
.. etc-

error log:
***********
111119 16:42:43 [Note] Plugin 'FEDERATED' is disabled.
111119 16:42:43 InnoDB: The InnoDB memory heap is disabled
111119 16:42:43 InnoDB: Mutexes and rw_locks use Windows interlocked functions
111119 16:42:43 InnoDB: Compressed tables use zlib 1.2.3
111119 16:42:43 InnoDB: Initializing buffer pool, size = 106.0M
111119 16:42:43 InnoDB: Completed initialization of buffer pool
111119 16:42:43 InnoDB: highest supported file format is Barracuda.
111119 16:42:44  InnoDB: Waiting for the background threads to start
111119 16:42:45 InnoDB: 1.1.8 started; log sequence number 2962618
111119 16:42:45 [Note] Event Scheduler: Loaded 0 events
111119 16:42:45 [Note] C:\Program Files (x86)\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.16'  socket: ''  port: 3307  MySQL Community Server (GPL)

Verification from client: 
*************************

SHOW VARIABLES LIKE 'performance_schema';
/* returns

Variable_name       Value 
------------------  ------
performance_schema  OFF   
*/

Suggested fix:
no idea.
[19 Nov 2011 16:00] Valeriy Kravchuk
You say 5.5.18 while your log contains 5.5.16. Are you sure you tried to connect to the same MySQL server that you changed configuration file for?
[19 Nov 2011 16:07] Peter Laursen
Yes I am sure taht I do not mismatch server. I have only one 5.5.x server!

About the version mismatch please see this other report I just filed:
http://bugs.mysql.com/bug.php?id=63329

1) 
The file name is "mysql-5.5.18-winx64".  'mysql_upgrade' identifies it as 5.5.18.

2)
But error log and SELECT VERSION() identifies it as 5.5.16

.. but whether it is .16 or .18 is may be irrlevant for this discussion!
[19 Nov 2011 16:11] Peter Laursen
I double checked the file position it is 
C:\Program Files\MySQL\MySQL Server 5.5\my.ini

I attach the ini.  it is trivial (created by the (old) installer)

Alos I checked that I have no my.ini or my.cnf in C:\ or C:\windows
[19 Nov 2011 16:11] Peter Laursen
my.ini

Attachment: my.ini (application/octet-stream, text), 8.71 KiB.

[19 Nov 2011 16:20] Peter Laursen
Plase forget!

SHOW VARIABLES LIKE 'basedir';
/*

Variable_name  Value                                         
-------------  ----------------------------------------------
basedir        C:/Program Files (x86)/MySQL/MySQL Server 5.5/
*/

So the problem is this (also very stupid and annying) bug 
http://bugs.mysql.com/bug.php?id=60830
[19 Nov 2011 16:26] Peter Laursen
after editing the registry (correcting the damage that the 32 bit installer did to my 64 bit installation) I get 

SHOW VARIABLES LIKE 'basedir';
/*

Variable_name  Value                                         
-------------  ----------------------------------------------
basedir        C:/Program Files (x86)/MySQL/MySQL Server 5.5/
*/

SHOW VARIABLES LIKE 'performance_schema'
/*
Variable_name       Value 
------------------  ------
performance_schema  ON    
*/

what is much better!