Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Incomplete
-
Affects Version/s: 5.5.30
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Server: CentOS 5.8 i386 + MariaDB 5.5.30
Client: windows x64 pro + MySQL WorkBench 5.2.47
Description
Freeze when retrive table list with mysql workbench.
following was my my.cnf configure.
[client] port = 3306 socket = /tmp/mysql.sock [mysqld] port = 3306 socket = /tmp/mysql.sock skip-external-locking log-bin=mysql-bin binlog_format=mixed server-id = 1 [mysqldump] quick max_allowed_packet = 16M [mysql] no-auto-rehash [myisamchk] key_buffer_size = 20M sort_buffer_size = 20M read_buffer = 2M write_buffer = 2M [mysqlhotcopy] interactive-timeout
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Hi,
Could you please attach the schema dump, and server error log, and also explain what exactly happens, it's not quite clear from the screenshot what's wrong there.
Besides, if the problem is persistent, please enable general log on the server and send its contents after reproducing the problem.
Thanks.
Sorry for long times delay.
I had done many research about this problem.
I found some body faced the same problem with me .
http://bugs.mysql.com/bug.php?id=55008
http://bugs.mysql.com/bug.php?id=55356
I tried their solution. then i got fixed.
Ok, let's talk how it occurs.
I previous using Mysql 5.5.30, some day, i compiled the MariaDB 5.5.30, import my old databases;
I should have to run mysql_upgrade, but i did not .
What i do got fixed is just simple:
type and run mysql_upgrade -h 127.0.0.1
then the mysql workbench working correct.
if you got upgrade from old to latest version MySQL or MariaDB,
you really should run mysql_upgrade, to check if your scheme got problems.
the mysql_upgrade tools will help you repair some problem.
i will keep watching it. see if it will appears next time.
sorry for the delay.
Hi,
Did you have any error messages in your error log file similar to those described in MySQL bug reports?
(While mysql_upgrade is always recommended, it's a bit strange that the problem happened while switching from MySQL 5.5.30 to MariaDB 5.5.30, as you described, so it would be useful for us to know which exact error you observed to be able to diagnose similar problems better in future.)
Please add a comment if you have new information on the issue.
MySQL 5.5.30 and Percona 5.5.30 working well.
MariaDB 5.5.30 got pained.