Bug #44804 mysql repeats "no query specified" message continuous
Submitted: 11 May 2009 20:53 Modified: 12 May 2009 21:23
Reporter: norbert van Nobelen Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Packaging Severity:S3 (Non-critical)
Version:6.0.10-alpha RPM OS:Linux (OpenSuse 10.3)
Assigned to: CPU Architecture:Any
Tags: no, query, repeat, specified

[11 May 2009 20:53] norbert van Nobelen
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 9
Server version: 6.0.10-alpha MySQL Community Server (Copyright 2000-2008 MySQL AB, 2008 Sun Microsystems, Inc.  All rights reserved.  Use is su

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> show tables;

No query specified

No query specified

No query specified

No query specified

No query specified

No query specified

How to repeat:
Installed RPM 6.0.10-alpha:

Login into mysql
After every ; the message repeats
[12 May 2009 7:10] Sveta Smirnova
Thank you for the report.

Verified as described.
[12 May 2009 7:14] Sveta Smirnova
Bug is only repeatable with RPM packages.

Workaround: use tar.gz package.
[12 May 2009 18:54] Daniel Fischer
I extracted the RPM like this:

rpm2cpio MySQL-client-6.0.10-0.glibc23.x86_64.rpm | cpio -idmv

Then I ran:

usr/bin/mysql -h ... -u ...

Welcome to the MySQL monitor.  Commands end with ; or \g.
mysql> show tables;
Empty set (0.00 sec)


In other words, the binary in the packages itself works fine on RHEL 5 and SLES 11. I don't currently have access to OpenSuSE 10.3.

On which platform(s) was this bug verified?
[12 May 2009 19:02] norbert van Nobelen
Ok, I will install the tar instead.
Close the bug?
[12 May 2009 19:09] Daniel Fischer
No, please don't close it. I would very much prefer to find the problem first. It may not be a client issue.
[12 May 2009 21:22] Daniel Fischer
Okay, I found it. This bug is actually fixed in the MySQL 6.0.11 code base.

As a temporary workaround, you might consider using the tarball exclusively, or even just replacing the mysqld binary from the RPM-based installation with one from a tarball. The problem is caused by the overlong version comment of the server included in the RPM packages. In future MySQL 6.0 releases, the client will be able to handle these longer comments.
[1 Jun 2009 20:29] Don MacAskill
This bug also affects 5.4. :(