MySQL Bugs: #19211: Query Browser Does not Show Tables from MySQL DB on a FC5 install

Bug #19211	Query Browser Does not Show Tables from MySQL DB on a FC5 install
Submitted:	20 Apr 2006 6:45	Modified:	15 Jun 2006 21:54
Reporter:	Ben Israel	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.20	OS:	Windows (XP Pro SP2)
Assigned to:		CPU Architecture:	Any

Description:
When connecting to MySQL 5.x DBs on FC5 x86_64 from the QB on my XP SP2 box does not show tables on DBs. The QB basically freezes when trying to expand tree to show tables on a DB.  I can enter and run queries against the DBs. The same QB works fine with a MySQL 4.x install on OSX.  

The FC5 MySQL seems to behaving fine; PHP based web pages run correctly, MySQL client over SSH works flawlessly etc.  It's just the QB on XP against MySQL 5 on FC5 that seems to be strange.

How to repeat:
Connect to a MySQL DB on a FC5 x86_64 machine from a QB on an XP SP2 machine.  Expand DB to show tables on DB.

Thank you for a problem report. Please, send the SHOW TABLES results from that DB and SHOW PROCESSLIST results from a separate session while you are trying to expand that database from QB.

SHOW TABLES result for a DB on host:

+--------------------+
| Tables_in_tmhphoto |
+--------------------+
| tmh_pp_admingroups |
| tmh_pp_admlog      |
| tmh_pp_cache       |
| tmh_pp_categories  |
| tmh_pp_comments    |
| tmh_pp_ecards      |
| tmh_pp_exif        |
| tmh_pp_extrafields |
| tmh_pp_favorites   |
| tmh_pp_ipcache     |
| tmh_pp_iponline    |
| tmh_pp_laston      |
| tmh_pp_notify      |
| tmh_pp_photoextras |
| tmh_pp_photos      |
| tmh_pp_photoviews  |
| tmh_pp_settings    |
| tmh_pp_sort        |
| tmh_pp_sortmemb    |
| tmh_pp_usergroups  |
| tmh_pp_users       |
+--------------------+

SHOW PROCESSLIST result while attempting expand tree from QB:
mysql> show processlist;
+------+------+-----------------------------------------------+----------+---------+------+-------+------------------+
| Id   | User | Host                                          | db       | Command | Time | State | Info             |
+------+------+-----------------------------------------------+----------+---------+------+-------+------------------+
| 1395 | root | adsl-75-4-0-50.dsl.irvnca.sbcglobal.net:62691 | tmhvid   | Sleep   | 7252 |       | NULL             |
| 1760 | root | adsl-75-4-0-50.dsl.irvnca.sbcglobal.net:60039 | tmhvid   | Sleep   | 3612 |       | NULL             |
| 2036 | root | localhost                                     | NULL     | Query   |    0 | NULL  | show processlist |
| 2037 | root | 192.168.0.102:1371                            | tmhphoto | Sleep   |   45 |       | NULL             |
+------+------+-----------------------------------------------+----------+---------+------+-------+------------------+
4 rows in set (0.00 sec)

Interestingly, if I kill PID 2037 (which is what seems to be hung in this case) the list will then expand in the QB.  However, if I try to  to expand the tree of another DB, same problem.  Then if I kill the associated PID, the tree expands, but I can execute 'use db_name' to switch to that DB. Mmmm.  Any ideas?

It seems the QB and the server are not talking nice to each other.  MySQL version is: 5.0.18 on x86_64 (AMD) kernel 2.6.16-1.2080_FC5

Is there anybody out there?

Hi!

I was unable to reproduce this bug with MySQL running in FC5 X64, and with QB under XP/SP2 and XP64.

Hi Ben. I also "Can't repeat":
  MySQL server 5.0.23 BK on FC5 AMDx64 
  QB 1.1.20 on XP Pro SP2

[root@FC5X64 mysql]# gcc --version
gcc (GCC) 4.1.0 20060304 (Red Hat 4.1.0-3)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[root@FC5X64 mysql]# uname -s -r -p
Linux 2.6.16-1.2111_FC5 x86_64

C:\Documents and Settings\Tonci>ver
Microsoft Windows XP [Version 5.1.2600]

Thread 2037 seems ok to me besides it's the only connection from LAN. Killing it you disconnected QB from MySQL server. Can you connect with mysql command line client from your XP machine? If so, reopen the report and we'll check some more.

Sorry I didn't reply.  For other reasons I rebuilt the server, including a fresh install of MySQL.  I have no idea why, but it began working after the rebuild.  Software versions were the same, hardware was the same, firewall rules were the same, etc.  In any event, it is happily working now.