MySQL Bugs: #12557: mysql 4.1.13 not identifying hosts properly

Bug #12557	mysql 4.1.13 not identifying hosts properly
Submitted:	12 Aug 2005 19:02	Modified:	1 Nov 2005 6:25
Reporter:	Patrick Lum	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4.1.13, 4.1.14	OS:	Linux (Red Hat Enterprise 3)
Assigned to:		CPU Architecture:	Any

Description:
MySQL does not identify the Host/IP properly in the "mysqladmin processlist" command. I am using mytop to monitor the processes.

This bug is not in 4.1.12.

How to repeat:
Write a script to do  a lot of small queries to bring up the queries/s and monitor using mytop. Execute the script to query the database remotely and observe the Host/IP. MySQL only shows the Host/IP of the first Host that did a query after MySQL was reseted. That Host is not changed if the queries are from another server.

Suggested fix:
None

Hi!

I was unable to reproduce this bug.  Can you please upload a perl script that reproduces this erratic behaviour ?

Thanks !

If you run mytop on your server, do you see the queries coming from different hosts?

Patrick..

I have changed synopsis to a more complete one.

Have you tried to repeat this behaviour on 4.1.14? On other servers (operating systems)? 

If you try to connect from these machines using, say, ssh or telnet, are their hostnames identified properly (with, for example, netstat command)?

Please, simply paste the command you performed and the results you observed into the bug report or attach them as a file.

test smack file

Attachment: test.smack (application/octet-stream, text), 1.33 KiB.

If you run mytop, do you notice that there are no active queries show from other hosts other than the local host? 

I am using super-smack to do performance testing. 

Here is my setup:
lab-game05 - mysql server with mytop
lab-db04 - remote machine with super-smack

Both machines are running Red Hat Enterprise 3 with msyql 4.1.14.

- create a test database on (lab-game05) called test with a table called mytable:
mysql> desc mytable;
+-------+-------------+------+-----+---------+-------+
| Field | Type        | Null | Key | Default | Extra |
+-------+-------------+------+-----+---------+-------+
| ID    | varchar(20) | YES  |     | NULL    |       |
+-------+-------------+------+-----+---------+-------+
1 row in set (0.00 sec)
- create a user called qatest with password 'x' to access database. You'll have to change the attached smack file if you have another user.

- on the remote machine, create a file /var/smack-data/test.dat
- run super-smack "super-smack test.smack 2 1000"

On the db server, run mytop and hit 'i' to filter out sleeping processes.

It is identifying that the wrong host!

      Id      User         Host/IP         DB      Time    Cmd Query or State                  
                    
      --      ----         -------         --      ----    --- ----------                                        
 1272694    qatest  lab-db05:38225       test         6 Connec Reading from net                                      
 1272695    qatest  lab-db05:38226       test         6 Connec Reading from net                
                    
 1275387      root       localhost       test         0  Query show full processlist          
                  

This same info is show with "mysqladmin -u root -p processlist"

+---------+------------+------------------+--------------+---------+------+------------------+------------------+
| Id      | User       | Host             | db           | Command | Time | State            | Info             |
+---------+------------+------------------+--------------+---------+------+------------------+------------------+
| 1293619 | qatest     | lab-db05:58227   | test         | Connect | 2    | Reading from net |                  |
| 1293620 | qatest     | lab-db05:58228   | test         | Connect | 2    | Reading from net |                  |
| 1296643 | root       | localhost        |              | Query   | 0    |                  | show processlist |
| 1296646 | qatest     | lab-db05:33011   | test         | Connect | 0    | Reading from net |                  |
+---------+------------+------------------+--------------+---------+------+------------------+------------------+

Just curious, how you compiled your 4.1.14 version (what configure options where used), or it was an RPM/standard binary from MYSQL?

How you start your mysql server usually (any mysqld options used)?

Used standard RPM install from MySQL.

Servers are usually started using /etc/init.d/mysql start.

Thank you for the additional information. Please, send the content of your /etc/init.d/mysql file, just to be sure about the real options used.

mysql scrip to start server

Attachment: mysql (application/octet-stream, text), 6.16 KiB.

configuration file on database server

Attachment: my.cnf (application/octet-stream, text), 6.00 KiB.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".